On May 17, Michael Stone wrote: > Are you running the broken version of kdm in testing that has the wrong > PATH and doesn't parse xresources properly?
No. I'm running fvwm here. But the pure X server without a windowmanager or any other X client (started with: X&; export DISPLAY=:0; xlock -mode blank) also shows the different behaviour of both versions of the xlockmore package. I say it again, the reason for the changed behaviour is the additional file /etc/X11/app-defaults/XLock in the version 1:5.21-3 of the package. If I remove this file I get back the old behaviour. And it's quite clear if you look into the ressource files: Old (1:5.21-1): /etc/X11/Xresources/xlockmore: XLock*logoutButton: -1 ==> public logout button disabled New (1:5.21-3): /etc/X11/app-defaults/XLock: ! 0 defaults to maximum defined value XLock.logoutButton: 0 ==> public logout button enabled Apparently /etc/X11/app-defaults/XLock takes precedence over /etc/X11/Xresources/xlockmore or /etc/X11/Xresources/xlockmore is even ignored in the new version. In general it's not a good idea to have the same kind of ressources in two different places. Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
