Thanks apelete, marking closed as fixed.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
--
Random "Failed to start x server" on Dapper LTS
https://bugs.launchpad.net/bugs/62647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
I do not use Dapper LTS anymore, so I think you can close it as fixed in Feisty.
Thanks.
--
Random "Failed to start x server" on Dapper LTS
https://bugs.launchpad.net/bugs/62647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Okay, unfortunately there's not enough information yet to troubleshoot
it. Do you still need it fixed in Dapper LTS? (E.g. are you using
Dapper in a production environment?) If not, then I think we can close
this as fixed in Feisty, and if someone needs the fix in Dapper then a
backport can be r
I have upgraded to Feisty since I first reported the bug.
It didn't happen on Feisty a single time though...
--
Random "Failed to start x server" on Dapper LTS
https://bugs.launchpad.net/bugs/62647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
Sorry to hear about this bug in Ubuntu, thanks for reporting it.
Does this issue still occur for you? If possible, can you test and see
if it still occurs in Feisty or newer?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
Random "Failed to start x server" on Dapper LTS
https:
The bug is still happening. GDM just fails to start two times now,
before my third reboot, and with the same "Fatal server error: Caught
signal 11. Server aborting" message in the log file...
--
Random "Failed to start x server" on Dapper LTS
https://launchpad.net/bugs/62647
--
ubuntu-bugs mai
