-
Notifications
You must be signed in to change notification settings - Fork 298
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-GIO-ERROR - 'org.nemo.preferences' does not contain a key named 'context-menus-show-all-actions' #2241
Comments
The key exists . https://github.com/linuxmint/nemo/blob/4.2-maintenance/libnemo-private/org.nemo.gschema.xml#L333 Try reinstalling nemo. |
That key is removed in the current master branch - this is from the nemo-fileroller extension - it had been checking that key to determine whether or not to show one of its menu entries. The extension is fixed in git (https://github.com/linuxmint/nemo-extensions), if you want to re-build it. Otherwise, uninstalling nemo-fileroller would resolve this also. |
@mtwebster From the info posted he is running nemo stable not master and the key was only removed two days ago from nemo-extensions master. |
@leigh123linux reinstalling nemo didn't fix it. I'm running the daily builds (https://launchpad.net/~linuxmint-daily-build-team/+archive/ubuntu/daily-builds) though. I agree though that even with the daily build ppa breaking code shouldn't be published. |
Just install the fixed nemo-fileroller package: https://github.com/linuxmint/nemo-extensions/releases/tag/master.mint19 The daily ppa is not considered stable, things may unavoidably break at times. What should probably happen is that the extensions be published in that ppa alongside everything else. |
Issue
After login, there are no symbols (folders, files) displayed on the Desktop.
Clicking the nemo tray icon or trying to open nemo via the start menu does not show any window.
Trying to open nemo via terminal results in the following error:
The corresponding file, however, does exist:
Additional information
The text was updated successfully, but these errors were encountered: