Post #3996249
2026-07-21 16:52 UTC
@creak@mstdn.ca @TheEvilSkeleton@social.treehouse.systems As far as Ubuntu is concerned, they update their distro frequently enough that the issue doesn't arise and they're keeping pace with GNOME development.
I dunno about Debian, but I'm willing to wager that when they ship stuff, they also have enough maintainers to carry the burden themselves once the software reaches EoL.
Mint doesn't have any of that, it's a relatively small distro with a very slow development cycle (they even slowed it down further recently). So that makes it doubly baffling that they would conduct themselves like that, when both parties involved are strapped for time and resources.
This issue isn’t even really about the pros and cons of libAdwaita, that was just for context.
Mint has deliberately chosen to freeze certain GNOME applications in a hopelessly outdated state because they disagree with the technical decisions made by the upstream developers. They probably lack the resources to maintain these apps themselves or backport fixes, yet still choose to ship outdated software.
The ones who suffer as a result are the Mint users, who have to deal with utterly outdated software suites, and the upstream developers behind them, who are unjustly blamed for this desolate state of affairs.
Mint allows this suffering to continue and refuses to take responsibility for its decisions.
Replies (1)
-
@creak@mstdn.ca 2026-07-21 21:13
@SebinNyshkim@meow.social @TheEvilSkeleton@social.treehouse.systems in order to mitigate this issue (if we assume Mint maintainers won't change), maybe add a template in the Github/GitLab issue that would ask the version of the GNOME Calendar app and warn that Mint have a very old version and that the bug is very probably already fixed. Just a suggestion. I personally don't mind answering a few questions when creating issues, as long as it reasonable 😉 but information such as the distribution, its version, and the version of the app seems very reasonable to me.