Announcement

**claydoh** · Dec 26, 2022, 10:42 AM

You might need to look at jornalctl and see if anything useful is found there.

Plasma doesn't use a screensaver, the closest thing would be the lock screen, so you might see if disabling that has any effect on things as an experiment.

As to Bluetooth, the device probably defaults to turning off or suspending when idle, even though the Bluetooth system default setting is NOT to do so. it probably is usb-driver related, like it is for me. I also use a Bluetooth mouse and keyboard most of the time, and have to disable autosuspend on it, as well as on both my Keychron KBs so I am not annoyed all the time

To check:

Code:

$ cat /sys/module/btusb/parameters/enable_autosuspend
Y

To disable it, create the file /etc/modprobe.d/btusb_autosuspend-disable.conf with the contents:

Code:

options btusb enable_autosuspend=0

Reboot, or reload btusb, and check again:

Code:

$ cat /sys/module/btusb/parameters/enable_autosuspend
N

I doubt this will cure any freezes, but might help make things less frustrating

When you have this happen next, instead of going to a vt, try hitting alt-space or alt-f2, to bring up krunner. You can try restarting plasmashell (plasmashell --replace) or kwin_x11 from there.

As for troubleshooting, I don't know. I'd say report a bug on kde's bugzilla, but ask for assistance on getting the desired info. They will offer suggestions or links for that.

**phands** · Dec 26, 2022, 01:03 PM

Thanks, claydoh I'll start looking at journalctl - something new to learn is always good!

You're right - it's the lock screen I use...I'll try disabling that tonight as well.

I'm used to the Bluetooth suspend pain - it usually takes a few seconds of mouse movement before the cursor starts to react after inactivity. I'll do the autosuspend disable thing anyway - seems useful, so thanks. When the hang happens, the bluetooth devices never come back, no matter how much activity or time I use. The USB devices always work perfectly and instantly, even when BTooth is dead. That could still be a driver issue, as IIRC, the drivers are combined??

I'll try the krunner/kwin_x11 advice tomorrow, if/when it has crashed overnight.

My hesitancy in going straight to the developers is that I know they're ultra-busy and mostly volunteers, so I want to be able to give them real info in any bug report.

**phands** · Dec 28, 2022, 10:37 AM

Hi again, claydoh. You were right - turning off the BlueTooth autosuspend didn't make any difference.

Sadly neither did turning off the lock screen. The system still hangs, just slightly differently. Trying to bring up KRunner fails. Restarting Plasmashell or running kwin_x11 both fail as well.

I've been digging into journalctl , and in the process of getting started, I found a QT based GUI for journalctl, which is excellent! It's called QJournalctl and is on github at https://github.com/pentix/qjournalctl/ I had to satisfy a dependency on libssh dev files, but it compiled easily once downloaded.

There's so much stuff in the journalctl logs that it's still going to take a lot of time to look through, but the GUI makes it a huge amount easier, as it has filtering by severity and good search features.

Thanks again for pitching in, and happy 2023!

Paul

**claydoh** · Dec 28, 2022, 11:47 AM

I should have mentioned KSystemLog, which can show quite a few different log files.....but you don't get the fun of compiling.
But QJournalctl is arguably better looking..

**arraybolt3** · Mar 15, 2023, 02:17 AM

I had something similar happening to me. I figured out that, even with the desktop frozen, I was able to hit Ctrl+Alt+T to bring up a terminal. Then I was able to do "killall plasmashell" and "killall kwin_x11". At that point KRunner would start working again though my whole desktop would look like a mess. From KRunner, I then ran "plasmashell" and then "kwin_x11" and my desktop was back up and running. I had to do this quite a bit since my desktop would go crazy while I was actively using it, usually in response to a notification popping up.

**jlittle** · Mar 15, 2023, 12:47 PM

Originally posted by arraybolt3 View Post

... I was able to do "killall plasmashell" and "killall kwin_x11"... then ran "plasmashell" and then "kwin_x11"

In theory, plasmashell --replace and kwin --replace does the same as killing then starting anew.

Announcement

Question about debugging: KDE hangs up every night

Question about debugging: KDE hangs up every night

Comment

Comment

Comment

Comment

Comment

Comment