Can only boot to CLI after latest update

[prog_drummer]

Hello all,

After updating via sudo zypper dup, my laptop only boots to a CLI interface. I used snapper to restore to a pre-update version and now everything is back to normal but if I try to update again I get the same issue.

During the update process, I got the TLP conflict issue as reported by other users. To fix this I deinstalled tuned.

How can I troubleshoot and fix the issue?

Thanks.

[rafaellinuxuser]

I had the same problem (cli after upgrade) about 2 or 3 weeks ago. I had to recover from a snapshot and waited until a few days ago to renew again and … now it works with whatever changes you have made.

[pascom]

Hello!
I have not have any such issue for ages (fingers crossed), but when it happened, I used to check which service failed (sudo systemctl status) and look in the journal (sudo journalctl -b, -b selects the current boot).
And I generally waited for the next release of the package which caused the issue (no way to file a bug for me, I cannot log into bugzilla ).
Best regards,
Pascom

[prog_drummer]

I just tried installing the updates again. It seems my issuse only occurs when I enable TLP (sudo systemctl enable --now tlp.service). startplasma-wayland fixes this but only for the current boot.

Any idea what I may be doing wrong with TLP?

[prog_drummer]

Both sudo systemctl --failed and sudo journalctl -b -p err show no errors.

[pascom]

Hello!
You can check sudo systemctl status display-manager.service to see what it looks like. Is sddm (unless you changed the login screen) running?
Personnally, I have no issue with TLP and sddm.
Best regards,
Pascom

[prog_drummer]

It’s running but it looks like it’s got some errors. See output below:

 display-manager.service - X Display Manager
     Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-05-28 18:34:45 BST; 3min 41s ago
    Process: 1319 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
   Main PID: 1358 (sddm)
      Tasks: 7 (limit: 4915)
        CPU: 535ms
     CGroup: /system.slice/display-manager.service
             ├─1358 /usr/bin/sddm
             └─1397 /usr/bin/Xorg.bin -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_vOmmEn -noreset -displayfd 16

May 28 18:34:47 localhost.localdomain sddm[1358]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last login: Tue May 28 18:33:16 BST 2024 on tty1"
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
May 28 18:34:47 localhost.localdomain sddm[1358]: Session started true
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: Failed to write utmpx:  No such file or directory
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: [PAM] Closing session
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: pam_unix(sddm-autologin:session): session closed for user x
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_close_session
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: Failed to write utmpx:  No such file or directory
May 28 18:34:47 localhost.localdomain sddm-helper[1593]: [PAM] Ended.
May 28 18:34:47 localhost.localdomain sddm[1358]: Auth: sddm-helper exited with 1

[prog_drummer]

For comparison, here’s how it looks with tlp disabled:

May 28 18:49:40 localhost.localdomain sddm[1361]: Authentication for user  "x"  successful
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: pam_unix(sddm-autologin:session): session opened for user x(uid=1000) by x(uid=0)
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: [PAM] Preparing to converse...
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: [PAM] Conversation with 1 messages
May 28 18:49:41 localhost.localdomain sddm[1361]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last login: Tue May 28 18:38:03 BST 2024 from 192.168.0.13 on ssh"
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
May 28 18:49:41 localhost.localdomain sddm[1361]: Session started true
May 28 18:49:41 localhost.localdomain sddm-helper[1586]: Failed to write utmpx:  No such file or directory

[pascom]

Hello! Looks like an issue caused by pam_kwallet5. Maybe you should upgrade to and use pam_kwallet6 (I checked it exists in zypper). I have none of them, so I am not sure I will be able to help you further.
Hope it helps,
Pascom