dualhead + locking system xorg crashes (915GM) (i810 driver)

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xorg.

Sorry for forgetting the package.
I think that is not only xorg but the combination of xorg and gnome-screensaver
because when i go to the screensaver settings and set the screensaver to blank screen the problem is fixed.
Also i've attched the logging of xorg when my screensaver is turned on.

 These are the last entry's in de loggiong

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!
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?
ProcXCloseDevice to close or not ?
SetGrabKeysState - disabled

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state_locked+0x7e1) [0x9768df91]
3: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state+0x2a) [0x9768e0ea]
4: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Clear+0x17e) [0x97620dbe]
5: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c25a08]
6: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0x155) [0xb7c1e625]
7: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c1e6bc]
8: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c22b2c]
9: /usr/bin/X [0x815754e]
10: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
11: /usr/bin/X(main+0x495) [0x8076f05]
12: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d9c050]
13: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Extended BIOS function 0x5f64 failed.
(WW) I810(0): Failed to set display devices to 0x800.
(WW) I810(0): Enabling LVDS directly. Pipe B.
(WW) I810(0): Disabling ADPA directly.
(WW) I810(0): Writing config directly to SWF0.
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
        the saved state
(--) I810(0): A non-CRT device is attached to pipe B.
        No refresh rate overrides will be attempted.
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method.
(II) I810(0): xf86UnbindGARTMemory: unbind key 5
(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 3
(II) I810(0): xf86UnbindGARTMemory: unbind key 4
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(WW) I810(0): Successfully set original devices (2)

Sorry for the confusion in changing titles, I read someone else's Xorg.0.log by mistake.

Could you test and see if the problem is still present with the "intel" driver please.

The problem was first noticed by me when i used the intel drivers.
But i had an old xorg config so i tried it with the i810 drivers.

So the problem is not driver related. i've have the problems with the intel (experimental drivers) and the old i810 drivers.

But I've have an other laptop (acer 9300 series) this system has a G-force mobile cart and it's giving the same problem. when is use it in dualhead modus (two screens).

Could you post the log of the crash for the intel driver if possible? (I'm more familiar with that codebase, so it is more useful to see that backtrace, even if its a common bug elsewhere in the stack).

Is the G-force backtrace the same? If so, post that too, and we might have to look at whether we're seeing a core Xorg bug.

When i us the intel driver my laptop is crashing like hell.
So i gona restore the original xorg.conf that uses the intel drivers.
Convert it to a dual screen conf and post the error logging.

Also if update gnome-screensaver. (security update form ubuntu 10-20-2007) but it didn't change the problem

I experience this problem on an IBM ThinkPad T42 which has an ATI Radeon Mobility 7500 using the "ati" driver. Backtrace in Xorg.0.log is almost identical, but here it is:

----
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state_locked+0x519) [0xb5827cc9]
3: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state+0x2a) [0xb58280ea]
4: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Clear+0x17e) [0xb57badbe]
5: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c4fa08]
6: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0x155) [0xb7c48625]
7: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c486bc]
8: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c4cb2c]
9: /usr/bin/X [0x815754e]
10: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
11: /usr/bin/X(main+0x495) [0x8076f05]
12: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dcf050]
13: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting
----

For me the problem is simply with the screensaver starting, whether locked or not -- my idle screensaver config doesn't lock, and I couldn't work out why it was back at GDM after I went away from it for a few minutes; if I select "Lock Screen" however the crash happens straight away. The screen fades out to black like usual, but at the point where the screensaver would start X crashes instead. Also confirmed that the problem occurs in dual-head scenario only -- exactly the same xorg.conf (I get my dual-head through xrandr commands at present) with only single-head enabled and the screensaver works fine.

very same problem here with an ATI Radeon Mobility 9000 (M9), (ati driver), card

----
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb5827b3b]
3: /usr/lib/xorg/modules/extensions//libGLcore.so(_swrast_Triangle+0x2d) [0xb5826c5d]
4: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb5868c0f]
5: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb587a870]
6: /usr/lib/xorg/modules/extensions//libGLcore.so(_tnl_RenderClippedPolygon+0x44) [0xb587acc4]
7: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb5875e36]
8: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb5877cca]
9: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb587ae10]
10: /usr/lib/xorg/modules/extensions//libGLcore.so(_tnl_run_pipeline+0x13f) [0xb586b4bf]
11: /usr/lib/xorg/modules/extensions//libGLcore.so(_tnl_draw_prims+0x3ee) [0xb586a8fe]
12: /usr/lib/xorg/modules/extensions//libGLcore.so(vbo_exec_vtx_flush+0x22d) [0xb58bb11d]
13: /usr/lib/xorg/modules/extensions//libGLcore.so(vbo_exec_FlushVertices+0x78) [0xb58b75f8]
14: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Flush+0x83) [0xb5776d93]
15: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c2c717]
16: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c0cb2c]
17: /usr/bin/X [0x815754e]
18: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
19: /usr/bin/X(main+0x495) [0x8076f05]
20: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d6e050]
21: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting
----

This problem only occurs once I use my laptop with the external monitor to have a dual screen display.

I think this is the same as bug #151253. If I change gnome-screensaver to use a blank screen, X does not die.

bug #151253 was marked invalid due to lack of a backtrace. Since this report has ample backtrace, I'm refiling this with gnome-screensaver rather than marking it a dupe.

I appear to have this as well, although the backtrace is slightly different (earlier in _mesa_update_state_locked and an extra level):
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48672d]
1: /lib/libc.so.6 [0x7fefc28f67d0]
2: /usr/lib/xorg/modules/extensions//libGLcore.so(xmesa_update_state+0x42) [0x7fef9f69f8a2]
3: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state_locked+0x455) [0x7fef9f5c3d25]
4: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state+0x11) [0x7fef9f5c4121]
5: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Clear+0x108) [0x7fef9f55f2e8]
6: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0x13b) [0x7fefc18e945b]
7: /usr/lib/xorg/modules/extensions//libglx.so [0x7fefc18ed00d]
8: /usr/bin/X(Dispatch+0x1db) [0x4514eb]
9: /usr/bin/X(main+0x45d) [0x439f4d]
10: /lib/libc.so.6(__libc_start_main+0xf4) [0x7fefc28e2b44]
11: /usr/bin/X(FontFileCompleteXLFD+0x231) [0x439249]

It is with the i810 driver and dual head with different sizes for the monitors (the laptop has native 1440x900 and the CRT is a normal one using 1280x1024).
Also, using the 'blank screen' screensaver doesn't crash. And the 'flying ubuntu' screen saver doesn't crash.
My guess would be that GL based screensavers crash. And DRI is not available for me on this specific setup.

This is with gutsy:
ii xserver-xorg-video-i810 2:1.7.4-0ubuntu5 X.Org X server -- Intel i8xx, i9xx display driver
ii gnome-screensaver 2.20.0-0ubuntu4.2 a screen saver and locker
ii xscreensaver-data 4.24-5ubuntu3 data files to be shared among screensaver frontends
ii xscreensaver-gl 4.24-5ubuntu3 GL(Mesa) screen hacks for xscreensaver

Feel free to ask more specific information. I just don't know what else is relevant here.
I also don't mind trying a patched .deb or installing debug packages.

I upgraded my laptop to hardy (which is due in some 12days).
This is no longer a problem. GL based screensavers only show on one screen, but at least don't crash the session.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.