Now here is something that did help. In effect it is likely much the same as killing gnome-settings-manager, except it is not killed, but just started later:
but these don't seem to do anything. Therefore I created a ~/.config/autostart/gsd.desktop which starts gnome-settings-daemon.
The downside of this approach in contrast to the kill-approach is that the if the daemon falls over, it is not automatically restarted.
Obviously it helps to start the daemon rather later than earlier. Looking at the preconditions in
/usr/share/upstart/sessions/gnome-settings-daemon.conf, they are
start on started dbus and starting gnome-session INSTANCE=GNOME
There is probably only one little thing missing here, but I have no background to guess what it might be.
Now here is something that did help. In effect it is likely much the same as killing gnome-settings- manager, except it is not killed, but just started later:
sudo echo manual >/usr/share/ upstart/ sessions/ gnome-settings- daemon. override
This prevents the gnome-settings- daemon to be started by the 'init --user' session manager.
I thought now the gnome-settings- daemon might be started by one of
/usr/share/ upstart/ xdg/autostart/ gnome-settings- daemon. desktop autostart/ gnome-settings- daemon. desktop
/etc/xdg/
but these don't seem to do anything. Therefore I created a ~/.config/ autostart/ gsd.desktop which starts gnome-settings- daemon.
The downside of this approach in contrast to the kill-approach is that the if the daemon falls over, it is not automatically restarted.
Obviously it helps to start the daemon rather later than earlier. Looking at the preconditions in upstart/ sessions/ gnome-settings- daemon. conf, they are
/usr/share/
start on started dbus and starting gnome-session INSTANCE=GNOME
There is probably only one little thing missing here, but I have no background to guess what it might be.