Bug 479448 - Segfault in kdeconnectd when retrieving device information
Summary: Segfault in kdeconnectd when retrieving device information
Status: RESOLVED DUPLICATE of bug 481760
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 23.08.4
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-05 21:37 UTC by Devin S.
Modified: 2024-08-02 13:57 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Crash report generated by KDE Crash Reporter. (3.29 KB, text/vnd.kde.kcrash-report)
2024-01-05 21:37 UTC, Devin S.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Devin S. 2024-01-05 21:37:34 UTC
Created attachment 164696 [details]
Crash report generated by KDE Crash Reporter.

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
KDE Connect Daemon appears to be running into problems when attempting to get device IDs. 

STEPS TO REPRODUCE
1. Open KDE Connect (or another application)
2. Wait a few seconds for the daemon to attempt to retrieve device information.
3. Daemon should crash with a segmentation fault.

OBSERVED RESULT
kdeconnectd crashes with a segmentation fault.

EXPECTED RESULT
kdeconnectd is able to retrieve device information with no issue.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.27 (x86_64, kernel: 6.5.0-14-generic)
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
I have noticed the crash message appearing as early as after login, while Plasma is loading. Additionally, the crash messages tend to appear when I'm using my device normally, and appear when I open Google Chrome or any other application as well.
Comment 1 cwo 2024-08-02 13:57:44 UTC
Thank you for the bug report! Another report that seems to cover the same issue has more activity, so I'm marking this as a duplicate of that bug.

*** This bug has been marked as a duplicate of bug 481760 ***