Ubuntu
xorg package

Failsafe X support added in proposed upload still doesn't work

Bug #477149 reported by Mario Limonciello
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
High
Unassigned
Karmic
Fix Released
High
Unassigned
Ubuntu karmic-updates
Lucid
Fix Released
High
Unassigned

Bug Description

Binary package hint: xorg

Recently some uploads to karmic-proposed were trying to fix the bulletproof-X support. These are still not working.

Trying to manually run the failsafe X server you get:
      Warning: Could not generate /etc/X11/xorg.conf.failsafe for vesa driver

Adding set -x, you can see why it's failing:

+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /etc/gdm/failsafeDexconf vesa xorg.conf
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z ]
+ exec
+ [ ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ SERVER=xorg
+ XF86CONFIG=/etc/X11/xorg.conf.failsafe
+ PROGNAME=failsafeDexconf
+ SHOWHELP=
+ EARLYEXIT=
+ getopt --options ho: --longoptions help,output: -n failsafeDexconf -- vesa xorg.conf
+ GETOPT_OUTPUT= -- 'vesa' 'xorg.conf'
+ [ 0 -ne 0 ]
+ eval set -- -- 'vesa' 'xorg.conf'
+ set -- -- vesa xorg.conf
+ :
+ shift
+ break
+ [ -n ]
+ [ -n ]
+ DEXCONFTMPDIR=
+ trap if [ -e "$DEXCONFTMPDIR/backup" ] && [ -n "$XF86CONFIG" ]; then \
        cat "$DEXCONFTMPDIR/backup" >"$XF86CONFIG"; \
      fi; \
      exec 4<&-; \
      rm -rf "$DEXCONFTMPDIR"; \
      bomb "received signal; aborting" HUP INT QUIT TERM
+ TDIR_PARENT=/tmp
+ TDIR=/tmp/dexconf-tmp-2459
+ [ ! -d /tmp ]
+ [ ! -w /tmp ]
+ rm -rf /tmp/dexconf-tmp-2459
+ mkdir -m 0700 /tmp/dexconf-tmp-2459
+ DEXCONFTMPDIR=/tmp/dexconf-tmp-2459
+ exec
+ cat
+ db_get xserver-xorg/config/device/driver
+ _db_cmd GET xserver-xorg/config/device/driver
+ IFS= printf %s\n GET xserver-xorg/config/device/driver
+ IFS=
 read -r _db_internal_line
+ RET=10 xserver-xorg/config/device/driver doesn't exist
+ return 10

ProblemType: Bug
Architecture: i386
Date: Fri Nov 6 22:06:46 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release i386 (20091027)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: xorg 1:7.4+3ubuntu9
PciDisplay:
 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Latency: 0
  Region 0: Memory at e0000000 (32-bit, prefetchable) [size=16M]
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=17d078ac-91bb-4a9b-b9c7-fd4751ecab95 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu9
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.31-14-generic i686
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1443): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (xfce4-terminal:1670): Terminal-WARNING **: Unable to load terminal preferences.
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
fglrx: Not loaded
glxinfo: Error: [Errno 2] No such file or directory
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

Related branches

lp:ubuntu/lucid/xorg
Revision history for this message
Mario Limonciello (superm1) wrote :
Changed in xorg (Ubuntu Karmic):
milestone: none → karmic-updates
Revision history for this message
Bryce Harrington (bryce) wrote :

It looks like debconf is no longer being seeded with the information that dexconf needs.

We should instead just put a static file in rather than trying to generate it. IIRC the generator was pretty much just ending up with a fairly empty file anyway. This attached file is basically what it had been generating in all cases.

Bryce Harrington (bryce)
affects: xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Revision history for this message
Mario Limonciello (superm1) wrote :

Fixing package. This really *is* a bug in xorg (where the failsafe stuff comes from). I just forcefully induced the failure using NVIDIA.

