Skip to content
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

Add lines to /etc/pam.d/lightdm to enable lightdm to mount encrpyted user dir #105

Closed
michaelmrose opened this issue May 1, 2021 · 1 comment
Assignees

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@michaelmrose
Copy link

@michaelmrose michaelmrose commented May 1, 2021

Is your feature request related to a problem? Please describe.
I prefer lightdm to sddm and would prefer it worked with zfscrypt

Describe the solution you'd like
Adding the following lines makes it work correctly

auth include system-login
account include system-login
session include system-login

Describe alternatives you've considered
The obvious alternative is to use sddm however sddm on trident uses a non standard session dir meaning that installing say i3-wm using the gui to select session type appears from the user perspective to be completely broken although you can fix this by copying over the desktop file to the dir used by sddm. Presumably this is also true of the 1001 different graphical environments available for lights. Configuring lightdm to run correctly just requires adding the same lines to the pam configuration that is included in the sddm file.

Personally I've been bitten by several bugs specifically with sddm in the past I don't consider it reliable software.

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented May 27, 2021

Couple quick issues with this:

  1. Trident does not use/provide/recommend lightdm. We setup SDDM and have that already running just fine.
  2. The issue you want fixed is that the lightdm PAM config file is not using the "system-login" rules on Void. That would need to be fixed in the lightdm package for Void, not in Trident itself.

You might want to open up a bug report on https://github.com/void-linux/void-packages to get that PAM config file patched, or submit the patch yourself: https://github.com/void-linux/void-packages/tree/master/srcpkgs/lightdm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment