Bug 2594

Hi! 
 
I'm seeing this bug with x.org 6.8.2.dfsg.1-6, KDE 3.4.2-2 (both Debian 
packages) and NVidia proprietary drivers 7676. I tried to gather some 
information to track this down, but didn't come up with    
too much:    
   
/var/log/Xorg.0.log:   
---   
   
   *** If unresolved symbols were reported above, they might not   
   *** be the reason for the server aborting.   
   
Fatal server error:   
Caught signal 11.  Server aborting   
   
   
Please consult the The X.Org Foundation support    
         at http://wiki.X.Org   
 for help.    
Please also check the log file at "/var/log/Xorg.0.log" for additional   
information.   
   
---   
   
Nothing unusual info before that, except (quite possibly unrelated):   
   
---   
(II) Loading sub module "fb"   
(II) LoadModule: "fb"   
(II) Loading /usr/X11R6/lib/modules/libfb.a   
Skipping "/usr/X11R6/lib/modules/libfb.a:fbmmx.o":  No symbols found   
(II) Module fb: vendor="X.Org Foundation"   
        compiled for 6.8.2, module version = 1.0.0   
        ABI class: X.Org ANSI C Emulation, version 0.2   
---   
   
In ~/.xsession-errors there's slightly more:  
  
---  
[...lots of similar errors...]  
error 3 request 20 minor 0 serial 491345  
error 3 request 20 minor 0 serial 494557  
error 3 request 20 minor 0 serial 494558  
error 9 request 161 minor 1 serial 494719  
error 3 request 129 minor 6 serial 494720  
error 3 request 20 minor 0 serial 494721  
error 3 request 20 minor 0 serial 494722  
error 3 requekio (KIOConnection): ERROR: Header read failed, errno=104  
kio (KIOConnection): ERROR: Header has invalid size (-1)  
X Error: BadWindow (invalid Window parameter) 3  
  Major opcode:  20  
  Minor opcode:  0  
  Resource id:  0x400050  
X Error: BadWindow (invalid Window parameter) 3  
  Major opcode:  20  
  Minor opcode:  0  
  Resource id:  0x400050  
X Error: BadWindow (invalid Window parameter) 3  
  Major opcode:  20  
  Minor opcode:  0  
  Resource id:  0x400050  
X Error: BadWindow (invalid Window parameter) 3  
  Major opcode:  20  
  Minor opcode:  0  
  Resource id:  0x400050  
kio (KIOConnection): ERROR: Could not write data  
kio (KIOConnection): ERROR: Could not write data  
amarok: Fatal IO error: client killed  
kio_uiserver: Fatal IO error: client killed  
klipper: Fatal IO error: client killed  
kded: Fatal IO error: client killed  
KWrited - Listening on Device /dev/pts/0  
kicker: Fatal IO error: client killed  
[...KDE apps terminate one by one after this...]  
---  
  
Let me know if I can provide more information.  
  
Thanks for looking into this.  
  
Regards,  
   Georg 

6.9 and 7.0 can print their own backtraces, which helps greatly in debugging
problems like this.  can you reproduce this on current X servers?

Yes, I still get the bug on X.org 7.0 (with nVidia drivers 8174). 
I also tried it on Looking Glass, and on Looking Glass there is no crash ! 
I'm going to send the backtrace when I get one. 

I can't get this bug any longer using the X.org 7.0rc4 provided with Dapper,    
KDE 3.5 and latest nVidia drivers. That's one of the latest updates of X.org 
in Dapper that solved the problem... (I was a bit late on some updates) 

This crash still occurs on me. 
If the balloon is enabled, X will crash when I click on 'Reply'. If it is 
disabled, X crashes as soon as a message is received 
 
I don't know how to produce a backtrace, but I found this in my logs: 
 
AUDIT: Fri Feb  3 12:20:06 2006: 11817 X: client 2 rejected from local host  
AUDIT: Fri Feb  3 12:20:06 2006: 11817 X: client 3 rejected from local host  
  
   *** If unresolved symbols were reported above, they might not  
   *** be the reason for the server aborting.  
  
Backtrace:  
0: /usr/bin/X(xf86SigHandler+0x94) [0x4783f4]  
1: /lib/libc.so.6 [0x2aaaab6e2890]  
2: /usr/lib64/xorg/modules/drivers/nvidia_drv.so(_nv000117X+0x3e)  
[0x2aaaacbbb3ee]  
  
Fatal server error:  
Caught signal 11.  Server aborting  
 
HTH. 
  

Silly me. I forgot to mention: Xorg 7.0, Kde 3.5.1 and nvidia binaries 8178  
from gentoo ebuilds. 
 

Same problem here, 

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x82) [0x4775c2]
1: /lib/libc.so.6 [0x2b8ff99a83e0]
2: [0x8baa80]

Fatal server error:
Caught signal 11.  Server aborting

Getting the same issue on X.org 6.9.0, Nvidia 8762 drivers and KDE 3.5.3.

I have the same problem with X.org 7.0-r1, kde 3.5.2, and Nvidia drivers 1.0-
8762. It also crahes X when just opening a chat window to start with.

Does not happen anymore with:
Xorg 7.1
KDE 3.5.4
nvidia binary drivers 1.0.8774

So I guess the bug can be marked as Fixed?

Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.

hi,
my system is still affected by this bug using xorg 7.3, kde 3.5.8 and nvidia drivers 169.09:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x4736b2]
1: /lib/libc.so.6 [0x2b5e22887430]
2: /usr/lib64/xorg/modules/drivers//nvidia_drv.so(_nv000759X+0x68) [0x2b5e253fa908]

Fatal server error:
Caught signal 11.  Server aborting

This also happens here (Sidux/Debian Sid) with:
Xorg 7.3+10
Compiz Fusion 0.7.3+git20080320.shame-1
KDE 3.5.9
Nvidia driver 169.12

Xorg backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c66ee]
1: [0xb7f81420]
 
Fatal server error:
Caught signal 11.  Server aborting

Bug occurs on my system (openSUSE 10.3, KDE 3.5.9, xorg 7.2, nvidia 169.09).  I'm willing to help diagnose the problem if someone tells me what information they need.

Also, would be interested in hearing any workarounds, as this bug is annoying as hell.  (I use two computers, one with the bug and one without, and thus often forget to avoid clicking on the IM balloon.)

It occurs on my system as well.  If it makes a difference, it only just started occurring when I upgraded from Kubuntu 7.10 to 8.04, so it's probably something within this upgrade.

If you need any additional information that you think I could provide you, just let me know.

A lot has changed in six years.  I don't think kompmgr is even a thing anymore.  If anyone is still seeing a crash running kopete with compositing enabled please file a new bug.