affects: nvidia-graphics-drivers-180 (Ubuntu Karmic) → xorg (Ubuntu Karmic)
Changed in xorg (Ubuntu Karmic):
status: New → Confirmed
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Mario Limonciello (superm1)
affects: nvidia-graphics-drivers-180 (Ubuntu Karmic) → xorg (Ubuntu Karmic)
Changed in xorg (Ubuntu Karmic):
status: Confirmed → Triaged
Bryce Harrington (bryce)
Changed in xorg (Ubuntu Lucid):
importance: Undecided → High
status: New → Fix Committed
Changed in xorg (Ubuntu Karmic):
assignee: nobody → Bryce Harrington (bryceharrington)
importance: Undecided → High
status: Triaged → In Progress
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted xorg into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in xorg (Ubuntu Karmic):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Roman Fiedler (roman-fiedler-deactivatedaccount) wrote :

At least dexconf still cannot generate a xorg.conf file, error similar to one in first post:

[pid 17251] <... read resumed> "GET xserver-xorg/config/device/bus_id\n", 4096) = 38
[pid 17251] write(7, "10 xserver-xorg/config/device/bus_id doesn't exist\n", 51) = 51

repo proposed activated, versions:
ii xserver-xorg 1:7.4+3ubuntu10
ii xserver-xorg-core 2:1.6.4-2ubuntu4

Revision history for this message
Mario Limonciello (superm1) wrote :

I can verify that the new proposed upload works properly.

@Roman:
The new functionality does not depend upon dexconf. The failsafe xorg.conf is generated by just cat'ing it out.

Revision history for this message
Roman Fiedler (roman-fiedler-deactivatedaccount) wrote :

Didn't know that, thought because of
+ exec /usr/share/debconf/frontend /etc/gdm/failsafeDexconf vesa xorg.conf (see initial post)
that both are linked. Will retry to generate failsafe xorg.conf.

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
Download full text (5.3 KiB)

There is one command in the GUI which still tries to generate via
dexconf. That probably should be disabled too, but that's separate from
this issue. First goal should just be to get user into the low graphics
mode so they can proceed with reinstalling -nvidia or whatever.

On Wed, Nov 11, 2009 at 09:28:12AM -0000, Roman Fiedler wrote:
> At least dexconf still cannot generate a xorg.conf file, error similar
> to one in first post:
>
> [pid 17251] <... read resumed> "GET xserver-xorg/config/device/bus_id\n", 4096) = 38
> [pid 17251] write(7, "10 xserver-xorg/config/device/bus_id doesn't exist\n", 51) = 51
>
> repo proposed activated, versions:
> ii xserver-xorg 1:7.4+3ubuntu10
> ii xserver-xorg-core 2:1.6.4-2ubuntu4
>
> --
> Failsafe X support added in proposed upload still doesn't work
> https://bugs.launchpad.net/bugs/477149
> You received this bug notification because you are a bug assignee.
>
> Status in “xorg” package in Ubuntu: Fix Committed
> Status in “xorg” source package in Lucid: Fix Committed
> Status in “xorg” source package in Karmic: Fix Committed
>
> Bug description:
> Binary package hint: xorg
>
> Recently some uploads to karmic-proposed were trying to fix the bulletproof-X support. These are still not working.
>
> Trying to manually run the failsafe X server you get:
> Warning: Could not generate /etc/X11/xorg.conf.failsafe for vesa driver
>
> Adding set -x, you can see why it's failing:
>
> + . /usr/share/debconf/confmodule
> + [ ! ]
> + PERL_DL_NONLAZY=1
> + export PERL_DL_NONLAZY
> + [ ]
> + exec /usr/share/debconf/frontend /etc/gdm/failsafeDexconf vesa xorg.conf
> + . /usr/share/debconf/confmodule
> + [ ! 1 ]
> + [ -z ]
> + exec
> + [ ]
> + exec
> + DEBCONF_REDIR=1
> + export DEBCONF_REDIR
> + SERVER=xorg
> + XF86CONFIG=/etc/X11/xorg.conf.failsafe
> + PROGNAME=failsafeDexconf
> + SHOWHELP=
> + EARLYEXIT=
> + getopt --options ho: --longoptions help,output: -n failsafeDexconf -- vesa xorg.conf
> + GETOPT_OUTPUT= -- 'vesa' 'xorg.conf'
> + [ 0 -ne 0 ]
> + eval set -- -- 'vesa' 'xorg.conf'
> + set -- -- vesa xorg.conf
> + :
> + shift
> + break
> + [ -n ]
> + [ -n ]
> + DEXCONFTMPDIR=
> + trap if [ -e "$DEXCONFTMPDIR/backup" ] && [ -n "$XF86CONFIG" ]; then \
> cat "$DEXCONFTMPDIR/backup" >"$XF86CONFIG"; \
> fi; \
> exec 4<&-; \
> rm -rf "$DEXCONFTMPDIR"; \
> bomb "received signal; aborting" HUP INT QUIT TERM
> + TDIR_PARENT=/tmp
> + TDIR=/tmp/dexconf-tmp-2459
> + [ ! -d /tmp ]
> + [ ! -w /tmp ]
> + rm -rf /tmp/dexconf-tmp-2459
> + mkdir -m 0700 /tmp/dexconf-tmp-2459
> + DEXCONFTMPDIR=/tmp/dexconf-tmp-2459
> + exec
> + cat
> + db_get xserver-xorg/config/device/driver
> + _db_cmd GET xserver-xorg/config/device/driver
> + IFS= printf %s\n GET xserver-xorg/config/device/driver
> + IFS=
> read -r _db_internal_line
> + RET=10 xserver-xorg/config/device/driver doesn't exist
> + return 10
>
> ProblemType: Bug
> Architecture: i386
> Date: Fri Nov 6 22:06:46 2009
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release i386 (20091027)
> Lsusb:
> Bus 001 Device 001: ID 1d6...

