https://bugs.kde.org/show_bug.cgi?id=502251
--- Comment #7 from TraceyC <kde...@tlcnet.info> ---
Thanks for the backtrace. Unfortunately it's missing some debug symbols for
the following lines that we need to figure out exactly what's going wrong:
#5 0x00007f3e305ecfed n/a (breeze6.so + 0x76fed)
#6 0x00007f3e3ad388f4 n/a (libQt6Core.so.6 + 0x3388f4)
Could you please install debug symbols and attach a new symbolicated backtrace
generated by using `coredumpctl gdb` in a terminal window and getting a new
backtrace? 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!
(In reply to Tim from comment #6)
> Also seeing a crash in Simple-scan also with segmentation fault if that
> helps.
That's likely a different crash with a different cause. If Dr Konqui crash
reporter comes up, please use it to create a new bug report. Otherwise, you can
create a new report and get another backtrace manually like you did for this
report.
--
You are receiving this mail because:
You are watching all bug changes.
