Can't unlock screen saver with pam_mysql

Bug #1419131 reported by Mitch Claborn
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Undecided
Unassigned
unity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description: Ubuntu 14.04.1 LTS
Release: 14.04
unity:
  Installed: 7.2.4+14.04.20141217-0ubuntu1

We are using pam_mysql to login to the workstation. Excerpt from /etc/pam.d/lightdm.conf:

auth required pam_mysql.so verbose=1 user=xxxxx passwd=xxxxx db=xxxx host=xxx table=operator usercolumn=username passwdcolumn=password crypt=0 where=operator.enabled=1

There is a similar line in /etc/pam.d/gnome-screensaver

Login to the workstation works fine. Up until this week, unlocking the screen saver worked fine also. Now it is not working to unlock from the screen saver. I added the verbose=1 option and can see the logging when user logs in, but no logging shows up when the user attempts to unlock the screen saver, leading me to believe it is not calling pam_mysql.

I tried a similar config in /etc/pam.d/unity but that did not help.

This are the entries from /var/log/apt/history.log from the day it stopped working:
Start-Date: 2015-02-05 05:12:23
Install:
 linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic),
 linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic),
 linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic),
 linux-headers-3.13.0-45:amd64 (3.13.0-45.74, automatic)
Upgrade:
 libclamav6:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 0.98.6+dfsg-0ubuntu0.14.04.1),
 linux-headers-generic:amd64 (3.13.0.44.51, 3.13.0.45.52),
 unity:amd64 (7.2.3+14.04.20140826-0ubuntu1, 7.2.4+14.04.20141217-0ubuntu1),
 indicator-session:amd64 (12.10.5+14.04.20140410-0ubuntu1, 12.10.5+14.04.20140925-0ubuntu1),
 libunity-core-6.0-9:amd64 (7.2.3+14.04.20140826-0ubuntu1, 7.2.4+14.04.20141217-0ubuntu1),
 tzdata-java:amd64 (2014i-0ubuntu0.14.04, 2015a-0ubuntu0.14.04),
 file:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3),
 libmagic1:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3),
 unity-services:amd64 (7.2.3+14.04.20140826-0ubuntu1, 7.2.4+14.04.20141217-0ubuntu1),
 clamav-freshclam:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 0.98.6+dfsg-0ubuntu0.14.04.1),
 clamav-base:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 0.98.6+dfsg-0ubuntu0.14.04.1),
 unzip:amd64 (6.0-9ubuntu1.1, 6.0-9ubuntu1.2),
 clamav:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 0.98.6+dfsg-0ubuntu0.14.04.1),
 tzdata:amd64 (2014i-0ubuntu0.14.04, 2015a-0ubuntu0.14.04),
 linux-libc-dev:amd64 (3.13.0-44.73, 3.13.0-45.74),
 linux-image-generic:amd64 (3.13.0.44.51, 3.13.0.45.52),
 linux-generic:amd64 (3.13.0.44.51, 3.13.0.45.52)
End-Date: 2015-02-05 05:13:35

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.4+14.04.20141217-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Feb 6 13:47:10 2015
InstallationDate: Installed on 2015-01-22 (15 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac (20140722.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mitch Claborn (mitch-news) wrote :
Revision history for this message
Mitch Claborn (mitch-news) wrote :

Here are entries from auth.log from a failure:

Feb 6 13:24:36 asset144 unix_chkpwd[3331]: password check failed for user (kim)
Feb 6 13:24:36 asset144 compiz: pam_unix(unity:auth): authentication failure; logname= uid=2050 euid=2050 tty= ruser= rhost= user=kim

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
status: New → Confirmed
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.