Comment 10 for bug 93613

I've recently upgraded to fiesty from edgy, and I'm experiencing the same problem (on initial upgrade I wasn't experiencing this problem - about 3/4 days ago).

I've tried the method of renaming gnome-session with a .real extension, and having a shell script running the following command as gnome-session in /usr/bin:

#!/bin/bash
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/bin/gnome-session.real $*

I also found that running like this did not produce the crash. So I logged out and renamed the files back (leaving gnome-session and gnome-session.valgrind), then logged back in again via gdm. I'm getting the crash again!

I'll try changing it back and logging in and out a few times, to see if I can reproduce it. In the meantime, here's the valgrind.log produced.