Registered Member
|
Hi fellow KDE lovers!
I have a question about getting detailed debug and log info from KDE...BEFORE I bother the developers with ill-defined bug reports. Since an update a few days ago, KDE partially hangs sometime in the middle of the night. The symptoms are that the system has gone to screen saver at some unknown time, and the on-screen clock continues to show the correct time. At that point, moving the mouse or hitting a keyboard key (Note both are Bluetooth) has no effect, and the system appears to be be hung....but it's not. Being a long term Linux and KDE addict, I experimented. It seems that a USB mouse and Keyboard still work - cursor moves, and I can enter a password to unlock and see all my (many, many!) windows in 4 workspaces. However...window management has stopped working...I can't raise a new window to the foreground, can't change focus, there is no screen background menu popup on right-click, so I usually ended up holding the power button to force a system restart. I suspect that the Bluetooth subsystem in KDE has hung as well, as USB still seems to work, and that's handled by the OS rather than KDE. Further experimentation...I can hit ctrl-allt-F2 to get to a non-GUI shell, and can login as root and do the usual things (including a clean reboot), so I tried to restart KWin and Plasmashell from there, but that failed, and then the USB subsystem hung as well....back to the power switch! The whole thing is repeatable - happens every night - and I don't see anything obvious in the usual logs in /var/log/syslog. However, /the previous session log, in syslog1.gz is filled with larger amounts of red text near the end, and before the hang. A huge number are from the likcups printer system, and I can't believe they are causing the hang. A large number are from plasmashell, but the dates are wrong for a crash last night......
There is so much noise in the syslog files, that I can't see anything obvious, and I don't know what to look for. System Info...
So...my question for you all is....can you suggest additional logging/debugging steps I can take before going to the developers? Thanks for even looking at this, and have a great 2022 - 2023 transition season!! Paul |
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]