We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Oh, I see what I did. I attached the log from *after* I got the system
back up. I'll find the relevant log and attach it tonight when I get
home.
--
Edgy Xorg crash
https://launchpad.net/bugs/63376
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
try doing
ls /var/log/ | grep Xorg
and see what it gives. for some reason, I don't have my backlogs -??-.
Hopefully you have :)
--
Edgy Xorg crash
https://launchpad.net/bugs/63376
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Apologies. The Xorg.0.log was just the latest log file (i.e., with the
latest timestamp) in /var/log. Is there another one I can attach,
assuming I can find a relevant one at this stage?
--
Edgy Xorg crash
https://launchpad.net/bugs/63376
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
assigning to linux as this is a "soft" lock on top of xorg crash.
PS. I think the Xorg.0.log you attached is not from the x session crash?
** Changed in: Ubuntu
Sourcepackagename: None => linux-source-2.6.17
--
Edgy Xorg crash
https://launchpad.net/bugs/63376
--
ubuntu-bugs mailing list
ubun
Here's my latest Xorg log.
** Attachment added: "Xorg.0.log"
http://librarian.launchpad.net/4568148/Xorg.0.log
--
Edgy Xorg crash
https://launchpad.net/bugs/63376
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
