> Also as said before, somewhere, the engine pointer sent to
> gpm_cell_array_charge_low_cb (where the segfault occurs). Strange thing
> is athat the pointer Mike's valgrind log complains about
> (0x3a54494d45202a2a) is exactly the same as the pointer it complains
> about when I test it..
It is ex
Rich,
If somebody could catch the bug in the debugger then at least the full text can
be found.
It does not necessarily need to come from the g-p-m binary. It could be from
any of the loaded libs or even have been loaded from configuration.
But if this is text then one possible option how it go
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.
--
[gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver)
https://bugs.launchpad.net/bugs/153878
You receiv
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/15639514/xorg.conf
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: None => gnome-screensaver
--
screensaver ignores mouse action on second display
https://bugs.launchpad.net/bugs/243449
You received this bug notifica
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+0x
