Login screen showing Authentication Failure Switch to greeter...

Bug #1733557 reported by Andrew Neeson on 2017-11-21
688
This bug affects 138 people
Affects Status Importance Assigned to Milestone
Unity
New
Undecided
Unassigned
unity (Ubuntu)
Undecided
Unassigned

Bug Description

When I lock my machine, the login screen shows my current user with the message: "Authentication Failure"

..and in the position when the password normally exists, the option "Switch to greeter..."

This happens mostly after switching user sessions.
Syslog contains entries like:
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 2 time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Nov 21 10:28:47 2017
InstallationDate: Installed on 2017-04-17 (217 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

Andrew Neeson (andyrokit) wrote :
no longer affects: gnome-control-center (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in lightdm (Ubuntu):
status: New → Confirmed

Anyone know either the cause, or a solution?

If it helps, the two computers where I'm seeing this also happen to be the two host computers where I run Virtualbox.

Andrew Neeson (andyrokit) wrote :

My issues began shortly after upgrading from 16.10 -> 17.10. Most of my issues related to graphical components so perhaps it was related to the switch to Wayland?

...as for a fix - I ended up reformatting my machine with a fresh 17.10. Haven't seen any of the issues since.

See: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733318
for a list of other issues to happen at the same time.

Eugene Romanenko (eros2) wrote :

Same on 16.04.3 after updating Unity to latest proposed packages.
Also on 17.10 with installed unity-session.

For me, this issue appears after switching to another user.

Steps to reproduce (must be more than one local users on system, eg. "bob", "alice"):
1. Login under bob.
2. Via upper-right menu switch to "alice".
3. On greeter screen setect "alice", login under alice.
4. Logout, return to greeter screen.
5. Select bob (already logged in). Enter password.
6. Lock screen. Issue appeared.
Issue appeared on every screen lock.

Messages in syslog:

Jan 6 17:15:33 eugene-Lenovo-Flex-2-14 systemd[1411]: Stopped Backing Service for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 1 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 2 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Starting Backing Service for the Unity Panel in Lockscreen mode...
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd-prestart-check[3804]: grep: /usr/share/gnome-session/sessions/ubuntu.session: Нет такого файла или каталога
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Started Backing Service for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Reached target A target that, when running, represents the screen being locked.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 3 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 4 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 5 time.

hife (hife) wrote :

Same as Eugene, the problem started popping up after upgrading Unity. When I lock my screen or wake from suspend, I get the described behaviour.

As a temporary fix, is there a way to just skip that screen and always go to the greeter when locking the screen or suspending?

hife (hife) wrote :

P.S.: To be precise, the message I get is not "Authentication failed", but "Authentication failure". This may be related to my system language being German.

Luis Alberto Pabón (copong) wrote :

I'm seeing this also upon 17.10 upgrade in unity / lightdm / unity greeter.

It doesn't happen 100% of the time, typically takes some time time to manifest (I only ever suspend my laptop from monday to friday), but once it starts happening, it always happens until I shut down.

Eugene Romanenko (eros2) wrote :

Appears on 16.04.3 after updating Unity to latest packages.
Also on 17.10 with installed unity-session.

For me, this issue appears after switching to another user.

Steps to reproduce (must be more than one local users on system, eg. "bob", "alice"):
1. Login under bob.
2. Via upper-right menu switch to "alice".
3. On greeter screen setect "alice", login under alice.
4. Logout, return to greeter screen.
5. Select bob (already logged in). Enter password.
6. Lock screen. Issue appeared.
Issue appeared on every screen lock.

Messages in syslog:

Jan 6 17:15:33 eugene-Lenovo-Flex-2-14 systemd[1411]: Stopped Backing Service for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 1 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 2 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Starting Backing Service for the Unity Panel in Lockscreen mode...
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd-prestart-check[3804]: grep: /usr/share/gnome-session/sessions/ubuntu.session: Нет такого файла или каталога
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Started Backing Service for the Unity Panel in Lockscreen mode.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Reached target A target that, when running, represents the screen being locked.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 3 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 4 time.
Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 5 time.

summary: - Login screen showing Authentication Failed Switch to greeter...
+ Login screen showing Authentication Failure Switch to greeter...
affects: lightdm (Ubuntu) → unity (Ubuntu)
tags: added: 16.04 17.10 unity xenial
Eugene Romanenko (eros2) wrote :

Screenshot from virtualbox test install.

Khurshid Alam (khurshid-alam) wrote :

Something to do with pam. But this is only happening in 16.04...I can't reproduce on bionic (https://code.launchpad.net/~azzar1/unity/pam-logging-xenial)

Garcia David (davidgfolch) wrote :

For me, in an Ubuntu 16.04, happends every time I lock (or my laptot sleeps) and the login screen appears. It seems that it happends since I've installed virtualbox 5.4?

Eugene Romanenko (eros2) wrote :

> It seems that it happends since I've installed virtualbox 5.4?

Sure no, it just since latest unity update was landed in 16.04.

Eugene Romanenko (eros2) wrote :

> only happening in 16.04...I can't reproduce on bionic

In artful and bionic this issue reproduceable if lightdm used as display manager.

description: updated
description: updated
Eugene Romanenko (eros2) on 2018-02-21
description: updated
description: updated

This just started happening to me in 16.04 LTS. Not fatal, but annoying.

FYI, I use a KVM switch on one of two monitors connected to Ubuntu.

This started happening to me after the following scenario:
- I had account for my wife, created on the machine, but she has not used it ever.
- today she logged in with her account.
- after she logged out the bug was present, when I attempted to log in.
Now when I Lock/Switch Account the bug is produced.

Eugene Romanenko (eros2) wrote :

Sometimes I think Unity developers never use Unity actually, as this issue immediately visible when you share home PC with wife and children (assuming they have separate accounts).

Khurshid Alam (khurshid-alam) wrote :

@Eugene

It depends on the hardware/graphics. But as I said, I can't reproduce it on bionic (bionic has different unity/lightdm version). Can you reproduce it in a live iso?

Eugene Romanenko (eros2) wrote :

> It depends on the hardware/graphics.

Sure, no. I tested and have this issue on home PC (16.04.3 after latest Unity update, AMD Phenom CPU/Nvidia GPU), work PC (17.10, Intel i7/Intel), Lenovo flex laptop (17.10, intel i5), and of course in VirtualBox (16.04.3 fresh install with latest updates, 18.04).

> But as I said, I can't reproduce it on bionic (bionic has different unity/lightdm version). Can you reproduce it in a live iso?

Not tried live iso, but I have test box with up-to-date 18.04. Just two days ago I tried:

Added second user account;
sudo apt install unity-session lightdm
sudo apt purge ubuntu-session gnome-shell gdm3

Reboot, login as first user, start second user session, end session, return to first user session, lock screen - issue here.

Bionic live iso does not have unity and lightdm preinstalled, so them will be downloaded from repository anyway.

Garcia David (davidgfolch) wrote :

In my case, I've installed virtualbox-dkms 32bits, in host "Ubuntu 16 64bits", instead than in the virtualbox hosted "Ubuntu 16 32bits"

When I've removed those 32bits libs the problem disappeared.

It started to happen to my laptop today after I did an upgrade.

Ubuntu 16.04.

4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Start-Date: 2018-02-24 14:43:33
Commandline: apt dist-upgrade
Requested-By: avillez (1000)
Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), grub-common:amd
64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), pulseaudio:amd64 (1:8.0-0
ubuntu3.7, 1:8.0-0ubuntu3.8), google-chrome-stable:amd64 (64.0.3282.167-1, 64.0.3282.186-1), python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 (9.4ubuntu4.5, 9.4ubuntu4.6)
End-Date: 2018-02-24 14:44:44

