Bug 1515100 - Remove pam_elogind.so from sddm PAM configuration
Summary: Remove pam_elogind.so from sddm PAM configuration
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 27
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jiri Eischmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-20 07:16 UTC by Pierre Juhen
Modified: 2018-09-10 17:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-10 17:28:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pierre Juhen 2017-11-20 07:16:18 UTC
Description of problem:

Messages in /var/log/messages

adding faulty module: /usr/lib64/security/pam_elogind.so
unable to dlopen(/usr/lib64/security/pam_elogind.so): /usr/lib64/security/pam_elogind.so: cannot open shared object file: No such file or directory

elogind.so is missing

Version-Release number of selected component (if applicable):

pam-1.3.0-6.fc27.x86_64

How reproducible:

Always



Regards

Comment 1 Tomas Mraz 2017-11-20 09:26:30 UTC
This module is not part of Linux-PAM project. If you need it become a Fedora packager and submit a package with the module for review.

Comment 2 Pierre Juhen 2017-11-22 05:43:29 UTC
Hi,

Therefore, you should comment out the line :

 session               optional pam_elogind.so

in /etc/pam.d/sddm-greeter, that causes the error message.

Regards,

Comment 3 Rick 2018-01-08 04:34:57 UTC
Really, that module shouldn't be referenced in that config file. And that file comes from the sddm package.  So it looks like someone might have fat fingered the packaged config file.  The bug is non-fatal, since I have at least one system with the misconfiguration that's working perfectly fine.

But it was also a red herring when I was trying to debug one that wasn't.

Comment 4 Talha Khan 2018-02-26 07:06:16 UTC
At the time of this comment (feb 26 2018), I still get that error message in my journalctl output, and the line mentioned by Pierre is still there in the config file.

Comment 6 Robert Story 2018-09-10 16:56:49 UTC
still around in fedora 28.. sddm-0.17.0-3.fc28.x86_64

Comment 7 Rex Dieter 2018-09-10 17:28:04 UTC
This is fixed in sddm-0.18.0 (for f29+ only for now).  The fix will be backported for prior fedora releases, when/if needed, but not to only fix this mostly-cosmetic bug.


Note You need to log in before you can comment on or make changes to this bug.