pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

pkg/46271: x11/xlockmore built w/pam fails all authentication attempts, won't unlock screen

>Number:         46271
>Category:       pkg
>Synopsis:       x11/xlockmore built w/pam fails all authentication attempts, 
>won't unlock screen
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 27 21:45:00 +0000 2012
>Originator:     John D. Baker
>Release:        NetBSD-6.0_BETA/i386, pkgsrc-current (pre-pkgsrc-2012Q1)
NetBSD squash.bozonet.ntc 6.0_BETA NetBSD 6.0_BETA (SQUASH) #15: Mon Mar 26 
11:13:35 CDT 2012  

With "PKG_OPTIONS.xlockmore+=pam" in /etc/mk.conf, the resulting
xlock program considers all unlock attempts as failed whether using the
user's password or the root password.

Should there be a pam configuration file for 'xlock'?  Is it intended
to use one of the existing pam configurations--"system" perhaps?  I saw
no errors logged anywhere when xlock engaged.
Set "PKG_OPTIONS.xlockmore+=pam" in /etc/mk.conf and build/install

Run 'xlock' to lock the screen.

Screen cannot be unlocked via password.  On architectures that support
it, switch to text-mode terminal, log in and kill xlock.
Workaround.  Do not enable the "pam" option when building x11/xlockmore.

Home | Main Index | Thread Index | Old Index