Hendri Schoeman (hendrisch) wrote :

I can confirm the same is also happening on my notebook.
Everything was fine up to about 2-3 weeks ago.

```
hendri@neptune: ~$ cat /etc/issue
Ubuntu 16.04.4 LTS \n \l
```

OS: Ubuntu 16.04.4 ... all up to date
Hardware:
 Gigabyte P15 Notebook
 - Graphics - nVidida GTX 950M + Intel (Dual graphics)
 - Processor - i7-7700HQ
 - HDD 1 - Standard 1 TB HDD
 - HDD 2 - 950 Evo m.2 SSD
 - 8GB mem
Graphics driver - nVidia 384.111

I reckon it has something to do with the nVidia Driver.

NULL (krush206) wrote :

I can confirm this bug occurs with me aswell, though, I was doing some maintenance in my computer yesterday and after replugging the power cable of the monitor, instead of plugging it in my voltage stabilizer, I plugged it in the computer's power supply, after using Ubuntu for awhile, I locked the screen and noticed the bug was gone, Im not sure why this worked but this was the workaround I (mistakenly) found

Nick Williams (rogwilco) wrote :

I started encountering this issue also. My system was working fine up until yesterday when this started happening. I most often notice it when I connect my laptop to an external display (or make some other display related change that kicks me to the login prompt).

Silvia (fichera-sil) wrote :

I have this problem starting from today when I locked my laptop with win+L.

Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial

Rubens (rhkina) wrote :

Same issue!
Ubuntu: 16.04 LTS

R_volkmann (r-volkmann) wrote :

Same for me since last unity update and is very annoying

- CPU: i8700k
- Geforce 1060
- no Virtualbox installed
- multi-user
- English languade, German keyboard

Bodinux (bodinux) wrote :

I confirm the occurrence of this bug since yesterday.

Alexander (azol) wrote :

Confirming the same issue, Ubuntu: 16.04 LTS
Just began to experience it after last batch of system updates.

P.Constantine (pconstantine) wrote :

Mar 11 22:50:23 lenovo lightdm[1216]: ** (lightdm:1216): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call
Mar 11 22:50:23 lenovo org.gtk.vfs.Daemon[11625]: A connection to the bus can't be made

B@MB@M (bart-bamweb) wrote :
Download full text (6.2 KiB)

I have the same issue.

I have Virtualbox running as well.
I'm not switching between users. Just standby and resume.

Here are some parts of several logfiles.

auth.log
======================================
Mar 12 16:36:33 BN pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
Mar 12 16:36:33 BN pkexec[20336]: bart: Executing command [USER=root] [TTY=unknown] [CWD=/home/bart] [COMMAND=/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 7126]
Mar 12 16:36:45 BN lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 12 16:36:45 BN lightdm: PAM adding faulty module: pam_kwallet.so
Mar 12 16:36:45 BN lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 12 16:36:45 BN lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 12 16:36:45 BN lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Mar 12 16:36:45 BN systemd-logind[1178]: New session c32 of user lightdm.
Mar 12 16:36:45 BN lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 12 16:36:45 BN lightdm: PAM adding faulty module: pam_kwallet.so
Mar 12 16:36:45 BN lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 12 16:36:45 BN lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 12 16:36:45 BN lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "bart"
Mar 12 16:36:49 BN lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Mar 12 16:36:49 BN dbus[1153]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.498" (uid=109 pid=20527 comm="/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indi") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.380" (uid=0 pid=10380 comm="/usr/lib/bluetooth/bluetoothd ")
Mar 12 16:36:49 BN dbus[1153]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.498" (uid=109 pid=20527 comm="/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indi") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=10380 comm="/usr/lib/bluetooth/bluetoothd ")
Mar 12 16:37:15 BN sudo: bart : TTY=pts/22 ; PWD=/home/bart ; USER=root ; COMMAND=/usr/bin/zsh
Mar 12 16:37:15 BN sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 12 16:38:58 BN pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Mar 12 16:38:58 BN pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
Mar 12 16:38:58 BN pkexec[22237]: bart: Executing command [USER=root] [TTY=unknown] [CWD=/home/bart] [COMMAND=/usr/lib/update-notifier/package-system-locked]

Xorg.0.log
======================================
[ 23362.625] (II) AIGLX: Suspendi...

Read more...

B@MB@M (bart-bamweb) wrote :

this is a 16.04 system

$ lsb_release -a
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial

DeltaLima (Marcus) (dlm274) wrote :

same here, experiencing this until 2018-03-08 on my DellXPS 13 with latest i7 gen. (8.).
i have not done some debugging, but at this date the unity package was updated:

2018-03-08 09:35:13 upgrade unity:amd64 7.4.5+16.04.20171201.3 7.4.5+16.04.20180221-0ubuntu1

root@Atomrakete:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial

It happens to me when i lock my screen with win+l

logfiles needed by someone?

Edu (eduweb) wrote :

Same issue in my laptop Lenovo G40-80 I think after some apt-get update/upgrade it has started. (Between 2 or 3 weeks ago)

I'm the only user of this computer. There is only my user and admin is disabled.
I use Virtual Box and it was upgraded recently to Version 5.1.34 r121010 (Qt5.5.1).

