Hi Jamie, do you happen to still have this bug? Sorry didn't run into it until just now.
None of your log files show evidence of an X crash. The backtrace you posted in comment #20 shows it's definitely an X server crash; unfortunately looks like debug packages weren't installed so no clue what the crash was. However in the initial apport data I noticed this, which looks weird: GdmLog: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting. Could something have been futzing up that directory and causing X to fail? Or maybe a red herring. Anyway, if this is still an issue please let us know. A full backtrace with symbols installed and such would be quite lovely. Docs are at https://wiki.ubuntu.com/X/Backtracing ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/627055 Title: [lucid] X received SIGQUIT _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
