I'm getting a quite repeatable error whe xscreensaver fires up (at least, every time I leave the laptop in xscreensaver mode, when I'm back to work I see kdm screen, not the xscreensaver lock. Below you can find the logs, please note that the firs line happens quite before the firs (EE) line. [ 18504.944] (II) intel(0): switch to mode 1680x1050@60.0 on pipe 1 using VGA1, position (1366, 0), rotation normal [ 21791.795] (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable [ 27140.348] (EE) [ 27140.348] (EE) Backtrace: [ 27140.348] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57e8ad] [ 27140.348] (EE) 1: /usr/bin/X (0x400000+0x1824f9) [0x5824f9] [ 27140.348] (EE) 2: /lib64/libpthread.so.0 (0x7f1c20030000+0x106b0) [0x7f1c200406b0] [ 27140.348] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f1c1d9f1000+0x2bfe2) [0x7f1c1da1cfe2] [ 27140.348] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f1c1d9f1000+0x2c50b) [0x7f1c1da1d50b] [ 27140.348] (EE) 5: /usr/bin/X (0x400000+0x10f04a) [0x50f04a] [ 27140.348] (EE) 6: /usr/bin/X (0x400000+0x36d81) [0x436d81] [ 27140.348] (EE) 7: /usr/bin/X (0x400000+0x3a82e) [0x43a82e] [ 27140.348] (EE) 8: /usr/bin/X (0x400000+0x29fba) [0x429fba] [ 27140.348] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f1c1eebbc05] [ 27140.348] (EE) 10: /usr/bin/X (0x400000+0x2a301) [0x42a301] [ 27140.348] (EE) [ 27140.348] (EE) Segmentation fault at address 0x0 [ 27140.348] (EE) Fatal server error: [ 27140.348] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 27140.348] (EE) [ 27140.348] (EE)
Without debug symbols, that trace is useless.
I see your point. I recompiled both xorg and intel driver with debug options (-ggdb), however it seems to happen only with two monitor connected (or I'm out of luck). In two-three days I hope to be able to provide more significant data. Thanks.
*** This bug has been marked as a duplicate of bug 71415 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.