ubuntu-x-swat team mailing list archive

[chris_c <c.camacho@xxxxxxxxxxxx>]

I've since fixed the problem, to replicate the problem just
do something to your xorg.conf that stops xorg starting
I noticed it first after a kernel upgrade while using cuda nvidia
driver

This isnt about the specific problem I've had but rather
that there is no fallback for xorg

---- Bryce Harrington <bryce@xxxxxxxxxxxxxxxxxxx> wrote: 
> Hi c-camacho,
> 
> 
> Thanks for including the attached files.  Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?
> 
> [This is an automated message.  Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
> 
> 
> ** Tags added: needs-xorglog
> 
> ** Tags added: needs-lspci-vvnn
> 
> ** Changed in: xorg (Ubuntu)
>        Status: New => Incomplete
> 
> -- 
> no fallback for failing xorg
> https://bugs.launchpad.net/bugs/489491
> You received this bug notification because you are a direct subscriber
> of the bug.
> 
> Status in “xorg” package in Ubuntu: Incomplete
> 
> Bug description:
> Binary package hint: xorg
> 
> If for any reason xorg fails to start, you get caught in a loop as gdm repeatedly tried to start xorg
> 
> At some point it should fall back to a console to allow a fix or even have some console based menu
> to allow none technical people to select possible solutions - some kind of "safe mode" xorg config would
> be useful...
> 
> As it stand I was forced to boot from cd and manually mount and fix the problem boot media
> 
> How on earth is a non technical Ubuntu user supposed to deal with xorg problems?

-- 
no fallback for failing xorg
https://bugs.launchpad.net/bugs/489491
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.