Ubuntu
xorg package

Failsafe X doesn't always overwrite /etc/X11/xorg.conf.failsafe

Bug #480747 reported by Mario Limonciello
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: xorg

x11-common: 1:7.4+3ubuntu10

The failsafe stuff makes the assumption that the content of this file has not been modified and will always work. Since it's treated as a conffile in /etc, it's very possible that someone has overwritten this file.

It would be better to keep this file in a static place elsewhere on the system and never overwrite it, just refer to the file when failsafe X mode is started.

Related branches

lp:ubuntu/natty/xorg
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi superm1,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[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
Revision history for this message
Mario Limonciello (superm1) wrote :

Logs aren't needed for this type of bug.

Revision history for this message
Bryce Harrington (bryce) wrote :

Actually, I gave some thought to this, and decided that since xorg.conf.failsafe is so obscure of a file, if someone did overwrite it, it would likely have been for a good reason, and that overwriting it would perhaps be rude.

For instance, this file assumes the "vesa" driver will work on their hardware, but that is not true in all situations. Perhaps they edit it to change to fbdev or something else. Shouldn't we respect whatever they specify?

Changed in xorg (Ubuntu):
importance: Undecided → Wishlist
status: Incomplete → Triaged
Revision history for this message
Flávio Etrusco (etrusco) wrote :

If it was always overwritten, what would be use for its existence?
BTW, failsafe X works without it, right? I vaguely remember trying it, but...

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.5+1ubuntu7

---------------
xorg (1:7.5+1ubuntu7) lucid; urgency=low

  * debian/local/Failsafe/failsafeXServer:
    + Actually produce xorg.conf.failsafe with the detected driver.
      Important for failures while running in KMS mode.
      (LP: #496773)
    + Force overwrite of existing xorg.conf.failsafe. Since above
      change produces different xorg.conf.failsafe's depending on
      what driver was selected, we must force it to regen each time.
      (LP: #480747)
 -- Bryce Harrington <email address hidden> Mon, 22 Feb 2010 22:38:22 -0800

Changed in xorg (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.