[18647] in Athena Bugs
sun4 8.4.15: xss
daemon@ATHENA.MIT.EDU (Richard J. Barbalace)
Tue Jan 2 23:46:32 2001
Message-Id: <200101030446.XAA17770@starbase.mit.edu>
To: bugs@MIT.EDU
Date: Tue, 02 Jan 2001 23:46:23 -0500
From: "Richard J. Barbalace" <rjbarbal@MIT.EDU>
System name: starbase.mit.edu
Type and version: SPARC/20 8.4.15 (with mkserv)
Display type: cgsix
Shell: /bin/athena/tcsh (/afs/sipb/project/tcsh/tcsh?)
Window manager: vtwm.gamma
What were you trying to do?
Set up both lock and unlock commands for xss (similar
to do what I used to do with xscreensaver).
What's wrong:
xss exits if both a lock and an unlock command are specified.
In my .Xresources I have:
!XScreenSaver.lockCommand: xv -root -quit /mit/rjbarbal/Graphics/cha.gif
XScreenSaver.lockCommand: zaway
!XScreenSaver.unlockCommand: xsetroot -solid black
XScreenSaver.unlockCommand: zwrite rjbarbal -m test
The lines beginning with ! are commented out. If either lockCommand
is specified, and both unlockCommands are commented out, xss is fine.
If either unlockCommand is specified, and both lockCommands are
commented out, xss is also fine. If one lockCommand and one
unlockCommand are specified, xss will exit after being unlocked. It
does not seem to matter what the lock and unlock commands are.
No error message is given when xss exits. Running "xss-command -lock"
after xss exits results in the error:
xss-command: no screensaver is running on display :0.0
What should have happened:
xss should not die.
Please describe any relevant documentation references:
man xss
