[18874] in Athena Bugs
xlock vs. xss on sgi 8.4
daemon@ATHENA.MIT.EDU (John Hawkinson)
Fri Mar 16 21:58:28 2001
Date: Fri, 16 Mar 2001 21:58:22 -0500
From: John Hawkinson <jhawk@MIT.EDU>
To: bugs@MIT.EDU
Message-ID: <20010316215822.A14902@x15-cruise-basselope.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I just looked into a user's xss/xlock problem.
/usr/bin/xlock was being run by his .desktop_{indy,o2}/panelsession
file, such that it started up automatically.
xss was being run from the standard Athena dotfiles.
They would both autoactivate and lock the screen (perhaps they
follow the same XresourceS?) at the same time, leading to
an unfortunate situation.
Oddly enough, one of them complained on the console about this,
but the lsosage happened anyway.
Is there anything to be done about this?
a) Can xss take some measure to ensure that an xlock isn't running?
b) Can the X resources be altered such that xlock doesn't see
xss's resources and they don't both lock the screen automatically?
Or something else?
In this user's case, I removed the xlock line from his pannelsession
and then logging in no longer produced two screensavers (where previously
it had done so).
--jhawk
