[4020] in testers
xss not ready for prime time
daemon@ATHENA.MIT.EDU (Joseph Sokol-Margolis)
Tue May 18 18:11:03 1999
Message-Id: <199905182209.SAA09941@oliver.mit.edu>
To: testers@MIT.EDU
Date: Tue, 18 May 1999 18:09:33 -0400
From: Joseph Sokol-Margolis <seph@MIT.EDU>
Bugs I've noticed so far on oliver (sipb's beta o2)
if you try and run xss-button, it should tell you to run xss-button
instead of xss (okay, this isn't really a bug)
xss does not appear to actually lock the screen. it puts up the normal
"This display is locked" message, but it accepts any non-null password
I give it.
when I select preferences from the xss-button I get the demo. this is
incorrect. If this can't be fixed, change the menu option, it's
confusing.
when I run xss, I get a little screen, if I click preferences, I get
both the demo and the preferences, this is inconvient. When I quit the
demo, xss spews "xss: child pid 9822 (<unknown>) exited abnormally (code 0)."
I can't test it's interactions with xscreensaver, as the latter needs
to be rebuilt for this platform.
it writes it's preferences to $HOME/.xscreensaver as it's installed as
xss, it should probably save to $HOME/.xss
xlock seems a little weird. on the sgi's xlock is installed locally
without read permissions, so I can't stat it. on the suns it's
installed on the packs, with read permission. I don't actually know if
this is a bug.
seph