Read more...

Revision history for this message
Roman Fiedler (roman-fiedler-deactivatedaccount) wrote :

I see. Just for the records, my issue was fixed by:

cat <<EOF >> /var/cache/debconf/config.dat
Name: xserver-xorg/config/device/bus_id
Template: xserver-xorg/config/device/bus_id
Value:
Owners: xserver-xorg

EOF

Revision history for this message
b2ag (thomas-b2ag) wrote :

I have a problem and wonder if it has something in common with this bug. I have had karmic-purposed sources on and after one of the last updates Xorg keeps sending me to a failsafe-session instead of starting up properly. I hardly understand whats the problem, because restarting kdm results in X is coming up with the proper driver (not low graphics).

b2ag:~# grep xorg /var/cache/debconf/config.dat
zsh: exit 1 grep xorg /var/cache/debconf/config.dat

Revision history for this message
Bryce Harrington (bryce) wrote :
Download full text (5.1 KiB)

On Thu, Nov 12, 2009 at 06:43:59PM -0000, b2ag wrote:
> I have a problem and wonder if it has something in common with this bug.

Nope, this wouldn't cause that issue.

> I have had karmic-purposed sources on and after one of the last updates
> Xorg keeps sending me to a failsafe-session instead of starting up
> properly. I hardly understand whats the problem, because restarting kdm
> results in X is coming up with the proper driver (not low graphics).
>
> b2ag:~# grep xorg /var/cache/debconf/config.dat
> zsh: exit 1 grep xorg /var/cache/debconf/config.dat
>
> --
> Failsafe X support added in proposed upload still doesn't work
> https://bugs.launchpad.net/bugs/477149
> You received this bug notification because you are a bug assignee.
>
> Status in ???xorg??? package in Ubuntu: Fix Committed
> Status in ???xorg??? source package in Lucid: Fix Committed
> Status in ???xorg??? source package in Karmic: Fix Committed
>
> Bug description:
> Binary package hint: xorg
>
> Recently some uploads to karmic-proposed were trying to fix the bulletproof-X support. These are still not working.
>
> Trying to manually run the failsafe X server you get:
> Warning: Could not generate /etc/X11/xorg.conf.failsafe for vesa driver
>
> Adding set -x, you can see why it's failing:
>
> + . /usr/share/debconf/confmodule
> + [ ! ]
> + PERL_DL_NONLAZY=1
> + export PERL_DL_NONLAZY
> + [ ]
> + exec /usr/share/debconf/frontend /etc/gdm/failsafeDexconf vesa xorg.conf
> + . /usr/share/debconf/confmodule
> + [ ! 1 ]
> + [ -z ]
> + exec
> + [ ]
> + exec
> + DEBCONF_REDIR=1
> + export DEBCONF_REDIR
> + SERVER=xorg
> + XF86CONFIG=/etc/X11/xorg.conf.failsafe
> + PROGNAME=failsafeDexconf
> + SHOWHELP=
> + EARLYEXIT=
> + getopt --options ho: --longoptions help,output: -n failsafeDexconf -- vesa xorg.conf
> + GETOPT_OUTPUT= -- 'vesa' 'xorg.conf'
> + [ 0 -ne 0 ]
> + eval set -- -- 'vesa' 'xorg.conf'
> + set -- -- vesa xorg.conf
> + :
> + shift
> + break
> + [ -n ]
> + [ -n ]
> + DEXCONFTMPDIR=
> + trap if [ -e "$DEXCONFTMPDIR/backup" ] && [ -n "$XF86CONFIG" ]; then \
> cat "$DEXCONFTMPDIR/backup" >"$XF86CONFIG"; \
> fi; \
> exec 4<&-; \
> rm -rf "$DEXCONFTMPDIR"; \
> bomb "received signal; aborting" HUP INT QUIT TERM
> + TDIR_PARENT=/tmp
> + TDIR=/tmp/dexconf-tmp-2459
> + [ ! -d /tmp ]
> + [ ! -w /tmp ]
> + rm -rf /tmp/dexconf-tmp-2459
> + mkdir -m 0700 /tmp/dexconf-tmp-2459
> + DEXCONFTMPDIR=/tmp/dexconf-tmp-2459
> + exec
> + cat
> + db_get xserver-xorg/config/device/driver
> + _db_cmd GET xserver-xorg/config/device/driver
> + IFS= printf %s\n GET xserver-xorg/config/device/driver
> + IFS=
> read -r _db_internal_line
> + RET=10 xserver-xorg/config/device/driver doesn't exist
> + return 10
>
> ProblemType: Bug
> Architecture: i386
> Date: Fri Nov 6 22:06:46 2009
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release i386 (20091027)
> Lsusb:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: innotek GmbH VirtualBox
> Package: xorg 1:7.4+3ubuntu9
> PciDisplay:
> 00:02.0 VGA compatible contr...

