Cant login in to system

Bug #1890998 reported by QkiZ
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm on login screen, GDM3. I'm choosing my user and typing password. After pressing enter key for confirm password screen is blinking once and I'm on GDM login screen once again.
I found this in syslog:

gnome-shell[6209]: The XKEYBOARD keymap compiler (xkbcomp) reports:
gnome-shell[6209]: > Warning: Unsupported maximum keycode 569, clipping.
gnome-shell[6209]: > X11 cannot support keycodes above 255.
gnome-shell[6209]: > Internal error: Could not resolve keysym Invalid
gnome-shell[6209]: Errors from xkbcomp are not fatal to the X server

Installed GDM version is 3.34.1-1ubuntu1. System wasn't updated since last reboot. After installing SDDM I can log in to system.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 10 10:20:33 2020
InstallationDate: Installed on 2019-03-01 (527 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/usr/bin/fish
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-05-15 (86 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2019-03-06T11:01:56.985551

Revision history for this message
QkiZ (qkiz) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please:

1. Try selecting 'Ubuntu on Wayland' on the login screen, before entering your password.

and if that didn't work then:

2. Try editing /etc/gdm3/custom.conf and uncommenting:

   #WaylandEnable=false

   to be:

   WaylandEnable=false

   and reboot.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
QkiZ (qkiz) wrote :

1. I tried this before I made a bug report. It just hang on purple screen right after confirming password. I needed to kill X session to return to login screen. Doesn't work.
2. Doesn't work also. Symptoms are same but log is different.
https://paste.ubuntu.com/p/gjqXkFGyqP/

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I would like to see a clean log of the problem in action. Please reboot fresh, reproduce the gdm login failure and then reboot _again_.

Now after the second reboot please hit Ctrl+Alt+F4 and log in to the text console. In the text console please run:

  journalctl -b-1 > prevboot.txt

and then attach the resulting text file here.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
QkiZ (qkiz) wrote :

Here's log from previous boot like you wanted.
https://paste.ubuntu.com/p/T5bWDQXr76/

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

These look like the problem:

sie 12 09:43:03 mkukielka-prs gdm-password][3167]: pam_unix(gdm-password:session): session closed for user mkukielka

sie 12 09:43:03 mkukielka-prs systemd-logind[1446]: Session 2 logged out. Waiting for processes to exit.
sie 12 09:43:04 mkukielka-prs systemd-logind[1446]: Removed session 2.

Although they don't explain the "why".

Please enable debug mode in /etc/gdm3/custom.conf and then repeat the steps from comment #4.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
QkiZ (qkiz) wrote :

Debug mode enabled, steps repeated.
https://paste.ubuntu.com/p/f97M7NgWF4/

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks.

It sounds like there's an invalid Xorg config file on your system with lots of:

  Option "_source" "server/udev"

and

  Option "_source" "_driver/libinput"

That may be why Xorg is exiting immediately. If you can find the config file that contains those then please move it elsewhere, and/or attach it here.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Try looking in /usr/share/X11/xorg.conf.d/

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
QkiZ (qkiz) wrote :

Files from /usr/share/X11/xorg.conf.d in attachment. None of these files contains 'Option "_source" "server/udev"' or 'Option "_source" "_driver/libinput"'.

Revision history for this message
QkiZ (qkiz) wrote :

I didn't modify those files. Those files belongs to following packages:
xserver-xorg-video-amdgpu
xserver-xorg-core
xserver-xorg-video-radeon
xserver-xorg-input-libinput
xserver-xorg-input-wacom

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This looks like the exact point of failure:

sie 13 11:38:35 mkukielka-prs /usr/lib/gdm3/gdm-x-session[3413]: unix_listener: cannot bind to path /tmp/ssh-eND2ca8O3cXt/agent.3413: Permission denied
sie 13 11:38:35 mkukielka-prs gdm-x-session[3385]: session exited with status 1
sie 13 11:38:35 mkukielka-prs /usr/lib/gdm3/gdm-x-session[3492]: X connection to :1 broken (explicit kill or server shutdown).

Perhaps some kind of SSH misconfiguration? If you are not using SSH for the moment then try moving ~/.ssh to a different name briefly. Or try logging in as a different user with a fresh home directory.

Revision history for this message
QkiZ (qkiz) wrote :

Still nothing.
https://paste.ubuntu.com/p/q8NKNMh4KX/
I renamed ~/.ssh to ~/.ssh.bak, switched back to gdm3, reboot and it's same. Still after confirming password I'm landing on gdm login screen.

Revision history for this message
QkiZ (qkiz) wrote :

I switched to sddm and log in to system to check permissions on ssh agent socket.

$ ls -la /tmp/ssh-GLokEJp0ajlD/agent.4700
srw------- 1 mkukielka mkukielka 0 sie 18 12:26 /tmp/ssh-GLokEJp0ajlD/agent.4700=
I think the permissions are good.

Revision history for this message
QkiZ (qkiz) wrote :

I found what causes this issue. I set up umask to 137 in .profile file. After commenting out this line and restart I can log in to system.

Changed in gdm3 (Ubuntu):
status: New → Invalid
Revision history for this message
QkiZ (qkiz) wrote :

Anyway it is stupid that setting custom umask blows gdm and prevent logging in.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes and no. Computers will do what you ask them to, not what you want them to.

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.