View Single Post
Old 06-30-08, 12:22 PM   #16
Registered User
Join Date: Feb 2006
Posts: 12
Default Re: Spawning new session leads to crash

Originally Posted by AaronP View Post
According to your log, you don't have it enabled, which leads me to believe that your crash is different from the rest. You'd see "Backing store enabled" in Xorg.0.log if it were enabled. Please do try the vesa driver, though, since the backtrace you pasted doesn't involve the NVIDIA driver at all.
The problem seems to be specific to the nvidia driver; I get no crash when switching sessions using the VESA driver.

There are 2 related Debian bugs: and 432101. 445322 is mine. As you say, and as noted there, nvidia does not appear in the stack trace for me (it does for the other bug, and other reports in this thread). The Debian X maintainers thought it possible nvidia was on my stack in an obfuscated way. Or perhaps the driver writes somewhere else, but isn't on the stack when the crash occurs--or maybe nvidia is just exposing an issue elsewhere.

My initial report seems to have been with xorg 1.3, which predates the version you mentioned earlier.

I would love to fix this. Let me know what I can do.

Here's the backtrace from my latest crash (with nvidia driver):
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Jun 30 09:33:16 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ddc" already built-in
(EE) Failed to load module "type1" (module does not exist, 0)
(II) Module "ramdac" already built-in

0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c913e]
1: [0xffffe420]
2: /usr/bin/X(ProcPolyPoint+0x13a) [0x808aeca]
3: /usr/bin/X [0x81547a4]
4: /usr/bin/X(Dispatch+0x314) [0x808dde4]
5: /usr/bin/X(main+0x4b5) [0x8074765]
6: /lib/i686/cmov/ [0xb7d21450]
7: /usr/bin/X(FontFileCompleteXLFD+0x219) [0x8073a51]

Fatal server error:
Caught signal 11. Server aborting

Could not init font path element unix/:7100, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!

I think that's about the same as before.

I suppose since it's the original session that's dying, Xorg.0.log would be more relevant. Unfortunately, it gets overwritten when the new session starts.
RossBoylan is offline   Reply With Quote