https://bugs.kde.org/show_bug.cgi?id=460513
--- Comment #9 from space9...@proton.me --- Yes, it does look similar, though the cause is different. A few things: - you reported a segfault in kwin_wayland, i.e. it tried to access invalid memory, then crashed. This is not incidental to what you experienced, it is the bug. - kwin_wayland is not still running, it restarted. Note the different process IDs, 237394 vs 238586 - maybe other programs are still running after the crash, but I don't see them either. You would have to take a process tree before the crash with something like `ps axjf` and log to a file, then compare with after. I'm happy to try to help you to reproduce your bug, though I do have limited time to spend on this now. I'll move further discussion over there. -- You are receiving this mail because: You are watching all bug changes.
