https://bugs.kde.org/show_bug.cgi?id=502915
TraceyC <kde...@tlcnet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
CC| |kde...@tlcnet.info
Resolution|--- |BACKTRACE
--- Comment #1 from TraceyC <kde...@tlcnet.info> ---
Thank you for the bug report. I also got a crash while testing this, but the
backtrace looks different.
Unfortunately the backtrace from your crash is incomplete and missing debug
symbols for the following lines that we need to figure out exactly what's going
wrong:
#7 0x000072e1a368cd0e in ??? () at
/usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/kcms/systemsettings_qwidgets/kcm_kdeconnect.so
#8 0x000072e1cdc7afe4 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#10 0x000072e1cfaa091a in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.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!
My testing:
- On my Android phone, I used F-Droid to uninstall KDE Connect and then
install v 1.33.2
1. I attempted to unpair the old phone entry from KDE Connect on my laptop
running git-master Plasma.
KDE Connect hung and then crashed when I terminated it. I'll file that as a
separate report.
--
You are receiving this mail because:
You are watching all bug changes.
