xinerama xserver crash

Bug #144777 reported by Michael Wood
14
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Undecided
Unassigned
xorg (Ubuntu)
Invalid
Unknown
Unassigned

Bug Description

Binary package hint: xserver-xorg
Binary package hint: xserver-xorg-core

A recent upgrade to gutsy seems to have caused xinerama to crash the X server

Linux 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

Here is my trace.

(gdb) Reading symbols from /usr/bin/Xorg...Log written to: /tmp/gdb_log.27307
michael@fornax:~/scripts$ Reading symbols from /usr/lib/debug/usr/bin/Xorg...done.
Using host libthread_db library "/lib/libthread_db.so.1".
done.
(gdb) (gdb) Signal Stop Print Pass to program Description
SIGUSR1 No Yes Yes User defined signal 1
(gdb) Signal Stop Print Pass to program Description
SIGUSR2 No Yes Yes User defined signal 2
(gdb) Signal Stop Print Pass to program Description
SIGPIPE No Yes Yes Broken pipe
(gdb) Starting program: /usr/bin/Xorg :9 -config /etc/X11/xorg.conf-wxinerama

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
Current Operating System: Linux fornax 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64
Build Date: 21 September 2007
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.9.log", Time: Tue Sep 25 14:52:02 2007
(++) Using config file: "/etc/X11/xorg.conf-wxinerama"
(II) Module already built-in
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success

Program received signal SIGSEGV, Segmentation fault.
PanoramiXCreateConnectionBlock () at ../../Xext/panoramiX.c:711
711 ../../Xext/panoramiX.c: No such file or directory.
        in ../../Xext/panoramiX.c
(gdb) Undefined command: "module". Try "help".
(gdb) #0 PanoramiXCreateConnectionBlock () at ../../Xext/panoramiX.c:711
#1 0x0000000000439f40 in main (argc=4, argv=0x7fff678eef18,
    envp=<value optimized out>) at ../../dix/main.c:468
(gdb) Continuing.

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x6d) [0x48670d]
1: /lib/libc.so.6 [0x2b86441157d0]
2: /usr/bin/Xorg(PanoramiXCreateConnectionBlock+0x155) [0x5079c5]
3: /usr/bin/Xorg(main+0x450) [0x439f40]
4: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b8644101b44]
5: /usr/bin/Xorg(FontFileCompleteXLFD+0x231) [0x439249]

Fatal server error:
Caught signal 11. Server aborting

Program received signal SIGABRT, Aborted.
0x00002b8644115765 in raise () from /lib/libc.so.6

Revision history for this message
Michael Wood (x3n) wrote :

Xorg config used to replicate crash

description: updated
Revision history for this message
Michael Wood (x3n) wrote :

Here is the standard log file that X creates

I tried disabling randr, based on the knowledge that previous versions of xinerama didn't support it but I still get the same crash.

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

I think you're right that -nvidia does not yet support xrandr. Xinerama ought to work though.

Have you tried the other two -nvidia binary drivers?

Changed in xorg:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

Michael,

