0

Ubuntu desktop login went wrong after a normal shutdown.
Problems:

  1. Ubuntu cannot login with wired connection enabled.
  • (On login screen) I clicked on username and entered password, then desktop freezes.
  • Terminal (Alt+F3) is fine.
  • After two minutes or so, Ubuntu returned to login screen, with a toast prompted: something like network authentication failure (with a wired connection icon)
  1. Ubuntu can login with wired connection disabled.
  • I disabled wired connection at login screen, and was able to login normally.
  • After login, I enabled wired connection and it is working.
  • When I try to open Chrome, "Enter password to unlock your login keyring" prompted.
    Existing question like: How can I stop being prompted to unlock the 'default' keyring on boot? is irrelevant to my problem. Auto login is disabled and I entered password during login.

System information:

  • Ubuntu 22.04.5 LTS / 6.8.0-51-generic
  • Wired connection is configured as DHCP in Setting, without "Security" options enabled.
  • dmesg has some errors: (wlp15s0 is the wireless adapter)
[  437.023309] wlp15s0: authenticate with 5e:b0:xx:xx:xx:xx (local address=5e:b0:xx:xx:xx:xx)
[  437.036102] wlp15s0: send auth to 5e:b0:xx:xx:xx:xx (try 1/3)
[  437.046327] wlp15s0: send auth to 5e:b0:xx:xx:xx:xx (try 2/3)
[  437.056604] wlp15s0: send auth to 5e:b0:xx:xx:xx:xx (try 3/3)
[  437.066697] wlp15s0: authentication with 5e:b0:xx:xx:xx:xx timed out
  • journalctl has some errors: (I don't know if there is/how to find the actual fatal log that is related to login failure)
    This js backtrace repeated many times:
gnome-shell[4455]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await exp>
                                                   refreshPropertyOnProxy@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:43:38
                                                   _translateNewSignals/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:212:18
                                                   _translateNewSignals@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:211:50
                                                   _onProxySignal/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:228:56
                                                   _onProxySignal@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:228:38

And this repeated a few times:

NetworkManager[2057]: <warn>  [1746435001.3139] device (wlp15s0): Activation: (wifi) association took too long, failing activation
...
NetworkManager[2057]: <warn>  [1746435001.3142] device (wlp15s0): Activation: failed for connection 'XXX'

I would like to address the root cause (component) of the login failure and fix it.

0 Answers0