On May 04, Michael Stone wrote: > Setting where?
I have tried it with command line options which usually oversteer the default settings. > It's not new; it's been there for more than 5 years. At least it wasn't there with out of the box settings in sarge and also in etch before my last update. So the default behaviour has changed within the last few weeks. This should have been worth a news message. I have looked a bit deeper into this. First I can disable the logout button with logoutButton -1. The manpage should mention this possibility. It also should mention what the allowed range for the logoutButton time is. If I use zero or rather large values xlock silently ignores them and falls back to the default value. Second there is a new ressources file in the package which wasn't there in sarge (/etc/X11/app-defaults/XLock) which makes the difference (there are also changes in the look, e.g. the blank mode now has white letters on black ground instead of black letters on white ground before). In the new package there are two ressorces files for xlock, /etc/X11/Xresources/xlockmore and /etc/X11/app-defaults/XLock, which have contrary settings: /etc/X11/Xresources/xlockmore: XLock*logoutButton: -1 This is the old one and apparently has disabled the logout button in the default configuration so far. /etc/X11/app-defaults/XLock: XLock.logoutButton: 0 This seems to oversteer the settings in /etc/X11/Xresources/xlockmore (or maybe this file is even ignored now). So a bit of cleanup seems to be necessary. And I would prefer a standard configuration without the logout button as it was before ;-). Regards, Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
