dconf extension lock detection #901
Description
Is your feature request related to a problem? Please describe.
Recently I updated my system to Fedora 42 to 43 and upon starting up after the update I found that all GNOME extensions were disabled and the toggle to enable them from Extension Manager was greyed out and non-clickable (clicking the toggle just opened the shade for the extension as if the toggle weren't even there). There was no feedback within the application as to what the issue was.
Eventually I discovered that the issue was that in /etc/dconf/db/local.d/locks/ was an extensions-mandatory file which must have been leftover somehow from some part of the update process (not quite sure). Deleting the lock file restored extension functionality.
This doesn't seem to be a very common issue (as it took awhile to find the solution), but it is a frustrating one that I could see a less technical user not being able to identify and fix.
Describe the solution you'd like
It would be helpful if when extensions are locked down in this way (due to an error in an update like in my case, or if an admin has intentionally locked down extension functionality) that Extension Manager inform the user if possible, perhaps offering solutions as well?
Additional context
Big fan of this project, thanks as always for all your hard work :)