I didn't know you could ctr+c in gdb and still get a backtrace. I went back to the debugging pages to see if there was some way some how to get a backtrace, I think this'll suffice. I read in the instructions that if a program hangs but doesn't crash you can perform a ctrl+c and still get a backtrace. I took a non-hanging (but responding to input) as if it were a program hanging and did just that (the ctrl+c). Sure enough I was able to get a backtrace. Hopefully it's detailed enough, since the conditions fall outside the normal. I'm attaching the log to my reply.
** Attachment added: "gdb-rhythmbox.txt" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/672089/+attachment/1729739/+files/gdb-rhythmbox.txt -- GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed https://bugs.launchpad.net/bugs/672089 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
