https://bugs.kde.org/show_bug.cgi?id=514706
--- Comment #3 from TraceyC <[email protected]> --- That crash is probably relevant. The way to be sure is to cause the crash again, and see if another coredump for systemsettings is created. Does this happen? Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #14 0x00007f78051d734f n/a (libQt6Core.so.6 + 0x1d734f) #35 0x00005641d491e4a0 n/a (/usr/bin/systemsettings + 0x154a0) 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#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
