https://bugs.kde.org/show_bug.cgi?id=434506
--- Comment #32 from Harald Sitter <sit...@kde.org> --- This is great news. The first trace is indeed the compositor crashing, [1] might help debug that in the future but is unrelated to the bug at hand. Your second trace isn't even a crash it's simply SIG32, which is sometimes used to synchronize threads, in particular somewhere deep in VLC. You can set `handle 32 pass nostop` in ~/.gdbinit then it won't stop gdb anymore in the future ;) https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl -- You are receiving this mail because: You are watching all bug changes.
