Hi Richard,

If the startup script fails to start X, it generally displays a rather
ugly text mode dialog telling you something went wrong and shows you the
errors.  It doesn't regenerate xorg.conf.  In fact, this is something
I've worked on this past week, which is why I know we don't already have
the capability:  http://people.ubuntu.com/~bryce/BulletProofX/

However there are a number of tools which will reconfigure your
xorg.conf (sometimes with disastrous results).  These comprise tools
generally associated with binary drivers.  I suspect that installing one
of these drivers may cause an automatic change to your xorg.conf to
switch to that driver, but I'm not 100% sure.  However these automatic
changes don't usually result in a completely incorrect xorg.conf.  Other
tools that do overwrite xorg.conf with their own generally are not run
automatically; they'd be something you ran specifically.  For instance,
displayconfig-gtk (shown in the screenshots above), as well as config
tools provided by the binary driver providers.  I believe running 'X
-configure' will do this as well.

Anyway, since we can't reproduce this easily, it'd be pretty difficult
to diagnose what exactly happened.  My best guess is like I gave before,
that an upgrade triggered an xorg reconfiguration event.  There is a
corner case I know of in Feisty where Ubuntu will successfully generate
a proper xorg.conf during the installation process, but will not install
the tool needed to correctly reconfigure xorg.conf later.  Fortunately
that particular scenario has already been fixed in Gutsy, so if I'm
right, the problem is already taken care of.

In any case, if you do run into this again, please reopen the bug.
Thanks again!

** Changed in: xorg (Ubuntu)
       Status: Needs Info => Fix Released

-- 
xorg.conf gets (wrongly) overwritten after hardware crash 
https://bugs.launchpad.net/bugs/114941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to