(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
this message in Xorg.0.log appears to be key. If I lower the virtual res in xorg.conf, I don't get the crash. If I subsequently set NoAccel, I still don't get the crash. It's only when I have my usual virtual res set (2960x1850) do I see the error. (This system doesn't work with UXA, so don't ask me to test that. :)
The first time I try to run totem, it errors out with this message:
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 76 error_code 11 request_code 132 minor_code 19)
(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.)
There is a corresponding error in Xorg.0.log:
(EE) intel(0): Failed to pin xv buffer
And then the second totem invocation will crash X.
Have twiddled a few knobs, and:
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
this message in Xorg.0.log appears to be key. If I lower the virtual res in xorg.conf, I don't get the crash. If I subsequently set NoAccel, I still don't get the crash. It's only when I have my usual virtual res set (2960x1850) do I see the error. (This system doesn't work with UXA, so don't ask me to test that. :)
The first time I try to run totem, it errors out with this message:
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 76 error_code 11 request_code 132 minor_code 19)
(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.)
There is a corresponding error in Xorg.0.log:
(EE) intel(0): Failed to pin xv buffer
And then the second totem invocation will crash X.