If I lock screen it don't happens immediately. It happens only after screen goes blank.
Then I have to click on "switch to greeter" in password field and wait some seconds to screen changes and I be able to insert password.

# lsb_release -a
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial

Axl Mattheus (4xm4x) wrote :

Replaced my hostname with ...hostname... and user name with ...user...

auth.log says:

Mar 13 16:59:10 ...hostname... lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 13 16:59:10 ...hostname... lightdm: PAM adding faulty module: pam_kwallet.so
Mar 13 16:59:10 ...hostname... lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 13 16:59:10 ...hostname... lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 13 16:59:10 ...hostname... lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Mar 13 16:59:10 ...hostname... systemd-logind[1033]: New session c6 of user lightdm.
Mar 13 16:59:10 ...hostname... lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 13 16:59:10 ...hostname... lightdm: PAM adding faulty module: pam_kwallet.so
Mar 13 16:59:10 ...hostname... lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 13 16:59:10 ...hostname... lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 13 16:59:10 ...hostname... lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "...user..."
Mar 13 16:59:16 ...hostname... lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm

Erik Meitner (e.meitner) wrote :

I have this problem after installing updates yesterday. Looks like like how Eugene shows in comment #10.

The attachment contains the data logged in x-0.log, seat0-greeter.log, lightdm.log, and x-1.log in the /var/log/lightdm directory during a test. I pressed CTRL-ALT-L, waited 10 seconds, clicked "Switch to greeter...", waited 10 seconds, then logged in and stopped recording.

There is a DBus error, but not much else.

WirelessMoves (gsmumts) wrote :

Same here, happens since I installed updates on my 16.04 system yesterday. Never had this before. Uisng STRG-L to lock the screen frequently.

WirelessMoves (gsmumts) wrote :
Download full text (6.7 KiB)

Addition: Here are the packages that were updated. After this update the problem appeared on my 16.04 LTE system:

Log started: 2018-03-14 06:45:32
(Reading database ... 253390 files and directories currently installed.)
Preparing to unpack .../python-samba_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking python-samba (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../samba-common-bin_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking samba-common-bin (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../smbclient_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking smbclient (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../samba-libs_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../libwbclient0_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../libsmbclient_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_amd64.deb ...
Unpacking libsmbclient:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../samba-common_2%3a4.3.11+dfsg-0ubuntu0.16.04.13_all.deb ...
Unpacking samba-common (2:4.3.11+dfsg-0ubuntu0.16.04.13) over (2:4.3.11+dfsg-0ubuntu0.16.04.12) ...
Preparing to unpack .../update-notifier_3.168.8_amd64.deb ...
Unpacking update-notifier (3.168.8) over (3.168.7) ...
Preparing to unpack .../update-notifier-common_3.168.8_all.deb ...
Unpacking update-notifier-common (3.168.8) over (3.168.7) ...
Preparing to unpack .../libapparmor1_2.10.95-0ubuntu2.9_amd64.deb ...
Unpacking libapparmor1:amd64 (2.10.95-0ubuntu2.9) over (2.10.95-0ubuntu2.8) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
Setting up libapparmor1:amd64 (2.10.95-0ubuntu2.9) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
(Reading database ... 253390 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.6.5-2ubuntu0.4_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.5-2ubuntu0.4) over (1.6.5-2ubuntu0.3) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up libgcrypt20:amd64 (1.6.5-2ubuntu0.4) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
(Reading database ... 253390 files and directories currently installed.)
Preparing to unpack .../libapparmor-perl_2.10.95-0ubuntu2.9_amd64.deb ...
Unpacking libapparmor-perl (2.10.95-0ubuntu2.9) over (2.10.95-0ubuntu2.8) ...
Preparing to unpack .../apparmor_2.10.95-0ubuntu2.9_amd64.deb ...
Unpacking apparmor (2.10.95-0ubuntu2.9) over (2.10.95-0ubuntu2.8) ...
Preparing to unpack .../friendly-recovery_0.2.31ubuntu1_all.deb ...
Unpacking friendly-recovery (0.2.31ubuntu1) over (0.2.31) ...
Preparing to unpack...

Read more...

john rogers (0-john-m) wrote :

I had this on my 16.04 system and it was INFURIATING - was taking 30s or so to login after a lock screen.
I *think* I've found a workaround...
Changing the driver to neuveu reboot ( deal with the failure to detect resolution if needed )
change back to nvidia driver reboot
back to normal :) ( for the last 3 locks at least... fingers crossed!

WirelessMoves (gsmumts) wrote :

Update to #37 and #38 reporting the issue on 16.04 LTS: The issue went away as silently as it initially came. Ran another apt update/upgrade today, totally different packages updated and then rebooted. 'Authentication Failure' in the lock screen is now gone, even after several reboots.

For completeness here are the packages that updated, I don't see a comonality here.:

Start-Date: 2018-03-14 21:25:36
Commandline: apt upgrade
Requested-By: martin (1000)
Install: linux-image-extra-4.13.0-37-generic:amd64 (4.13.0-37.42~16.04.1, automatic), linux-headers-4.13.0-37-generic:amd64 (4.13.0-37.42~16.04.1, automatic), linux-headers-4.13.0-37:amd64 (4.13.0-37.42~16.04.1, automatic), linux-image-4.13.0-37-generic:amd64 (4.13.0-37.42~16.04.1, automatic)
Upgrade: unity-control-center-faces:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), linux-image-generic-hwe-16.04:amd64 (4.13.0.36.55, 4.13.0.37.56), linux-generic-hwe-16.04:amd64 (4.13.0.36.55, 4.13.0.37.56), unity-control-center:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), firefox-locale-en:amd64 (58.0.2+build1-0ubuntu0.16.04.1, 59.0+build5-0ubuntu0.16.04.1), libunity-control-center1:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), firefox:amd64 (58.0.2+build1-0ubuntu0.16.04.1, 59.0+build5-0ubuntu0.16.04.1), linux-headers-generic-hwe-16.04:amd64 (4.13.0.36.55, 4.13.0.37.56)
End-Date: 2018-03-14 21:26:48

31 comments hidden view all 111 comments
Igor (igorekz) wrote :

Sorry, top-right corner of the top bar of course.

Alex Whitney (whitneyas) wrote :

This seems to be happening to me when my screens locks from timeout and I come back.

Tao Zhang (agmao) wrote :

Same problem here. Sometimes after this occurs, I cannot even log in, have to restart the system.

> This seems to be happening to me when my screens locks from timeout and I come back.

Me too.

I started getting this problem about a week ago after the usual updates. Ubuntu 16.04 LTS. I have only one account I use, pretty much defaults everything. I do use Virtualbox though I get the problem without ever even starting the Virtualbox console after a restart.

unity 7.4.5+16.04.20180221-0ubuntu1
unity-greeter 16.04.2-0ubuntu1

However when I check apt history the last time unity packages were upgraded was 2018-03-06, at least a month earlier. (/var/log/apt/history.log*)

What packages could have caused this? I unfortunately don't have an exact date when this problem started and I think I postponed restarting the computer for many days when the updater was nagging me to restart last week.

Rod Waltermann (roddw2) wrote :

I have this problem, and found a thread here:
https://askubuntu.com/questions/584207/cannot-log-in-at-locked-screensaver-must-log-in-with-switch-user?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

The fix that worked for me was a permission problem on /etc/shadow
$ ls -l /etc/shadow
-rw-r----- 1 root shadow 2202 Jun 23 12:39 /etc/shadow

For me the permission was:
$ ls -l /etc/shadow
-rw-r----- 1 root root 2202 Jun 23 12:39 /etc/shadow

When I changed the group to shadow and restarted the system. I was able to login from the lock screen again. The reason I believe that restarting is required is that the lightdm crashes if it cannot access the shadow file. and once it crashed, you get the message about authentication failure, switch to greeter.

The explanation was that the lockscreen runs in user context, whereas the greeter runs as root, so the shadow group allows lightdm to access it.

I tried the lock screen several times now, and it is solidly working. I did not change the group from shadow to root, so perhaps an update changed the file permission, or a patch changed the password utility. not sure.

My issue resolved itself. There was a kernel update with some other package updates and after restarting the problem was gone.

The shadow file permissions are OK now, I did not have a chance to check them before.

Ethan Lamoreaux (hraefn) wrote :

