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
cinnamon-settings-daemon not starting #148
Comments
What distro are you using? |
Ubuntu 16.10 with https://launchpad.net/~gwendal-lebihan-dev/+archive/ubuntu/cinnamon-nightly The problem has been present on this specific user account on this specific machine for 2+ years with no problems on numerous other machines, though, so I suspect that at some point in time, some configuration migration to a new format, or some-such, may have failed, so I'm mainly interested in discovering, what might prompt cinnamon{,-session} to attempt to start csd from that erroneous location. Best regards, Sune Mølgaard |
Any ideas? |
It turned out that I had the following three files of between 2 and 4 years of age, which I have now removed: cinnamon-fallback-mount-helper.desktop in /etc/xdg/autostart cinnamon-settings-daemon.desktop specified to exec "/usr/lib/cinnamon-settings-daemon/cinnamon-settings-daemon". I'll leave it up to you to decide whether such files should be removed as obsolete (possibly after asking the user), or if nothing should be done. In the latter case, please close this issue. |
For a very long time, now (+2 years), gtk theme and desktop backgrounds have been failing to adhere to the settings I chose (on one specific machine).
Looking at .xsession-errors just now, I see
with the top line being the important one.
What may prompt Cinnamon to try to start csd from /usr/lib/cinnamon-settings-daemon/cinnamon-settings-daemon , when
smo@dell-smo:~$ ls -lh /usr/bin/cinnamon-settings-daemon
lrwxrwxrwx 1 root root 73 Jan 12 01:03 /usr/bin/cinnamon-settings-daemon -> ../lib/x86_64-linux-gnu/cinnamon-settings-daemon/cinnamon-settings-daemon
?
Best regards,
Sune Mølgaard
The text was updated successfully, but these errors were encountered: