Recently became known Information about an intense public dispute between one core developers of GNOME Calendar, and the Linux Mint package maintenance team. The conflict lies in Linux Mint's decision to distribute a severely modified and outdated version of the application to adapt the software to its environment.
The problem isn't the technical alteration of the code, but rather that the distribution retains the official name "GNOME Calendar" and keeps the original contact links in the information window. As a result, Linux Mint users experiencing errors in this modified version constantly direct their bug reports to the GNOME developers, requiring a team of volunteers to spend their time classifying and closing complaints about problems they didn't cause or that they fixed years ago.
To understand the magnitude of the problem, it is necessary to analyze the changes that Linux Mint implemented. In their effort to maintain compatibility with their own environments desktop and visual themes, Mint made the active decision to downgrade GNOME Calendar. While the original project had moved forward using GTK4 and libadwaita, Linux Mint forced a step back to GTK3.
Furthermore, to achieve this forced integration, Mint made the application use libAdaptalibAdapta is a fork of libadwaita. The major drawback is that libAdapta is locked into outdated versions (based on version 1.5, while the original project is already at 1.9). This regression, spanning 2 to 4 years, Obsolescence caused hundreds of old bugs, already patched by GNOME, to resurface on the computers of Linux Mint users.
The breakdown in communication and the limitations of free licenses
Seeking a logical solution, the The GNOME Calendar team opened a formal report on the Linux Mint platform requesting a simple action: Remove references to the main project, remove support links, and change the name and icon of the modified application..
This The request for termination was ignored For six whole months, and when the Mint package maintainer finally responded, they deflected attention from the core issue by comparing their situation to that of Ubuntu LTS and Debian, arguing that these distributions also offer older versions of the calendar. However, the The GNOME developer immediately emphasized that the conflict does not lie in the age of the product. from the code, but in the distribution of a structurally altered version which usurps the identity of the original project, a problem not generated by unmodified Debian or Ubuntu packages.
The climb of Tensions reached their peak when Linux Mint categorically rejected the request of rebranding. Instead, the The maintainer suggested that the GNOME developers themselves should program the warning systems. within the application to notify users about outdated versions, a proposal that demanded even more unpaid work from the original team.
The case was closed unilaterally by Mint under the premise that free software licenses allow this type of redistribution and modification without restrictions. For GNOME developers, this stance is an evasive tactic. which deliberately confuses freedom of the code with trademark infringement, setting a dangerous precedent.
The incident has opened a deep debate about ethics in the distribution model, highlighting how certain derivative distributions can abuse the open source ecosystem, mentally exhausting the original creators by shifting support responsibilities onto them in a hostile and inconsiderate manner.
By distributing a broken, unsupported, and heavily modified build under the explicit name of "GNOME Calendar," Linux Mint is infringing on the project's identity, deceiving end users, and tarnishing the reputation of the original developers. Hostile distributions know that hiding behind the "you chose the wrong license" argument is an easy defense against independent developers who lack the legal resources to initiate trademark infringement litigation.
Finally, if you are interested in learning more about this, you can consult the details in the following link.