https://bugs.kde.org/show_bug.cgi?id=508865
--- Comment #4 from Matthew <[email protected]> --- (In reply to Matthew from comment #3) > (In reply to TraceyC from comment #2) > > Thank you for the bug report. Unfortunately the backtrace is incomplete and > > missing debug symbols for the following lines that we need to figure out > > exactly what's going wrong: > > > > #4 0x00007f48856d5737 in ??? () at /usr/lib64/libQt6Network.so.6 > > #5 0x00007f4886c6fd67 in ??? () at /usr/lib64/libQt6Core.so.6 > > > > Could you please install debug symbols 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! > > Could you show the exact steps on how to do this and I will happily do this matt@matt ~ $ sudo coredumpctl gdb PID: 595563 (conftest) UID: 250 (portage) GID: 250 (portage) Signal: 6 (ABRT) Timestamp: Thu 2025-08-28 19:01:07 BST (3h 3min ago) Command Line: ./conftest Executable: /var/tmp/portage/dev-libs/libsodium-1.0.20_p20250606/work/libsodium-stable-abi_x86_64.amd64/conftest Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/[email protected] Unit: [email protected] User Unit: [email protected] Slice: user-1000.slice Owner UID: 1000 (matt) Boot ID: 0f8bcb460200414da23ea82c82c8a85f Machine ID: e1ffbd53ad614b419bce718a738c3a95 Hostname: localhost Storage: none Message: Process 595563 (conftest) of user 250 terminated abnormally without generating a coredump. Coredump entry has no core attached (neither internally in the journal nor externally on disk). matt@matt ~ $ -- You are receiving this mail because: You are watching all bug changes.
