Hi all, While searching for an alternative to xscreensaver (I find the unlock screen plain ugly and don't use any of the animations anyway), I came across i3lock, which is already included in Factory. It does all I need (lock the screen) and is very lightweight. However, it misses one important feature: the actual unlocking of the screen :-) This works as root, and it works if I SGID shadow the i3lock binary. But I guess this is not the right thing to do? The package even includes a pam file /etc/pam.d/i3lock (this is suse package specific different from the upstream one) containing: #%PAM-1.0 auth include common-auth account include common-account password include common-password session include common-session But I cannot determine what this is good for. I put in some debug code and found out that pam_authenticate() fails with PAM_AUTH_ERR, for insufficient access to /etc/shadow, I would expect PAM_CRED_INSUFFICIENT, but then I know next to nothing about PAM internals. So what to do? make i3lock sgid shadow? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org