Comment 5 for bug 709264

Interesting - I've been hitting something similar to this while messing around with the startup order of compiz trying to get the glib mainloop to start before anything else g* starts. Could people who are having this problem do the following?

1. Drop to a VT
2. pidof compiz #note the number that it spits out
3. sudo gdb #needed to attach to arbitrary applications
4. attach the_number
5. set logging-file ~/glib-bug.txt
6. bt
7. bt full
8. exit

And then post the resulting glib-bug.txt in their home dir? That would be fantastic.

Also, Unity Team members - please assign yourself if this bug is related to you.