I'm getting what i believe is this same bug in an almost-up-to-date feisty (last update 8 march 2007). xorg dies with this in Xorg.0.log.old:
----
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d81]
1: [0xb7fbe420]
Fatal server error:
Caught signal 11. Server aborting
----
was dying mysteriously at 11 minute intervals, apparently becaue the screensaver was turned on (i switched to 'random' from 'display photos', and promptly forgot i'd done so). I can now reliably produce the crash by trying to start beryl, googleearth, various screensaver, glxinfo, or any other 3d programs. i'm using
xserver-xorg-core 2:1.2.0-3ubuntu3
nvidia 9746 (using nvidia installer)
millions of other possible packages.
3d worked fine on this computer for about 2 months until about 2 weeks ago (time frames approximate); maybe this is a regression in recent xorg releases?
would like to include apport bug traces but not sure how to do that manually; please suggest a method if you think such a trace would be of use.
forum activity in the last couple of weeks suggest the bug may still persist for other users too:
I'm getting what i believe is this same bug in an almost-up-to-date feisty (last update 8 march 2007). xorg dies with this in Xorg.0.log.old: X(xf86SigHandle r+0x81) [0x80c5d81]
----
Backtrace:
0: /usr/bin/
1: [0xb7fbe420]
Fatal server error:
Caught signal 11. Server aborting
----
was dying mysteriously at 11 minute intervals, apparently becaue the screensaver was turned on (i switched to 'random' from 'display photos', and promptly forgot i'd done so). I can now reliably produce the crash by trying to start beryl, googleearth, various screensaver, glxinfo, or any other 3d programs. i'm using
xserver-xorg-core 2:1.2.0-3ubuntu3
nvidia 9746 (using nvidia installer)
millions of other possible packages.
3d worked fine on this computer for about 2 months until about 2 weeks ago (time frames approximate); maybe this is a regression in recent xorg releases?
would like to include apport bug traces but not sure how to do that manually; please suggest a method if you think such a trace would be of use.
forum activity in the last couple of weeks suggest the bug may still persist for other users too: