|
KAtomic ... well, blows up!
M'kay, this is really more about figuring out how to troubleshoot X applications than it is about needing to play a particular game ...
I try to make a habit of occasionally roaming around the menus on my [-current] system and trying apps I've never run before. Tonight it was the game "KAtomic." I was running XFCE. I tried running the game and BLAM! X died. I saw some disturbing lines at the top of the screen, what looked like the tail end of a series of numbered lines of errors specific to X. Then I tried changing my wm to KDE, since KAtomic -- sporting the ubiquitous 'K', was obviously a KDE app. Even worse. Under KDE, starting the game using the menus resulted in a frozen system. I couldn't even CTRL-ALT-BACKSPACE out of X ... the system was hung. Once I was back up and running, I tried starting KAtomic from a terminal in fluxbox, and redirected standard error to a file. Here is what it contains: kbuildsycoca running... katomic: Fatal IO error: client killed kdeinit: Fatal IO error: client killed klauncher: Exiting on signal 15 kded: Fatal IO error: client killed Now, the thing is, not only is that not terribly specific, but I know there is other, more specific error-gunk that X is spitting out as it dies, since I can see it at the top of my screen once I am back at a prompt. I am wondering how to get all of THAT stuff. Is there another way to capture it? It doesn't seem to be in the X.org.log, nor in syslog. I admit, I am grasping at straws, and am not sure where to look for more information. Thx, Glenn |
Usually the error logs come from the verbosity of the program, I mean if there is no error checking or no error message when the program fails in one function then there is no direct error output from the program
The <<katomic: Fatal IO error: client killed>> error seems to come from QT library (the library that provides GUI elements, like menu, buttons etc), but not from the program itself If you are curious, you could use << gdb katomic>>, then type <<run>> and look gdb output until the program stops, then you can type <<where>> to try to find out more.. But the program surelly has debug symbols stripped so it won't talk much. I have seen X locks from various reason also, often the x video driver caused problem, but that depends on your video card and driver though. |
Quote:
(No debugging symbols found) and then after a couple of returns, KAtomic runs and dies and pulls X down and, of course, my gdb session with it. :( I tried from pure console but since KAtomic is a KDE app it can't be debugged/run without X running. Sure wish I could capture what X is spitting out upon death. I thought that went SOMEwhere ... but I can't find it. I will run KAtomic and try to copy down a couple of the lines with a pen[cil], maybe someone will recognize something ... there's gotta be a better way! |
Maybe look into your logs: /var/log/Xorg.0.log or /var/log/Xorg.0.log.old
Or start X with output redirected to a file : Code:
startx > ~/Xerrors 2>&1 |
Quote:
xauth: creating new authority file /home/chexmix/.serverauth.4112 X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Slackware 12.1 Slackware Linux Project Current Operating System: Linux catbutt 2.6.27.5-smp #1 SMP Fri Nov 7 12:52:17 CST 2008 i686 Build Date: 30 June 2008 11:35:29PM 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.0.log", Time: Sun Nov 9 19:51:24 2008 (==) Using config file: "/etc/X11/xorg.conf" (II) Module "ddc" already built-in failed to open catalog, using default messages Backtrace: 0: X(xf86SigHandler+0x7e) [0x80d8b5e] 1: [0xffffe400] 2: /usr/X11R6/lib/libpixman-1.so.0 [0xb7fc9787] 3: /usr/X11R6/lib/libpixman-1.so.0 [0xb7fcd910] 4: /usr/X11R6/lib/libpixman-1.so.0(pixman_image_composite+0x59c) [0xb7fcd52c] 5: /usr/lib/xorg/modules//libfb.so(fbComposite+0x1ad) [0xb7b002dd] 6: X [0x81688f3] 7: X(CompositePicture+0x150) [0x814fc10] 8: X(miGlyphs+0x233) [0x814c753] 9: X [0x8168704] 10: X(CompositeGlyphs+0x9a) [0x814fd8a] 11: X [0x8157648] 12: X [0x8152aa5] 13: X [0x814620e] 14: X(Dispatch+0x2bf) [0x808688f] 15: X(main+0x48b) [0x806ddab] 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7e37390] 17: X(FontFileCompleteXLFD+0x20d) [0x806d121] Fatal server error: Caught signal 11. Server aborting XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 11462 requests (11462 known processed) with 0 events remaining. xinit: connection to X server lost. waiting for X server to shut down xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0" |
I would try disable the composite extension in xorg.conf, just for checking
Just add these lines at the end of /etc/X11/xorg.conf: Code:
Section "Extensions" |
Quote:
I will have to look into these extensions. Maybe my system (a 1000 mHz PIII) just is too old to take advantage of them? I don't know anything about them. :study: Again, thanks for your help with this, keefaz! |
| All times are GMT -5. The time now is 10:35 PM. |