From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.4-2 i686; en-US; 0.8.1)
Description of problem:
When I lock the screen xscreensaver is crashing. It happens regardless of
which particular screensaver is set to run. Once crashed, the screen is
still locked but any attemts to enter the user password at the unlock
prompt fail to authenticate. I can usually log into another virtual
terminal and kill processes of xscreensaver and whichever screensaver was
running. The screensaver process is in state TN at this point and
xsreensaver is usually still running. At this point I can return to X but
it is usually in an unpredictable unstable state and often will very
quickly crash out back to the CLI (I'm in init level 3). xscreensaver
seems to recognise that the child has died and will sometimes start to
rapidly cycle through all the screensavers, each of which quickly dies and
it loops doing this.
Steps to Reproduce:
1. Click the lock icon in the panel or click the gnome foot and then "Lock
Actual Results: Error messages print to the screen in the background and
the xscreensaver login prompt appears but it cannot successfully validate a
Expected Results: The screen should lock and I should be able to
sucessfully log back in.
I've had trouble getting the error output as after a few moments
xscreensaver seems to recognise that its child has failed and it cycles,
obliterating the message. But it seems like it is:
X error in xmatrix:
X Error failed request: BadDrawable (invalid Pixmap or Window parameter)
Major op code of failed request: 62 (X_CopyArea)
Resource id number of failed request: 0xe00001
Serial number of failed request: 2980
Current serial number of output streem: 7249
I'm not sure if it matters but this is the stock XFree86 install on top of
the i810 DRI module of a custom built unpatched 2.4.4 kernel.
Also sometimes I do catch an error message stating:
Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget
with width 65527 and height 1:
which may or may not be related.
Finally, I will attach a copy of the log generated one of the times that
this caused an outright crash of X.
Created attachment 17410 [details]
XFree86 crash log
*** This bug has been marked as a duplicate of 36670 ***