Read more...

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

This bug was fixed in the package xorg - 1:7.4+3ubuntu10

---------------
xorg (1:7.4+3ubuntu10) karmic-proposed; urgency=low

  * local/Failsafe/failsafeXServer: Since dexconf no longer produces
    an xorg.conf, it will neither generate a failsafe xorg.conf, so now
    we just generate one directly. Otherwise X won't start a failsafe
    session properly.
    (LP: #477149)
 -- Bryce Harrington <email address hidden> Mon, 09 Nov 2009 15:39:57 -0800

Changed in xorg (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

(copied to lucid)

Changed in xorg (Ubuntu Karmic):
status: Fix Released → Fix Committed
Changed in xorg (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.4+3ubuntu10

---------------
xorg (1:7.4+3ubuntu10) karmic-proposed; urgency=low

  * local/Failsafe/failsafeXServer: Since dexconf no longer produces
    an xorg.conf, it will neither generate a failsafe xorg.conf, so now
    we just generate one directly. Otherwise X won't start a failsafe
    session properly.
    (LP: #477149)
 -- Bryce Harrington <email address hidden> Mon, 09 Nov 2009 15:39:57 -0800

Changed in xorg (Ubuntu Karmic):
status: Fix Committed → Fix Released
revolted (binarynerd01)
Changed in xorg (Ubuntu Lucid):
status: Fix Released → In Progress
Revision history for this message
Steve Langasek (vorlon) wrote :

please don't change bug statuses without explanation.

Changed in xorg (Ubuntu Lucid):
status: In Progress → Fix Released
Revision history for this message
Andis Grosšteins (andis-grossteins) wrote :

this bug may not be fixed in karmic xorg - 1:7.4+3ubuntu10

Caught this while trying to enable nvidia drivers for my old geforce4 and got in failsafe mode.
here is what dexconfig (presumably) generates after selecting reconfigure and reset to defaults:

Section "Device"
 Identifier "Configured Video Device"
 BusID "10 xserver-xorg/config/device/bus_id doesn't exist"
EndSection

I removed the BusID line in failsafe dialogue, returned to shell login (tty1) and ran sudo service gdm start.
Now X works with default config.

Revision history for this message
Andis Grosšteins (andis-grossteins) wrote :

log file from the moment after xorg.conf was generated

Bryce Harrington (bryce)
Changed in xorg (Ubuntu Karmic):
assignee: Bryce Harrington (bryceharrington) → nobody
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.