dependency problem lightdm -> pam
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
I've installed Lubuntu 18.04 and found that problem:
the display-manager service complains:
● lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/
Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
Docs: man:lightdm(1)
Process: 1717 ExecStartPre=
Main PID: 1720 (lightdm)
Tasks: 6 (limit: 4915)
CGroup: /system.
├─1720 /usr/sbin/lightdm
├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/
└─1786 lightdm --session-child 12 19
Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(
Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: pam_kwallet5.so
Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_gnome_
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet5.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_
It's because /etc/pam.d/lightdm and /etc/pam.
If it is not intended to let things run into error message (and possible further trouble), you should either remove these lines from the config files or add dependencies to pull in that packages.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed May 2 12:21:26 2018
InstallationDate: Installed on 2018-04-30 (2 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
Status changed to 'Confirmed' because the bug affects multiple users.