-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to Enable Extensions without gnome restart #25
Comments
Hey @starr-dusT - thanks for reporting this issue. The extension should be available, without the need for restarting Gnome. I'll classify this as a bug, and will look into it - although it may take a while. |
Hey @PeterMosmans. I'm using Fedora 37 along with the Gnome it comes with (43.1). When I have a moment I'll try on another distro/gnome version and see what happens. Thanks for looking into it! It isn't really a huge deal. For now I'm not enabling the extensions through Ansible then enabling them in the extension manager after a reboot. |
Can confirm this happens on Ubuntu 22.04.1 with Gnome 42.2 too. |
Thanks for reporting @starr-dusT / @CubicrootXYZ . I'm finally taking a look at this |
Hey @CubicrootXYZ / @starr-dusT : I've implemented 2 changes in the extension:
https://github.com/PeterMosmans/ansible-role-customize-gnome/compare/enforce-gnome-restart |
@PeterMosmans tried it, still getting the error message but ansible continues now and everything gets installed properly. |
Thanks for testing - yeah, the error still shows (I'm a bit hesitant to suppress that), but at least all updates are recognized after 'force reloading' Gnome. |
Hello. Love this role as setting keybinds within Gnome is one of my least favorite things! I've noticed issues with enabling extensions, but hopefully I'm just missing something...
If I install and enable extensions like this:
The playbook fails during the enable task with:
The error indicates it cannot find an installed extension to enable and if I manually list extensions with
gnome-extenions list
the desired extension isn't listed. If I restart Gnome and run the playbook again the enable works and the extension is shown withgnome-extenions list
. Is this expected behavior or am I missing something here? Thanks!The text was updated successfully, but these errors were encountered: