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

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.

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

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!

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

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.

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.

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...

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

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

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...

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

(copied to lucid)

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

please don't change bug statuses without explanation.

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.

log file from the moment after xorg.conf was generated