Anyone having this problem w/ xlock?
xlock: caught signal 11 while running swirl mode (uid 500).
We also had this this problem, but only on machines running quite old versions of SuSE Linux (5.x, x < 3 or so). Seems to be a bug in one of xlock's modules. This is in fact *not* off topic, because it can be a real security problem when someone locks his/her screen with xlock -mode random and the screen simply unlocks some time later during his/her absence. We solved it by telling the users to use xlock -mode some-mode with some-mode not being "swirl" ;-) Hope this helps, Jan Hildebrandt -- jan.hildebrandt@mathema.de MATHEMA Software GmbH (http://www.mathema.de) Nägelsbachstraße 25a D-91052 Erlangen, Germany Tel: (+49)9131/8903-0 Fax: (+49)9131/8903-55