-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devuan chimaera slim/elogind hangs #328
Comments
Does this reproduce with the latest version of |
I observe the same problem on a gentoo-machine (with a weird installation with
My first suspicion was that maybe I screwed up and slim would not end up using a different config due to being a different service. But both Graphical login with an encrypted home is known to work on this machine via a custom pam-module which stopped working with pam-1.4. However, I foolishly removed the corresponding bits from the PAM-config already and now I don't know where I placed those entries, exactly, any more. Current
|
Since logs were requested, I extracted them for the logins earlier. I removed date/time and hostname and redacted policy and protector names (even though they should be safe to share IIUC). This should be a login via
The logs for the login appears to really just end there, shortly after the And this should be a login via
|
I guess that's not the right place to ask this question, but I didn't get any support where I asked.
To the question. I installed Devuan Chimaera and I wanted to use fscrypt with pam, so as to use my login password to decrypt my home folder.
Using the console I successfully log on the system and my files are decrypted.
With the login manager (slim) immediately after I put my login details, the screen hangs with the default background and no menus or mouse cursor were shown.
I tried to put
session optional pam_fscrypt.so drop_caches lock_policies
beforesession required pam_unix.so
incommon-session
(Debian buglibpam-fscrypt: encrypted home not unlocked in time
) with no luck.Any ideas are welcome!
The text was updated successfully, but these errors were encountered: