Red Hat Bugzilla – Bug 1248548
FC22.x86_64: can't authenticate users after update
Last modified: 2016-07-19 15:54:06 EDT
Description of problem:
I've just installed fedora-22.3 (x86_64) and updated with
# dnf update
Now I can't login after reboot. The system boots successfully, but when I try to login with it, I see gdm3 again and again. I can reproduce it only for the gnome x11 and gnome classic, Gnome on Wayland works perfectly and I can login with it.
Version-Release number of selected component (if applicable):
Version of gdm: GDM 3.16.2
Linux alex.fedora 4.0.4-301.fc22.x86_64 #1 SMP Thu May 21 13:10:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Steps to Reproduce:
1.try to authenticate with a user on GDM
GDM returns "Unable to authenticate user"
user logs in
~$ systemctl status gdm.service
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2015-07-30 19:06:35 ALMT; 24min ago
Main PID: 848 (gdm)
Jul 30 19:06:35 alex.fedora systemd: Starting GNOME Display Manager...
Jul 30 19:06:35 alex.fedora systemd: Started GNOME Display Manager.
Jul 30 19:06:46 alex.fedora gdm-password]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=alex
Jul 30 19:06:52 alex.fedora gdm: GdmDisplay: display lasted 0.589490 seconds
Jul 30 19:07:01 alex.fedora gdm: GdmDisplay: display lasted 0.498776 seconds
Jul 30 19:07:08 alex.fedora gdm: GdmDisplay: display lasted 0.473066 seconds
Just tried to login with slim instead of gdm3, and login was successful. Seems that actual problem is in the gdm.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.