gnome-screensaver-gl-helper assert failure: gnome-screensaver-gl-helper: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.

[Frank S]

Binary package hint: gnome-screensaver

using Terminal Server Client on Ubuntu 9.1 release candidate. multiple workspaces with multiple Terminal connections. When working on one for extended period error message pops up when I switch to a different workspace. There appears to be no actual affect on anything I am doing, I just get the crash report pop-up.

Note: I screen save never switches on, I am still actively using the desktop, just a different workspace.

ProblemType: Crash
Architecture: i386
AssertionMessage: gnome-screensaver-gl-helper: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.
CrashCounter: 1
Date: Wed Oct 28 10:59:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.28.0-0ubuntu3
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: gnome-screensaver
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 _XRead () from /usr/lib/libX11.so.6
Title: gnome-screensaver-gl-helper assert failure: gnome-screensaver-gl-helper: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #423714, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.