[2144] in SIPB bug reports
xscreensaver
daemon@ATHENA.MIT.EDU (yandros@Athena.MIT.EDU)
Sat Oct 5 17:26:58 1991
From: yandros@Athena.MIT.EDU
Date: Sat, 5 Oct 91 17:26:26 -0400
To: bug-sipb@Athena.MIT.EDU
Reply-To: yandros@Athena.MIT.EDU
Based on the behavior of several people on -i help, I was able to get
xscreensaver to do the following on a vax-2000:
with these resources:
xscreensaver*BorderWidth: 0
xscreensaver*DisplayTimes: False
xscreensaver*autoLock: True
xscreensaver*float.BorderWidth: 0
xscreensaver*float.bitmap: /mit/yandros/Graphics/Bitmaps/enterprise.xbm
xscreensaver*geometry: -2-53
xscreensaver*icon.bitmap: /mit/yandros/Graphics/Bitmaps/fedemb.xbm
xscreensaver*lockCommand: /mit/yandros/Code/Csh/.saver.lock
xscreensaver*unlockCommand: /mit/yandros/Code/Csh/.saver.unlock
xscreensaver*useBackground: True
xscreensaver*velocity: 30
and these invocations:
xscreensaver
xscreensaver -requirePort
xscreensaver -L
xscreensaver -requirePort -L
I was able to get xscreensaver to consistently dump core whenever it
tried to either blank or lock the screen(The last two never mapped a
window, which may be normal, as I'm unfamiliar with the -L option).
With the first two options, I was able to successfully access all of
the menu functions that do not blank/lock the screen (i.e. change
timeout/(un)lock command/autolock/message), but any attempt to lock
the screen, either through the menu or with the mouse buttons caused
xscreensaver to dump core and exit when no message whatsoever. Two
core dumps, neither made with the -L option, are (frozen) in
~yandros/.Transient/core.xss.F and
~yandros/.Transient/core.xss.requirePort.F. Please let me know when
I can delete them.
-C
P.S. Oh, and you should note that xscreensaver now prints a 'more
usefull' message upon finding it's port taken:
xscreensaver: couldn't bind to port 32253: Address already in use
xscreensaver: Are you running another xscreensaver?
:^)
