Bug 472323 - After reboot and logging into accout kdeconnect crashes
Summary: After reboot and logging into accout kdeconnect crashes
Status: RESOLVED DUPLICATE of bug 453875
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: 23.04.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-17 13:27 UTC by neilhellfeldt
Modified: 2024-07-31 08:04 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description neilhellfeldt 2023-07-17 13:27:26 UTC
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
***


STEPS TO REPRODUCE
1. Reboot System
2. Login
3.  kdeconnect crashes

OBSERVED RESULT
Crashing

EXPECTED RESULT
Not Crashing

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This happened after a recent update

Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f66ecd19a74 in KdeConnectConfig::deviceId() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23
#5  0x00007f66ecd1e49f in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23
#6  0x00007f66ecd0abb9 in LanLinkProvider::broadcastToNetwork() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23
#7  0x00007f66eb2f39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f66eb2f798e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f66eb2e7bf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f66ebf6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f66eb2bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f66eb314201 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f66eb314aec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f66e99d349d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f66e9a2e178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f66e99d21b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f66eb314e7a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f66eb2b97cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f66eb2c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x0000556fb201c0f6 in ?? ()
#21 0x00007f66ea823a90 in __libc_start_call_main (main=main@entry=0x556fb201bbf0, argc=argc@entry=1, argv=argv@entry=0x7ffecc38cbd8) at ../sysdeps/nptl/libc_start_call_main.h:58
#22 0x00007f66ea823b49 in __libc_start_main_impl (main=0x556fb201bbf0, argc=1, argv=0x7ffecc38cbd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffecc38cbc8) at ../csu/libc-start.c:360
#23 0x0000556fb201c315 in ?? ()
[Inferior 1 (process 4072) detached]
Comment 1 Ofca 2023-08-03 09:19:32 UTC
you may want to check for conflicting openssl installations on your OS, i.e. if you don't have Qt using one version, and kdeconnect another, perhaps in /usr/local/lib - I've seen similar traces and that was the root cause.

If not, you may also try building kdeconnect from sources:
https://community.kde.org/KDEConnect/Build_Linux

It may help with exposing the cause.
Comment 2 cwo 2024-07-31 08:04:18 UTC

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