Post #3996248

2026-07-21 21:13 UTC

@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.

Replies (1)

@SebinNyshkim@meow.social 2026-07-21 21:24

@creak@mstdn.ca @TheEvilSkeleton@social.treehouse.systems Someone already made that suggestion on the Mint Issue tracker and it does not address the core issue: Mint users open tickets on the GNOME Calendar issue tracker because Mint is entirely disinterested in forking or rebranding, thus users keep being sent there to open issues that don't even exist anymore. It takes time away from GNOME devs for a problem that is entirely caused by Mint. It shouldn't be an issue for GNOME devs to solve or even address on their end. The core issue remains Mint's blatant unwillingness to fix an issue they brought on and they already went ahead and tell GNOME Calendar devs to deal with it and be total assholes about it. An issue template will not stop people from opening issues for ancient software full of bugs that have long been fixed. Time spent on telling people it's Mint's fault, is time not spent on making the actual app better and it burns devs out. Again: This is an issue of Mint that GNOME devs shouldn't have to deal with to begin with. All it would take is for Mint to replace a link. That's it.

Open ##3999802