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

docs(gnome-extensions): Add known issue about GSConnect not working type of scenario

Browse source
This commit is contained in:
fiftydinar 2024-07-22 16:54:55 +02:00
parent 8ccd96b93e
commit d8e48d98e9
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -68,3 +68,25 @@ If you get the error similar to this one (Fly-Pie extension example):
Then please open the issue in BlueBuild Modules GitHub repo with the affecting extension, as it's trivial to fix.
https://github.com/blue-build/modules/issues/new
### Some extensions published in https://extensions.gnome.org are hard-coded to user locations
Those type of extensions are fixed to these locations:
- `/usr/local/share/` (`/var/usrlocal/share/`)
- `$HOME/.local/share/`
Those locations are not writable in build-time.
That means that extension has build instructions for packagers to build the extension either system-wise or user-wise.
While some extensions might not have this limit even with the instructions above, some extensions might have.
GSConnect from https://extensions.gnome.org has this limitation & requires the system version of the extension to make it work successfully.
Those system versions are usually provided by the system packagers.
So the solution is to install the extension from system repository instead if available.
In this scenario, you will notice the extension error similar to this when trying to run it (notice the explicit request to `/usr/local/share` location):
```
GLib.FileError: Failed to open file “/usr/local/share/glib-2.0/schemas/gschemas.compiled”: open() failed: No such file or directory
```