Recent searches
Search options
On #GNOME, you have this really useful app called Settings where you can, well, set your system Settings. So far, so good.
So then one day, it stops launching. Oops! So you go into terminal to try and launch it to see if there is any debug output…
settings
Unknown command.
Oh, why? Because Settings app’s binary isn’t called settings, it’s called gnome-control-center.
But of course you already knew that because you can read minds.
(Raised similar issues before, they don’t get the problem.)
In case anyone at #GNOME/Red Hat/Fedora/IBM wants to take a look:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2813
PS. My hunch: Most likely has something to do with the app attempting to launch after external monitor configuration changes.
Said external monitor configuration changes happen if you accidentally hit Super + P to toggle between Single monitor and Joined monitor modes and then hit it again to go back to Joined monitor upon with #GNOME summarily forgets the configuration you had before and concocts a different one on the spot (eat that, AI), forcing you to manually set up your monitors again.
@aral #Wayland or #Xorg? Wayland would be my prime suspect if you are using that?
I often have quirky screen resolution issues when swapping between monitors although not directly Gnome Settings crapping out, also I'm not on Fedora... Swapped back to X recently (after trying to run some old game) and things a tad more stable..