-
Notifications
You must be signed in to change notification settings - Fork 6
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
Problem with schema not visible #18
Comments
Came upon the same issue on a fresh Linux Mint 17.3 installation. Could the readme be updated with a mention to jest's solution for this possible problem? |
I also had this issue using Cinnamon on Arch Linux. I saw on projecthamster.org that you plan on rewriting a lot of things. However, seeing that "as it looks right now, the current hamster repository will stay as it is", it would be nice to at least include the workaround in the README file as Songworks suggested. At least for the time being. |
New shema have been build and codebase have been updated on cinnamon spice It should solve the issue. |
As this Issue documents the cinnamon applet is now maintained by the Mint Linux team. |
My platform:
According to the docs it is enough to clone the repo into
~/.local/share/cinnamon/applets
. However, when doing so, I'm able to see the applet on the list, but adding it to the panel results in the error. The corresponding lines in the log:After digging a bit, looks like this results from the lines in
convenience.js
:Indeed, running
gsettings list-schemas
doesn't showorg.cinnamon.hamster-applet
. Only after doing what is normally done by proper package, i.e. droppingschemas/org.cinnamon.hamster-applet.gschema.xml
into/usr/share/glib-2.0/schemas
and runningglib-compile-schemas .
inside, the applet is able to see the schema, installs and runs correctly.Is this some specificity of my platform, or is it supposed to work that way? If so, the README is oversimplifying things...
Maybe adding some detection of the schema in applet's local dir would be helpful? I see that Gio.SettingsSchema describes exactly this use case. If you think it is the way to go, I can hack some PR from this...
The text was updated successfully, but these errors were encountered: