https://bugs.kde.org/show_bug.cgi?id=519874
--- Comment #12 from [email protected] --- (In reply to TraceyC from comment #11) > Thanks for the backtrace. Unfortunately it's incomplete and missing debug > symbols for the following lines that we need to figure out exactly what's > going wrong: > > > #14 0x0000ffffa452dcac in ?? () from /usr/lib/libFcitx5Qt6DBusAddons.so.1 > #15 0x0000ffffadf2c004 in ?? () from /usr/lib/libQt6Core.so.6 > #19 0x0000ffff8d2a08fc in ?? () from /usr/lib/libQt6DBus.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. Thanks > again! I ran thread apply all backtrace full with debuginfod enabled, but those lines still show question marks. Please note that I am running Arch Linux ARM (aarch64) on an Android tablet (Xiaomi Pad 5). The official Arch Linux ARM repositories do not provide debug packages or a debuginfod server for aarch64, and the x86 debuginfod server does not cover ARM builds. Building a package as large as Qt6 with debug symbols locally on this tablet might seem impractical. If there's absolutely no other way, I will do it. -- You are receiving this mail because: You are watching all bug changes.
