https://bugs.kde.org/show_bug.cgi?id=527021
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |generic-crash Status|REPORTED |NEEDSINFO Product|kde |kwin Resolution|--- |BACKTRACE Version First|unspecified |6.7.5 Reported In| | See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=454054 CC| |[email protected] Keywords| |qt-crash Assignee|[email protected] |[email protected] |g | --- Comment #1 from TraceyC <[email protected]> --- Thank you for the bug report. I'm not able to reproduce this on git-master. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines (that have ???) that we need to figure out exactly what's going wrong: #5 0x00000008392f35f5 in ??? () at /usr/local/lib/qt6/libQt6DBus.so.6 #11 0x000000083abfcffc in ??? () at /usr/local/lib/qt6/libQt6Core.so.6 Could you please install debug packages and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. After you've attached the new backtrace, set this back to REPORTED. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
