[6536] in SIPB bug reports
Xscreensaver bug
daemon@ATHENA.MIT.EDU (Boris Zbarsky)
Wed Oct 22 11:45:33 1997
To: bug-sipb@MIT.EDU
Date: Wed, 22 Oct 1997 11:45:22 EDT
From: Boris Zbarsky <bzbarsky@MIT.EDU>
[From Greg Hudson's message]
> So, this is really quite gross, but try putting a "sleep 1;" before
> the xscreensaver command. It may be failing to lock because it can't
> grab the mouse or some other resource. (I'm guessing that you did
> this as a windowmanager menu item, and the windowmanager has the mouse
> grabbed when the command runs.)
>
> I don't know why it's not killing zaway; maybe the code path for when
> it can't grab a resource is buggy and doesn't kill off the appropriate
> children.
OK. I played around with xscreensaver some more. I'm trying to start
it from the prompt (ideally, I'd like to start it with xautolock).
Sometimes when I run just 'xscreensaver -L +icon' followed by
'xscreensaver -L +icon -lc zaway', it'll work properly, except when it
exits the "xscreensaver -L +icon -lc zaway" it gives me one of the
following two error messages:
1) Xlib: unexpected async reply (sequence 0x45)!
2) X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 45 (X_OpenFont)
Serial number of failed request: 47
Current serial number in output stream: 39
After this it invariably does not work again -- just flashes the screen.
Oh, I tried putting the "sleep 1;" in, it didn't work.
Also, I tried running it under Linux and on the cluster SGI's, under
both Afterstep and the SGI windowmanager. Still no luck.
Boris
*********************************************************
* There are three kinds of lies: Lies, Damn Lies, and *
* Statistics. *
* -- Disraeli *
*********************************************************
