https://bugzilla.novell.com/show_bug.cgi?id=216149 ------- Comment #28 from rschulz@sonic.net 2006-10-31 17:49 MST ------- Another update: With the nVidia proprietary driver version 8774 the symptom occurs in the same manner and after approximately the same amount of elapsed time as with the open driver. The diagnostics in ~/.xsession-errors are the same as with the nv driver. Furthermore, those same diagnostics are recorded when trying to launch applications once the first application crash occurs. To wit: The program 'galculator' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 960 error_code 11 request_code 53 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.) Another thing I'll note is that it seems that already running applications die upon switching from one virtual desktop _to_ the one on which they're displayed. That certainly characterizes the GKrellM and Firefox crashes. The "mtrr" diagnostic does not occur when applications die. This time I could not induce the entire session to die, but KWin crashed. When I finally ended the session, /var/log/messages did record this message: Oct 31 16:47:03 smiley kernel: mtrr: type mismatch for c0000000,10000000 old: uncachable new: write-combining RRS -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.