What exactly are you using to lock your screen? Is it x11/xlockmore, x11/xscreensaver or something else perhaps?adripillo said:Seems it have some problems when I lock screen and want to unlock it.
It says the password is not correct
fonz said:What exactly are you using to lock your screen? Is it x11/xlockmore, x11/xscreensaver or something else perhaps?
Screen unlocking does not work
If screenlock does not accept your password add the following to /etc/pam.d/enlightenment:
auth required pam_unix_auth.so
Authentications via PAM had errors setting up the authentication session. The error code was 1.
auth required pam_unix.so
kpa said:That advice in the wiki is most likely for Linux, in FreeBSD the PAM module is called pam_unix(8). Try this line in the file:
Code:auth required pam_unix.so
Don't let the name fool you, x11/xscreensaver can also lock the screen if so desired.adripillo said:I do not know what enlightenment uses to lock the screen, but it is not a screensaver for sure.
fonz said:Don't let the name fool you, x11/xscreensaver can also lock the screen if so desired.
Anyway, does Enlightenment have a setting somewhere that specifies how the screen is locked?
fonz said:Can you check (see /var/db/pkg/) whether one of the ports I mentioned has been installed?
If you run it manually (e.g.adripillo said:I have installed now x11/xlockmore
% xlock -mode kumppa
), does the problem persist?That's a known problem. If you ever wish to install x11/xscreensaver and you're building from ports, just disable that one.adripillo said:but can not install x11/xscreensaver (fireflies fails).
fonz said:If you run it manually (e.g.% xlock -mode kumppa
), does the problem persist?
Then I suspect it's indeed a PAM problem. Can you try x11/xtrlock? It's very small, simple and it appears not to use PAM.adripillo said:I used this time x11/xlockmore to lock screen, but when I want to unlock it it also says password is wrong.
fonz said:Then I suspect it's indeed a PAM problem. Can you try x11/xtrlock? It's very small, simple and it appears not to use PAM.
I'm glad you now have at least something that works. However, I suspect that the problem with the other locks isn't in Enlightenment itself but in your system's PAM configuration. I do recommend that you look into it when you can spare the time.adripillo said:This one worked fine and is very funny. Thanks a lot. Hope some day the Enlightenment get fixed.
fonz said:I'm glad you now have at least something that works. However, I suspect that the problem with the other locks isn't in Enlightenment itself but in your system's PAM configuration. I do recommend that you look into it when you can spare the time.
<login>:<password-crypted>
auth required /usr/local/lib/pam_pwdfile.so pwdfile /usr/local/etc/enlightenment.passwd
auth required pam_permit.so
Thanks for joining in and for suggesting a solution.Peter2121 said:It seems that Enlightenment does not speak correctly with the FreeBSD PAM subsystem.