This is what was being logged just before a reproducible (on this boot anyway) firefox-3.5 seg fault when I launched firefox on the CLI after a prior crash. aaport didn't pick up on the crash though.
Crash was when I was in google voice, trying to click the button to edit cell phone settings... It did work previously (several days back) - no idea what changed. [08-08 02:40:16] Torbutton NOTE: Crash detected, attempting recovery [08-08 02:40:16] Torbutton NOTE: Restoring cookie status [08-08 02:40:16] Torbutton NOTE: Loading non-tor jar after crash [08-08 02:40:16] Torbutton NOTE: Restoring tor state (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead (firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead Segmentation fault (core dumped) -- (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead - overeager XID caching https://bugs.launchpad.net/bugs/401823 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
