Building on it being an SSD/race problem, I decided to add a delay
before gnome-settings-daemon would start. The relevant file that I
changed was /etc/xdg/autostart/gnome-settings-daemon.desktop. I changed
the line:
Exec=/usr/lib/gnome-settings-daemon/gnome-settings-daemon
to this:
Exec=bash -c
Post #54 also doesn't work for me and I also have an SSD drive. Here's
my xsession-errors file right after logging in.
** Attachment added: ".xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/649809/+attachment/1720579/+files/.xsession-errors
--
Meerkat (1
** Visibility changed to: Public
--
gnome-settings-daemon crashed with SIGSEGV in g_hash_table_lookup()
https://bugs.launchpad.net/bugs/665922
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
desktop-
Sorry, I don't have a definite way of reproducing the crash. Apport just
happened to be running which is why it was able to catch this. So far,
from the time I reported the crash, System Monitor hasn't crashed again.
Perhaps it's random.
--
gnome-system-monitor crashed with SIGSEGV in gtk_widget_
** Attachment added: "CoreDump.gz"
https://bugs.launchpad.net/bugs/627831/+attachment/1533449/+files/CoreDump.gz
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/627831/+attachment/1533450/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.
