this post was submitted on 31 Aug 2026
72 points (97.4% liked)
Linux
15016 readers
875 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments







Ah yeah that's the main thing I hate about GNOME. If you have the extension installed you can just go to .local/share/gnome-shell/extensions and for each extension add 50 to the supported gnome-shell versions list. It actually works perfectly fine on GNOME 50 on my PC with that hack. I really don't know why GNOME extensions work this way because I've never had an extension that didn't run like normal after doing this.
The purpose of this is to force extension developers to verify that their extension works on the new version. The alternative would be extensions randomly breaking your system on upgrade.
Yeah that's reasonable. I guess I'd just want maybe a button in the extension manger "use anyway" to quickly enable "unsupported" extensions after an update without having to use this hack.
Extensions rewrite the shell's code, they're both very powerful and dangerous, it's why they're all reviewed by GNOME devs. I'm not sure letting people optionally bork their shell is a good idea, even if there's some automatic recovery options and it's gonna be harmless most of the time. No, the correct solution is if you like the extension you pick up the mantle, it's all open source - you can ask for the keys or fork away.
Well, since this extension is also on GitHub, I can try to sync it up that way, and then do a little editing to try to get it to work.
Thanks for the tip!