This bug has been bugging me for a while now, not sure exactly when it showed up but it was after an update a good while ago. When I lock my console, I get this "bug screen" immediately. When I want to unlock I have to click the "Switch to greeter" button which has mysteriously replaced my password entry blank. Typically my Xorg session is running on virtual terminal 7. When I click the "switch to greeter" button, the screen goes blank and a new Xorg session is started on VT8, which then displays the greeter. I can switch between the bug screen on VT7 and the greeter on VT8 using CTRL+ALT+(F7 or F8). After I log in, the Xorg session on VT8 shuts down and I am automatically switched back to VT7 which may show the bug screen for a flash before the screen unlocks.

After a reboot (which I typically do only after an update that requires it) this bug goes away for a while but just when I think it has been fixed, it shows up again.

My /etc/shadow permissions are:
-rw-r----- 1 root shadow 1924 Feb 18 02:53 /etc/shadow

Erik Meitner (e.meitner) wrote :

@Rael Gugelmin Cunha (rael-gc):
You are probably right. The changelog for the "unity" package says: "* Refactor the way UserAuthenticator is created and passed around. Handle failures to create new threads and fallback to a "Switch to greeter..." button in case of failure. (LP: #1311316)"

It seems that the initial bug from LP: #1311316 of "Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again." was addressed with a workaround, but this workaround has caused even more problems. I never had the issue of not having a password prompt.

Adrienne (rykasimba) wrote :

This happens to me on 16.04LTS about once a week. When it happens my login also changes to Kanji characters. the only way to fix it is to reboot. Then it comes right back.

Same issue ubuntu 17.10 and auth.log looks exactly the same as reported in <a href=https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/comments/35> comment #35 </a> above.

tail /var/log/auth.log output

Abhay Mitra (abhaymitra) wrote :

Same issue on Ubuntu 16.04.4 LTS (single user login).

Pavel Slechta (paslechta) wrote :

I can confirm the issue on 16.04.4 LTS. And I am not switching any sessions.

amias (amias) wrote :

this is happening to me on 18.04 upgraded all the way from 16.04 as the releases came out.

i don't have secure boot , i use an nvidia graphics card , i am running vmware workstation 14

Ross Reedstrom (reedstrm) wrote :

count me an additional sufferer - 16.04.4, upgraded as upgrades came out. I also see the behavior go away for a time, then come back after the computer has not rebooted for a period of time. I see it no matter how the computer is locked: crtl-alt-L, lid close to sleep, timeout, the . Once the authentication error shows up, it doesn't go away until a full reboot. Single user/session

Dell XPS 15 (9550) intel/nvidia, stock everything, except kernel updated to 4.15.0-20-generic #21~16.04.1-Ubuntu

Archit Kumar (architkumar) wrote :

Same error : 16.04lts , single user, dual boot.
kernel 4.13.0-39-generic

Robert Clayton (rnctx) wrote :

Same error here with me on 16.04 (+ latest updates from security). Also using virtualbox as a plain ole non-root user.

Lex_Dysia (johnkirk) wrote :

I've experienced the same problem on a fully patched 16.04 LTS.
This issue only occurred in the last few weeks & may have corresponded to when I added 3 new users to the machine.
I have previously used the first option in https://askubuntu.com/questions/859581/how-to-change-the-unity-lockscreen-wallpaper to modify my lock screen wallpaper.
After this recent "Authentication failure" issue occurred I recompiled the Greeter Schema as per the link above (sudo glib-compile-schemas /usr/share/glib-2.0/schemas) which has cured the problem on my machine at least.

Sam (shf42) wrote :

I updated snapd (along with many other packages) and now the message is gone. Maybe snapd was at fault, but I am not sure.

Rael Gugelmin Cunha (rael-gc) wrote :

This bug happens in Bionic (18.04) too.

Playing With (afulldeck) wrote :

^ Crap. I was hoping the upgrade to 18.04 would remove it. I have the same bug with 16.04. This is been going on for some time. Does anyone know what is causing it???

bx1 (abx1) wrote :

The extra "Enter" to take me to the login screen is killing couple of seconds of my work. I am not sure if this is related to Xorg. Ping me if I need to dig in more. Here's the log

