Since the hardware is no longer available for doing troubleshooting
with, we'll have to close the bug for now. However please feel free to
reopen if you or anyone else has the same HW and can reproduce this
issue using the latest development version of Ubuntu and is willing to
do some troubleshoot
No, I have not. I don't tend to run current+1 releases. I will run
Natty when Natty is GA. I used to run +1 releases but any more I really
don't have time to do the daily updating and bug reporting/tracking that
that requires. Indeed, I have even shifted to an M.O. of only running
LTS on my non
Hey Brian,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
xorg server segfaulted
https://bugs.launchpad.net/bugs/670565
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://
Actual crash is in GdmLog1. Not a very helpful crash, indeed.
--
xorg server segfaulted
https://bugs.launchpad.net/bugs/670565
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
htt
--
xorg server segfaulted
https://bugs.launchpad.net/bugs/670565
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
