Post #4009827

2026-07-22 10:17 UTC

Oh the GNOME Calendar vs Linux Mint situation is so much worse than I thought from the GNOME perspective rant blog post. The key thing that makes me say this? The existence of LibAdapta. Mint maintains an entire ass fork of LibAdwaita whose sole purpose is theming GTK apps to look more at home within Mint's look. Keeping GNOME branding and support links on something this deeply altered is such a middle finger, especially when GNOME explicitly asked before to not repackage their apps with custom theming because it points angry users of software far altered from what they ship toward them. Further Reading: - “How far would hostile distributions go to hurt application developers?” - TheEvilSkeleton, a GNOME contributor - “Who’s responsible for bug reports on old software versions?” - Nate, a KDE contributor

Replies (1)

@navi@social.vlhl.dev 2026-07-22 10:29

@lunareclipse@snug.moe while at the same time, gnome calendar provides no option to replace the bug report url, it's odd to me to complain about wrong reports but give distros no way to remedy that except patching whenever there's a bug report option, most distros set it, e.g. gentoo's gimp package: -Dbug-report-url="${BRANDING_OS_BUG_REPORT_URL}" checking it on mint, they use the ubuntu package, which also does: -Dbug-report-url=$(BUGTRACKER) \ (ofc this does mean that mint's package will link to ubuntu's bug tracker which is uuhhh okay ig (actually maybe not if they're building the recipes from ubuntu themselves)) i feel like this would've been mostly avoided from the start if build options were provided, and it's doubly odd to insist on having mint fork it without considering adding branding build time options like plenty of other packages do for this exact reason

Open ##4009825