-nvidia also has a TwinView mode (see http://ubuntuforums.org/showthread.php?t=221174 for directions) you could test.

Of course, this still doesn't explain why xinerama suddenly stopped working. Could you test booting the gutsy live-cd, apply your xorg.conf, restart X, and see if you can recreate the issue in that environment? If so, then also test against the tribe-5 live-cd. This will help rule out if recent (post-tribe-5) work is what caused the issue.

Revision history for this message
Michael Wood (x3n) wrote :

On the default install of gutsy xinerama worked fine with the nvidia driver, I don't know which version of it comes with gutsy tribe 5 or if it's one of the packages which has been changed - All this info must be in launchpad i'm sure... somewhere...

I did try installing nvidia-glx-legacy but it wouldn't load because there was a module/driver version missmatch, i didn't chase up that possibility much further as it seemed that the cards worked individually fine.

Revision history for this message
Michael Wood (x3n) wrote :

I booted into the live cd and successfully configured and ran a xinerama setup using the nvidia drivers

Here is a summary of the packages which are different that might be causing this crash:

--- Package Name ----|-- Live CD -- | -- Install -- |
xsever-xorg | ubuntu patch 6 | ubuntu patch 10
linux-restricted-modules-common | 2.6.22-3.10.1 | 2.6.22-4.12.3
linux-restricted-modules-'uname -r' | 2.6.22.3-10.1 | 2.6.22.4-12.3 *

* which is providing nvidia kernels:
 - Livecd Provides: nvidia-kernel-1.0.9639, nvidia-kernel-1.0.7185, nvidia-kernel-100.14.11
 - Current Install Provides: nvidia-kernel-1.0.9639, nvidia-kernel-1.0.7185, nvidia-kernel-100.14.19

libxinerama1 same same
nvidia-glx same same

I have tried booting into the original gutsy kernel 2.6.22-10, but i'm unable to install the linux-restricted-modules-2.6.22-10 as it's been taken out of the repository.
"Package linux-restricted-modules-2.6.22-10-generic has no available version, but exists in the database."

I don't think twinview is really any option for people who don't have a multihead graphics card, I believe it relies on both heads being on the one board, where as with my setup, and others, there are actually 2 physical graphics cards.

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

Canceling the xorg package since this seems to be l-r-m specific.

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Confirmed
Changed in xorg:
status: New → Invalid
Revision history for this message
Michael Wood (x3n) wrote :

I've done some more investigation;

Downgrading the following packages

./xserver-xorg_7.2-5ubuntu6_all.deb
./xserver-xorg-core_1.3.0.0.dfsg-6ubuntu3_amd64.deb
./xserver-xorg-input-all_7.2-5ubuntu6_amd64.deb

Allowed me to get as far as starting X with xinerama and nvidia (no crash this time unlike initial report). unfortunately gdm breaks instead:

The program 'gdm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1 error_code 9 request_code 55 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
gdm[9191]: WARNING: failsafe dialog failed (inhibitions: 0 0)
The program 'gdm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1 error_code 9 request_code 55 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
gdm[9191]: WARNING: failsafe dialog failed (inhibitions: 0 1)
The program 'gdm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1 error_code 9 request_code 55 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
gdm[9191]: WARNING: failsafe dialog failed (inhibitions: 1 1)

and from /var/log/gdm/:0
AUDIT: Sun Oct 7 02:26:13 2007: 9662 X: client 2 rejected from local host (uid 108)

I tried to roll back even further to try and get nearer and nearer the live cd downgrading to the following from tribe 5:

gdm_2.19.6-0ubuntu3_amd64.deb
libx11-6_1.1.1-1ubuntu3_amd64.deb
libx11-data_1.1.1-1ubuntu3_all.deb
libxinerama1_1.0.2-1build1_amd64.deb
linux-restricted-modules-common_2.6.22.3-10.1_all.deb
linux-restricted-modules-generic_2.6.22.10.11_amd64.deb
nvidia-kernel-common_20051028+1ubuntu7_all.deb
x11-common_7.2-5ubuntu6_amd64.deb
xauth_1.0.2-0ubuntu1_amd64.deb
xbase-clients_7.2-5ubuntu6_all.deb
xorg_7.2-5ubuntu6_amd64.deb
xserver-xorg_7.2-5ubuntu6_all.deb
xserver-xorg-core_1.3.0.0.dfsg-6ubuntu3_amd64.deb
xserver-xorg-input-all_7.2-5ubuntu6_amd64.deb
xset_1.0.2-0ubuntu1_amd64.deb
xsetmode_1.0.0-0ubuntu2_amd64.deb
xutils_7.2-5ubuntu6_all.deb

However this didn't fix the issue i had with gdm.

Revision history for this message
Michael Wood (x3n) wrote :

changing the xorg-xserver packages back to tribe 5 of gutsy changed something so i'm adding it back in

Changed in xorg:
status: Invalid → New
Revision history for this message
Tux541 (jakepi) wrote :

I am having the exact same issues. I have also tried downgrading my nvidia drivers and that did not work either. Any solution yet? If I just start X manually as my user with Xinerama enabled the system works fine yet GDM crashes. If I disable just Xinerama GDM works great again. Just wanted to add that I noticed in my syslog gdmgreeter is segfaulting with error 4 and so is compiz.real with an error 4.

Revision history for this message
Michael Wood (x3n) wrote :

un-confirmed

Changed in linux-restricted-modules-2.6.22:
status: Confirmed → New
Revision history for this message
Michael Wood (x3n) wrote :
Revision history for this message
Michael Wood (x3n) wrote :

I compiled xorg-server-X11R7.2-1.2.0 from source [1] this initially did not fix the problem as on it's own the xserver would not load any of the modules specified in my configuration or find fonts, (probably because the compiled xserver wasn't installed in the right location, using the correct --prefix when doing ./configure should fix this) then i used checkinstall and this worked in that I can now start gdm with xinerama (though i can not start X on it's own)

unfortunately i've tried so many things to get this working now that I can't be sure which has fixed it, but as far as i can see installing xserver from the latest source has fixed this bug. Either because it has been fixed by the freedesktop people or has un-done an ubuntu patch.

[1] http://xorg.freedesktop.org/archive/X11R7.3/src/xserver/

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

(Leaving at incomplete until further testing identifies what change causes the fix)

calc reported a backtrace with nvidia when enabling xinerama, but it's a bit different from what was reported before:

<calc> Backtrace:
 0: /usr/bin/X(xf86SigHandler+0x6a) [0x483d5a]
 1: /lib/libc.so.6 [0x2b099b4e6100]
 2: /lib/libc.so.6(realloc+0x79) [0x2b099b52bd79]
 3: /usr/bin/X(Xrealloc+0x1b) [0x56753b]
 4: /usr/bin/X [0x4bdde9]
 5: /usr/lib/xorg/modules/drivers//nvidia_drv.so [0x2b099e1ae7a3]

This was after doing a software update over the holiday break; prior to the holidays his configuration worked correctly.

Changed in linux-restricted-modules-2.6.22:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Michael Wood (x3n) wrote :

I some what naively applied the current updates:

date time action package from_version to_version

2008-01-18 02:37:59 upgrade x11-common 1:7.2-5ubuntu6 1:7.2-5ubuntu13
2008-01-18 02:38:00 upgrade xserver-xorg-core 2:1.3.0.0.dfsg-6ubuntu3 2:1.3.0.0.dfsg-12ubuntu8
2008-01-18 02:38:01 upgrade xserver-xorg-input-all 1:7.2-5ubuntu6 1:7.2-5ubuntu13
2008-01-18 02:38:01 upgrade xutils 1:7.2-5ubuntu6 1:7.2-5ubuntu13
2008-01-18 02:38:01 upgrade xbase-clients 1:7.2-5ubuntu6 1:7.2-5ubuntu13
2008-01-18 02:38:09 upgrade xserver-xorg 1:7.2-5ubuntu6 1:7.2-5ubuntu13
2008-01-18 02:38:11 upgrade xorg 1:7.2-5ubuntu6 1:7.2-5ubuntu13

This reverted me back to square one /see initial report/ this time instead of trying to roll back all of the above packages I did it one by one checking to see if the problem occured (each time I /etc/init.d/gdm restart ed) until i finally got to xserver-xorg-core, installing this upgraded package caused the problem. none of the others had any affect. So we can finally pin point the package which causes this.

xserver-xorg-core-2:1.3.0.0.dfsg-6ubuntu3 WORKS
xserver-xorg-core-2:1.3.0.0.dfsg-12ubuntu8 BROKEN

now to find the crucial difference...

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Invalid
Changed in xorg-server:
status: New → Confirmed
Michael Wood (x3n)
description: updated
Changed in linux-restricted-modules-2.6.22:
status: Invalid → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try Hardy alpha3 too. It'd be great to find out which patch broke it for you. It's likely that some patch introduced in 12ubuntu3 is the reason. Try disabling all of them and build the package.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Closing for xorg component, leaving xorg-server.

Changed in xorg:
importance: High → Unknown
status: Confirmed → Invalid
Revision history for this message
Michael Wood (x3n) wrote :

I dared another upgrade

xserver-xorg-core-2:1.3.0.0.dfsg-6ubuntu3 WORKS
xserver-xorg-core-2:1.3.0.0.dfsg-12ubuntu8 BROKEN
xserver-xorg-core-2:1.3.0.0.dfsg-12ubuntu8.3 WORKS ! (19-Jan-2008 release)

I've looked through the changelog but I'm not familiar enough with xserver-xorg, also massive number of patches since it stopped working and now makes finding it like looking for a neadle in a haystack using a neadle.

less patches please ;)

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

If I've understood correctly, the security patches have fixed this issue? This was reported on hardy as well, before those patches. Reopen if it's still broken with current Hardy.

Changed in xorg-server:
status: Confirmed → Fix Released
Revision history for this message
Michael Wood (x3n) wrote :

Just re-tested on Hardy, Hardy Alpha 6 does not suffer from this bug.

Revision history for this message
aidave (aidave) wrote :

Adding the Xinerama line to xorg.conf causes a startup crash for me.
Hardy Alpha 6

Revision history for this message
Michael Wood (x3n) wrote :

could you attach your /etc/X11/xorg.conf and a copy of the log file from /var/log/Xorg.0.log after your crash. note that the log file needs to be from the crash time rather than when you have successfully loaded X.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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