-
Notifications
You must be signed in to change notification settings - Fork 16
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
GLIB.FileError #8
Comments
@htcosta please try to create a folder called "schemas" inside the extension folder at "home/user/.local/share/gnome-shell/extensions/gnomespotifylabel@mheine.github.com/". Then move the file "gschemas.compiled" and "org.gnome.shell.extensions.spotifylabel.gschema.xml" into the new folder. It should look like this then: If you are on Ubuntu you can restart your gnome shell with "Alt + F2" and "r" afterwards. @mheine it seems that these two files are in the root of the new zip folder instead of the schemas/ folder. It works locally if I use |
That worked, was on Fedora 32, Gnome 3.36.6 |
@raujonas I'm fairly sure that I've always used the |
This also works on Ubuntu 20.04 |
thanks |
raujonas fix worked for me, Ubuntu 20.10 |
GLib.FileError: Failed to open file “/home/user/.local/share/gnome-shell/extensions/gnomespotifylabel@mheine.github.com/schemas/gschemas.compiled”: open() failed: No such file or directory
Stack trace:
buildPrefsWidget@/home/user/.local/share/gnome-shell/extensions/gnomespotifylabel@mheine.github.com/prefs.js:15:44
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17
The text was updated successfully, but these errors were encountered: