https://bugs.kde.org/show_bug.cgi?id=511410
--- Comment #2 from wrongfix <[email protected]> --- (In reply to TraceyC from comment #1) > As the message at the top of the summary says, if something crashed, we need > a backtrace of it so we can figure out what's going on. Can you please > attach a backtrace of the crash using the coredumpctl command-line program, > as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > If you don't have coredumps for kwin, this isn't a crash and there are some > other things we can try. There is no coredump, since it is not a crash, it is a freeze. If I connect via SSH to my laptop from other system I see 100% CPU usage by Xwayland process, and that is. There is nothing unusual in logs. The overall issue feel very similar to the old bug described in https://bugs.kde.org/show_bug.cgi?id=442846 It seems that kwin is waiting for something or blocked by something, but it is not crashed. -- You are receiving this mail because: You are watching all bug changes.
