Solved Laptop hangs after login manager

Solved issue

/dev/pie

Member
Joined
Jul 10, 2020
Messages
36
Reaction score
23
Credits
316
Hello, so sometimes my laptop will freeze after the login manager. Here are my system specs:
1739539639848.png


Here is a picture of it frozen. Also I would like to note that after a reboot or 2 I am able to log in and everything seems to work fine.
1739539845824.jpeg


How would I go about finding this error? I am pretty familiar with the terminal. Thanks in advance.
 


Can you switch to a TTY when it hangs (Ctrl + Alt + F2-F6)? If so just read the kernel message log (dmesg). The tail (pardon the pun) end of it should indicate any h/w issues (dmesg | tail -n 20 -- it should be in the most recent 20 lines). I'm afraid IDK where you'd find Wayland's error logs, I'm still on X11.
 
Code:
sudo journalctl | grep -i wayland

Since it looks like KDE here.
Code:
sudo journalctl -u kwin

Code:
sudo journalctl -u sddm
 
Since you're using an AMD Radeon, what is output of...
Code:
sudo glxinfo | grep OpenGL
 
Can you switch to a TTY when it hangs (Ctrl + Alt + F2-F6)? If so just read the kernel message log (dmesg). The tail (pardon the pun) end of it should indicate any h/w issues (dmesg | tail -n 20 -- it should be in the most recent 20 lines). I'm afraid IDK where you'd find Wayland's error logs, I'm still on X11.
When it hangs I am unable to switch to TTY. However when I run sudo journalctl -u sddm. I get this error at the time the crash happened:

Feb 14 05:21:17 fedora systemd[1]: Started sddm.service - Simple Desktop Display Manager.
Feb 14 05:21:17 fedora sddm-helper[1550]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which i>
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) m>
for more information.
Feb 14 05:21:17 fedora sddm-helper[1550]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=990)>
Feb 14 05:21:24 fedora sddm-helper[1766]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which i>
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) m>
for more information.
Feb 14 05:21:24 fedora sddm-helper[1766]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Feb 14 05:21:24 fedora sddm-helper[1766]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Feb 14 05:21:25 fedora sddm-helper[1766]: pam_unix(sddm:session): session opened for user devpie(uid=1000) by d>
Feb 14 05:21:25 fedora sddm-helper[1766]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Feb 14 05:21:25 fedora sddm-helper[1766]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/libe>
Feb 14 05:54:39 fedora sddm[1546]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Feb 14 05:54:39 fedora sddm[1546]: Auth: sddm-helper (--socket /tmp/sddm-auth-ef6f37e9-04e3-4c2d-a453-cbe0377c6>
Feb 14 05:54:39 fedora sddm[1546]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Feb 14 05:54:39 fedora sddm[1546]: Auth: sddm-helper exited with 1
Feb 14 05:54:40 fedora sddm[1546]: Signal received: SIGTERM
Feb 14 05:54:40 fedora systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
Feb 14 05:54:40 fedora systemd[1]: sddm.service: Deactivated successfully.
Feb 14 05:54:40 fedora systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.
 
Well
with character encoding "ANSI_X3.4-1968"
Sheds some light on. You shoult be on UTF-8 as amatter general rule. Very surprised Qt ain't compatible though... Anyway, you can edit /etc/locale to your <language>.UTF-8 (I think you can list the available ones withe locale <something> but I just go for en_US and be done) and then just restart. I'm sure there's a) a GUI way and b) a way to avoid a reboot, but I did this in ye olde days that many installers defaulted to C because SA didn't exist (en_ZA still doesn't seem to for some, so it's en_US and then UK dictionaries/spell-checkers -- timezone works though, GMT+2, Harare, Pretoria)
 
Well

Sheds some light on. You shoult be on UTF-8 as amatter general rule. Very surprised Qt ain't compatible though... Anyway, you can edit /etc/locale to your <language>.UTF-8 (I think you can list the available ones withe locale <something> but I just go for en_US and be done) and then just restart. I'm sure there's a) a GUI way and b) a way to avoid a reboot, but I did this in ye olde days that many installers defaulted to C because SA didn't exist (en_ZA still doesn't seem to for some, so it's en_US and then UK dictionaries/spell-checkers -- timezone works though, GMT+2, Harare, Pretoria)
my locale.conf file already has LANG="en_US.UTF-8" set.
 
I would guess this could be the problem

Code:
Feb 14 05:54:39 fedora sddm[1546]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Feb 14 05:54:39 fedora sddm[1546]: Auth: sddm-helper (--socket /tmp/sddm-auth-ef6f37e9-04e3-4c2d-a453-cbe0377c6>
Feb 14 05:54:39 fedora sddm[1546]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"

It you can login to the CLI or ssh to the computer.

This should give more info.
Code:
journalctl -u sddm.service -b

Temporarily disable SElinux to see if that helps.
Code:
sudo setenforce 0

Also I would try re-installing sddm.
Code:
sudo dnf reinstall sddm
 
my locale.conf file already has LANG="en_US.UTF-8" set.
Maybe check the output of locale

Code:
Feb 14 05:21:24 fedora sddm-helper[1766]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Feb 14 05:21:24 fedora sddm-helper[1766]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Feb 14 05:21:25 fedora sddm-helper[1766]: pam_unix(sddm:session): session opened for user devpie(uid=1000) by d>
Feb 14 05:21:25 fedora sddm-helper[1766]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Tells me you're authenticated correct.
fedora sddm-helper[1766]: pam_unix(sddm:session): session opened for user

... Anyway, turns out it may be another bug (Arch forums pretty much useful for all distros) in a display driver (even though you're on AMD, not Nvidia):
https://bbs.archlinux.org/viewtopic.php?id=296796
Almost identical issue, except it was Nvidia, not AMD (see thread mentioned below). The topic didn't get resolved so much as "fixed itself" and OP didn't really explain what happened (my theory is running everything as root/via sudo "cleaned up" properly after that session)... Anyway if/when you get it right, it may be good to just post your journalctl afterwards for the sake of other users as this seems to be pandemic.

I'm with @dos2unix on trying to reinstall sddm if all else fails. I checked and a lot of distros were having similar issues last year, including SUSE. There's even an Arch thread here:
https://linux.org/threads/arch-kde-wayland-freeze-after-login.51278/

So this does seem very sddm-specific. I find it weird that this would happen on an AMD system. So maybe I'll chalk it up to the KDE community this round and leave the Nvidia bashing just this once, lol.
 



Top