This happens to me multiple times in a single day, first the wifi completely disconnects and then the KDE freezes and I can’t do anything other than restart. I checked the dmesg and it said something along the lines of “Timeout for the driver failed”. When the problem replicates I will paste all the dmesg in here.
Have you tried waiting several minutes or more to see if the problem clears itself? If it does, you may have a miscreant background task that needs to be ID’d and halted, disabled and/or restarted to avoid freezing.
Do any of the messages in dmesg or journal replicate many times in succession? If so, they’re probably alluding or pointing to the cause.
If this is an old installation, it may benefit if you log out of plasma, empty ~/.cache/ logged in as root, then restart plasma.
1 Like
Checking dmesg is good but you might be too late to catch the problem.
Often, a complete freeze is caused by running out-of-memory, that will not leave any signs in the log. Yyou can check for that by having the KDE system monitor run and show the Memory use (Overview or History). Make sure you place this somewhere on the screen you can still see it when the freeze happens.
2 Likes
Oh I didn’t wait generally because it happened while I was playing games but yes the messages in dmesg were replicated many times in succession.
Oh okay, I will be running the system monitor.
It doesn’t seem to be about RAM as it didn’t even use up to 50%
Now I waited a few minutes after the freeze and yeah it went back to normal.
And how exactly I will log out of Plasma?
Like you were going to reboot or shutdown, except you click on leave.
Good you found out that it is not memory and that it returns normal after waiting a few minutes,
If it returns, it is good to have a look at the journal. Write down the time the problem started and open the log using journalctl. To get the log for the current boot, use
sudo journalctl -b -1
Change the -1 to -2 if you want the previous log, etc. If you found the correct log you can redirect the output to file using “sudo journalctl -b -1 > my_log.txt”
If you want to have help reviewing, share the log via susepaste and share the link and the time the problem started.
Well sorry for answering this late I was sick to continue in topic even when the KDE functions after a few minutes I couldn’t get it to connect to the Wi-Fi because of that I have the log as a screenshot
Sharing logs via images is rarely useful. In this case, we see only the start, where most likely relevant clues are at or near the end.
sudo journalctl -b -1 | susepaste
would provide much more valuable information.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.