| Summary: | CTD when unpairing old copy of device on desktop PC after 1.33.3 update on mobile | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | poomklao |
| Component: | kcm_kdeconnect | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | albertvaka, kdedev, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=474202 https://bugs.kde.org/show_bug.cgi?id=502947 https://bugs.kde.org/show_bug.cgi?id=498051 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/164347/events/8d3e806bd4fb40e090d7b30d6ddd5dec/ | ||
| Attachments: | kcmkdec-konfusdai-bt-sym.gdb | ||
|
Description
poomklao
2025-04-17 08:36:49 UTC
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. Created attachment 180372 [details]
kcmkdec-konfusdai-bt-sym.gdb
Here ya go! See attached (my main client would likely mangle it)
On that note, drkonqi-pk-debug-installer also consistently crashed at the time. I'll try to repro, then file a new bug. (Is there a way to activate drkonqi on an old coredump?)
Thanks so much for the updated backtrace, that's definitely more useful. It looks like the same backtrace as bug 498051, which we were able to reproduce. I'm marking this as a duplicate, please follow the other report for updates on this issue. To get more information from an older coredump, you might try the Crashed Process Viewer. Also have a look at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl *** This bug has been marked as a duplicate of bug 498051 *** |