[4996] in testers

home help back first fref pref prev next nref lref last post

xss, gnome-terminal crashes

daemon@ATHENA.MIT.EDU (Christopher D. Beland)
Sun Jul 15 07:05:58 2001

Message-Id: <200107151105.HAA01730@whack-a-mole.mit.edu>
To: testers@MIT.EDU
Date: Sun, 15 Jul 2001 07:05:48 -0400
From: "Christopher D. Beland" <beland@MIT.EDU>


06:23 ##############################################################################
06:23 
06:23 xss: X Error!  PLEASE REPORT THIS BUG.
06:23 
06:23 ##############################################################################
06:23 
06:23 X Error of failed request:  BadValue (integer parameter out of range for operation)
06:23   Major opcode of failed request:  107 (X_SetScreenSaver)
06:23   Value in failed request:  0xffff8ca0
06:23   Serial number of failed request:  46
06:23   Current serial number in output stream:  47
06:23 
06:23 ##############################################################################
06:23 
06:23     If at all possible, please re-run xscreensaver with the command^N
06:23     line arguments `-sync -verbose -no-capture', and reproduce this
06:23     bug.  That will cause xscreensaver to dump a `core' file to the
06:23     current directory.  Please include the stack trace from that core
06:23     file in your bug report.  *DO NOT* mail the core file itself!
06:23     That won't work.
06:23 
06:23     http://www.jwz.org/xscreensaver/bugs.html explains how to create
06:23     the most useful bug reports, and how to examine core files.
06:23 
06:23     The more information you can provide, the better.  But please
06:23     report this bug, regardless!
06:23 
06:23 ##############################################################################
06:23 

I did so; the result is at /mit/aui/crashes/core.xss.beland.

A little while later, gnome-terminal crashed just as I was typing
"ls".  The result is at /mit/aui/crashes/core.gnome-terminal-beland.

These were both on whack-a-mole, which is an O2.

This may be related - I remotely rebooted the machine yesterday, but
it didn't come back up.  I came it to find it kernel paniced.  When I
hit Enter to reboot, the screen partially garbled, and froze.  I had
to power cycle it.  These crashes happened a few minutes later; I
wonder if I'm having hardware problems of some sort.

Hrm,

Beland

===============================================================
Christopher Beland - http://web.mit.edu/beland/www/contact.html
MIT STS/Course 6 (EECS)   -   MIT Athena User Interface Project              
The Talk of MIT   **   http://web.mit.edu/beland/talk/talk.html
===============================================================

home help back first fref pref prev next nref lref last post