particle-os/particle-os-modules
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(gnome-extensions): Clarify known issue about extension-only gsch… (#289)

Browse source
This commit is contained in:
fiftydinar 2024-07-22 17:22:28 +02:00 • committed by GitHub
commit e863d596ba
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

10
modules/gnome-extensions/README.md
View file

@ -58,11 +58,17 @@ How to uninstall extensions using the module:
## Known issues
### Some extensions complain about missing gschema.compiled file
### Some extensions use extension-only gschemas.compiled file location
This is a rarity, but some extensions might complain about this one, due to the way they are programmed with hard-coded gschema locations.
This is a rarity, but some extensions might have this issue, due to the way they are programmed with hard-coded gschema locations.
Most extensions which follow Gnome extension standards don't have this issue.
Standard location for global `gschema.compiled` file is:
`/usr/share/glib-2.0/schemas/gschema.compiled`
Those problematic extensions explicitly ask for this extension-only location instead:
`/usr/share/gnome-shell/extensions/$EXT_UUID/schemas/gschemas.compiled`
If you get the error similar to this one (Fly-Pie extension example):
`GLib.FileError: Failed to open file “/usr/share/gnome-shell/extensions/flypie@schneegans.github.com/schemas/gschemas.compiled”: open() failed: No such file or directory`