Bug 1144948 - login fails with gdm
login fails with gdm
Status: RESOLVED WORKSFORME
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: GNOME
Current
x86-64 openSUSE Factory
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-08 21:10 UTC by ravas mi
Modified: 2019-08-19 01:06 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ravas mi 2019-08-08 21:10:45 UTC
Gdm won't accept my password. This happens seemingly randomly on a fresh boot. I think this started within the last 2-3 snapshots. CTRL+Alt+F1 then CTRL+Alt+F2 seems to solve the problem.

VERSION_ID="20190730"
5.2.3-1-default

I'll do a zypper dup and report back if this continues.

---

Here's the seemingly relevant information from journalctl

Aug 08 13:47:50 tumbleweed-hn gdm-password][1859]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty7 ruser= rhost=
Aug 08 13:47:50 tumbleweed-hn gdm-password][1859]: pam_unix(gdm-password:auth): check pass; user unknown
Aug 08 13:47:37 tumbleweed-hn gdm-password][1859]: gkr-pam: error looking up user information
Aug 08 13:47:37 tumbleweed-hn gdm-password][1859]: accountsservice: ActUserManager: user (null) has no username (uid: -1)
Aug 08 13:47:33 tumbleweed-hn gdm-password][1855]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty7 ruser= rhost=
Aug 08 13:47:33 tumbleweed-hn gdm-password][1855]: pam_unix(gdm-password:auth): check pass; user unknown
Aug 08 13:47:22 tumbleweed-hn gdm-password][1855]: gkr-pam: error looking up user information
Aug 08 13:47:22 tumbleweed-hn gdm-password][1855]: accountsservice: ActUserManager: user (null) has no username (uid: -1)
Aug 08 13:47:22 tumbleweed-hn gnome-shell[1485]: ActUserManager: user (null) has no username (uid: -1)

---
Comment 1 ravas mi 2019-08-08 22:20:19 UTC
I meant "CTRL+Alt+F1 then CTRL+Alt+F7 seems to solve the problem."
Comment 2 xiaoguang wang 2019-08-09 02:07:02 UTC
When issue happens, it's better to attach the full journal log by command 'journalctl -b'.
Comment 3 ravas mi 2019-08-17 00:22:58 UTC
The update might have solved the problem. It has not happened in the last week.
Comment 4 Yifan Jiang 2019-08-19 01:06:57 UTC
Hi ravas,

Thank you for the report and confirmation, I am closing it by now. Please feel free to reopen when the issue appears again.