ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #33342
[Bug 477149] [NEW] Failsafe X support added in proposed upload still doesn't work
Public bug reported:
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu Lucid)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu Karmic)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
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 member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
Follow ups
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Bryce Harrington, 2010-03-25
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Andis Grosšteins, 2010-03-21
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Andis Grosšteins, 2010-03-21
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Steve Langasek, 2010-01-31
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: revolted, 2010-01-31
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Launchpad Bug Tracker, 2009-11-30
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Steve Langasek, 2009-11-30
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Launchpad Bug Tracker, 2009-11-30
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: b2ag, 2009-11-12
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Roman Fiedler, 2009-11-12
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Roman Fiedler, 2009-11-11
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Mario Limonciello, 2009-11-11
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Roman Fiedler, 2009-11-11
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Martin Pitt, 2009-11-10
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Bryce Harrington, 2009-11-09
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Mario Limonciello, 2009-11-08
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Bryce Harrington, 2009-11-08
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Mario Limonciello, 2009-11-07
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Bryce Harrington, 2009-11-07
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Bryce Harrington, 2009-11-07
-
[Bug 477149] Re: Failsafe X support added in proposed upload still doesn't work
From: Mario Limonciello, 2009-11-07
-
[Bug 477149] [NEW] Failsafe X support added in proposed upload still doesn't work
From: Mario Limonciello, 2009-11-07
References