[ 40206.697] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 40206.751] (EE) modeset(0): failed to set mode: Permission denied
[ 40212.065] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 40212.131] (II) modeset(0): EDID vendor "AUO", prod id 8685
[ 40212.131] (II) modeset(0): Printing DDC gathered Modelines:
[ 40212.131] (II) modeset(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2086 1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[ 40212.148] (--) synaptics: ELAN1300:00 04F3:3057 Touchpad: touchpad found

DocWilco (k-ubuntuone-m) wrote :

A full reboot did fix this for me on 16.04

Rolf Leggewie (r0lf) on 2018-06-30
tags: added: bionic
Rolf Leggewie (r0lf) wrote :

I doubt this is a regression due to the fix for bug 1311316, simply for the fact that this problem was reported last November while the fix for bug 1311316 was only uploaded to the archive in February.

ptah (brett-h-l) wrote :

I can confirm this problem running Ubuntu 16.04 on Lenovo Carbon X1. Started ~4 months ago. Lock, close lid, open lid, "ubuntu authentication failure switch to greeter", hit enter and return to normal login screen. Single user.

Rael Gugelmin Cunha (rael-gc) wrote :

@Rolf: this issue is not new. But it started to happen everytime a second user logs in after https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316 fix. I helped to test that fix.

Peter Smith (l-peter-v) wrote :

FWIW this has been happening to me for some time.
Single user on this laptop.
Ubuntu 16.04
It doesn't happen all the time, but it occurs sooner if I have been using a large number of tabs in Chrome.
Hope that might help. :)

Erik Meitner (e.meitner) wrote :

I upgraded from 16.04 to 18.04. Same problem with the exception that I can't switch to the login screen from the lock screen by hitting a key. I need to press CTRL-ALT-F1 to get to the login screen. Then I can log in to get back to my session.

Rael Gugelmin Cunha (rael-gc) wrote :

Usually after click to switch to greeter and got able to login, if I restart compiz (compiz --replace &), this will stop.

Rael Gugelmin Cunha (rael-gc) wrote :

God, this bug is so annoying... I faced it several times in a day!

inactivist (inactivist) wrote :

Recompiling the greeter schemas as mentioned in #89[1] worked for me (Ubuntu 16.04 x64) -- haven't seen the failure in weeks, was seeing it every day or so before. I have no idea why it works, but so far so good. Wish I had time to dig deeper.

$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas

[1]https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/comments/89 worked for me.

Rael Gugelmin Cunha (rael-gc) wrote :

Recompile the greeter schemas made nothing here: after the second user login/logout, the first one will continue to see the message.

Szilárd Páll (sin-pecado) wrote :

As many others, after a recent update, whenever on return to any of the three machines I have with up-to-date 16.04.5, I am met with the "Authentication failure message" and am forced to switch to the greeter which on some boxes (e.g. my workstation with multiple NVIDIA GPUs) takes >5 sec.

Michael Engelbrecht (mikee13) wrote :

Hi. I also have this problem on my DELL Optiplex AIO 9010 running Ubuntu 16.04.5 LTS.

And "Yes I know that 16.04 is no longer supported" ... however it seems that if you upgrade to 18.04, it does not solve the problem and in fact makes it worse !! At the moment, I get this message after my desktop has been sleeping, click on it and the usual login prompt appears whereas with 18.04 it seems that we cannot switch to the login screen without pressing CTRL-ALT-F1.

Rick Harris (rickfharris) wrote :

In reply to #105

Have tested reverting that fix and it just re-introduces the bug
"After locking screen there is no input field to type password for unlock"

Having no input field is worse.

Rael Gugelmin Cunha (rael-gc) wrote :

@angela: I tested and it doesn't work. It had the same effect as restart or restart unity/compiz plugin: it'll work only until log with second user and suspend, then error is back.

Shlomo Bachar (shlomo-bachar) wrote :

This bug happens to me also. I had this problem in my laptop during a few months. But it disappeared after a while. Now it suddenly appeared on my desktop. 16.04 LTS. I dont have other users in my computers as others mentioned. It happened after a few weeks of a fresh Ubuntu installation. Annoying but not serious. It happens after returning from screen lock or restart. Disappears after doing "ESC".

pommm (pommm) wrote :

I 've got this bug after "apt-get dist-upgrade" on my system too.

System before bug:
Ubuntu 16.04.1 LTS
Kernel 4.4.0-45-generic #66-Ubuntu SMP

After upgrade:
Ubuntu 16.04.5 LTS
Kernel 4.4.0-131-generic #157-Ubuntu SMP

User A logged in
User A lock screen
User B logged in
User B logged out
User A try to login.

Message:
Authentication failure
Swith to Greeter

If click Swith to Greeter it witll allow you to login and then it is back.

Displaying first 40 and last 40 comments. View all 111 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers