https://bugs.kde.org/show_bug.cgi?id=463334
--- Comment #2 from [email protected] --- I think I've got the coredump, although i'm not experienced with debugging at all, so I don't know exactly what I'm doing. Fedora has its abrt tool that is preinstalled for automated bug reports. It stores files for every crash in a directory. Among many files with info in that directory there is coredump in form of binary blob. It weights 269MB (!), so I cannot post it directly as an attachement here. https://www.dropbox.com/s/ntzd34pm3xlmrhy/kwin-coredump.tar.gz?dl=1 I roughly checked how to interact with coredumps using gdb and after downloading debug info for dependencies it printed this: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". --Type <RET> for more, q to quit, c to continue without paging-- Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. cProgram terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fe9f8972938 in KWin::DrmConnectorMode::~DrmConnectorMode (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kwin-5.26.4-1.fc37.x86_64/src/backends/drm/drm_object_connector.cpp:71 71 drmModeDestroyPropertyBlob(m_connector->gpu()->fd(), m_blobId); [Current thread is 1 (Thread 0x7fe9f19f0980 (LWP 1891))] -- You are receiving this mail because: You are watching all bug changes.
