Multitude of issues after upgrading to 16.04

Bug #1578877 reported by Steve Par
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ever since upgrading to 16.04, Rhythmbox GUI fails to open. Also, if I open User accounts under System Settings nothing opens, but after I can't close the System Settings window..

And here's a sample of auth.log entries:

May 6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 6 07:32:03 steven-OptiPlex-7020 lightdm: PAM adding faulty module: pam_kwallet.so
May 6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 6 07:32:03 steven-OptiPlex-7020 lightdm: PAM adding faulty module: pam_kwallet5.so
May 6 07:32:03 steven-OptiPlex-7020 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
May 6 07:32:03 steven-OptiPlex-7020 systemd-logind[1004]: New session c1 of user lightdm.
May 6 07:32:03 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
May 6 07:32:03 steven-OptiPlex-7020 lightdm: pam_ck_connector(lightdm-greeter:session): nox11 mode, ignoring PAM_TTY :0
May 6 07:32:05 steven-OptiPlex-7020 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 6 07:32:05 steven-OptiPlex-7020 lightdm: PAM adding faulty module: pam_kwallet.so
May 6 07:32:05 steven-OptiPlex-7020 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 6 07:32:05 steven-OptiPlex-7020 lightdm: PAM adding faulty module: pam_kwallet5.so
May 6 07:32:05 steven-OptiPlex-7020 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "steven"
May 6 07:32:15 steven-OptiPlex-7020 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
May 6 07:32:15 steven-OptiPlex-7020 lightdm: pam_unix(lightdm:session): session opened for user steven by (uid=0)
May 6 07:32:15 steven-OptiPlex-7020 systemd-logind[1004]: New session c2 of user steven.
May 6 07:32:15 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): session opened for user steven by (uid=0)
May 6 07:32:15 steven-OptiPlex-7020 lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
May 6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The PKCS#11 component was already initialized
May 6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The Secret Service was already initialized
May 6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The SSH agent was already initialized
May 6 07:32:19 steven-OptiPlex-7020 polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.79 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
May 6 07:32:31 steven-OptiPlex-7020 dbus[949]: [system] Failed to activate service 'org.bluez': timed out
May 6 07:34:01 steven-OptiPlex-7020 dbus[949]: [system] Failed to activate service 'org.bluez': timed out
May 6 07:34:03 steven-OptiPlex-7020 systemd-logind[1004]: Removed session c1.
May 6 07:34:04 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): session closed for user lightdm

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 6 08:00:07 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-06 (89 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-21 (14 days ago)

Revision history for this message
Steve Par (15303bdc) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.