I have attached an archive of four valgrind logs, but at no time did I manage to trigger apport (it seems to occur at random). The first I ran after killing g-s-d and just running the command from the terminal. The second and third I produced by changing the command in 'sessions' so that it ran on startup. The fourth is after I removed the .crash file from /var/crash, in case this was preventing apport from appearing.
I am now running Intrepid, but (I think) I remember still getting this issue (there was a .crash file present for it on my clean install). I will keep the valgrind command running on each startup in case I get the problem that apport catches again. Please let me know if the logs I provided are useful or not, and if a log of apport catching the issue would be of more help. ** Attachment added: "Valgrind logs" http://launchpadlibrarian.net/16347074/valgrind-logs-gnome-settings-daemon.tar.gz ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => New -- gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/246447 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
