https://bugs.kde.org/show_bug.cgi?id=449805
--- Comment #2 from temptem...@gmail.com --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Can you please attach one? Thanks! Hi, I only have this Coredump: > https://transfert.free.fr/aJ91KU And unfortunately, the process execeeded my Coredump limits so it would appear the main thread was not included: *** warning: Error reading shared library list entry at 0x6f635f74696e6900 Failed to read a valid object file image from memory. Core was generated by `/bin/kwin_wayland --wayland_fd 5 --socket wayland-0 --xwayland-fd 7 --xwayland-'. Program terminated with signal SIGSEGV, Segmentation fault. warning: Section `.reg-xstate/4652' in core file too small. #0 0x00007f6d20b64781 in ?? () [Current thread is 1 (LWP 4652)] (gdb) bt #0 0x00007f6d20b64781 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffde279f250 *** I don't know if you can make anything of this. People at systemd seem to think these are still usable somehow... https://github.com/systemd/systemd/issues/3883#issuecomment-239106337 -- You are receiving this mail because: You are watching all bug changes.
