Getting a valgrind log is not trivial, one way to do it is to create a gnome-session wrapper calling valgrind on the actual gnome-session binary renamed. If you don't want to spend work on it that's ok, somebody else will likely hit the bug as well and send a debug log then. The program is "gnome-session" and there is no argument required. The .gnome2/session is in your user directory, if you don't have it you are using a stock session then
-- [apport] gnome-session crashed with SIGSEGV in pthread_getspecific() https://bugs.launchpad.net/bugs/103315 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
