Hello Sebastien,
it indeed doesn't crash in the sense that Apport is triggered. g-s-d
seems to get somehow into a completely unresponsive state, meaning you
can't terminate it with anything but kill -9 . It seems to consume no
CPU time, so g-s-d is obviously not running in a loop.
I did some further testing with g-s-d when it was properly running that showed
interesting behaviour. If I sended a SIGTERM ("normal kill") to g-s-d, the
custom desktop theming disappeared instantly, like one would expect when g-s-d
has been terminated.
But looking at the running processes showed that the same g-s-d process was
still there, allthough now in an unresponsive state (like it happens if I just
start a desktop session on my virtual machine)! Doing kill -9 helps of course
to terminate it completely.
I tested this both on my virtual machine when I had restarted g-s-d
manually and also on my Maverick desktop running on real hardware (where
never any problem with g-s-d has occured).
As a conclusion, could it be possible that the following happens: While
the desktop session is loading, g-s-d receives (for an unknown reason) a
SIGTERM and remains in an unresponsive state untill one kills it with
kill -9 (and manually restarts it).
Is there any way I can help with debugging such an issue?
Anyway, here is my .xsession-errors file (beware, it inflates to
73MB!).
Kind regards,
Jan
** Attachment added: "xsession-errors.tar.bz2"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/733253/+attachment/1994606/+files/xsession-errors.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733253
Title:
gnome-settings-daemon freezes, desktop theming disappears
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
