SUMMARY When I start my pc and I log into the pc, KDE Connect crashes. FYI, I am using RHEL 9 as my linux distro. STEPS TO REPRODUCE 1. Go to the power button 2. Select Restart 3. Wait for pc to restart 4. Log into the pc 5. KDE Connect crashes OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x00007fb006e0d036 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23 #5 0x00007fb006e1062d in KdeConnectConfig::deviceInfo() () from /lib64/libkdeconnectcore.so.23 #6 0x00007fb006dfd0b5 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23 #7 0x00007fb0056dbc69 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x00007fb0056deeee in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #9 0x00007fb0056d2c8f in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x00007fb0063af533 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x00007fb0056a7958 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x00007fb0056f8ad3 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #13 0x00007fb0056f93cc in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #14 0x00007fb00412ef4f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x00007fb004184268 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #16 0x00007fb00412c713 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x00007fb0056f97d8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #18 0x00007fb0056a6362 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #19 0x00007fb0056ae894 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #20 0x0000557602f9d011 in main () [Inferior 1 (process 3032) detached]
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x00007fb006e0d036 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23 #5 0x00007fb006e1062d in KdeConnectConfig::deviceInfo() () from /lib64/libkdeconnectcore.so.23 #6 0x00007fb006dfd0b5 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23 #7 0x00007fb0056dbc69 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x00007fb0056deeee in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #9 0x00007fb0056d2c8f in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x00007fb0063af533 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x00007fb0056a7958 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x00007fb0056f8ad3 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #13 0x00007fb0056f93cc in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #14 0x00007fb00412ef4f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x00007fb004184268 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #16 0x00007fb00412c713 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x00007fb0056f97d8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #18 0x00007fb0056a6362 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #19 0x00007fb0056ae894 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #20 0x0000557602f9d011 in main () [Inferior 1 (process 3032) detached]
Sorry it doesn't work for you. Just an observation from a fellow KDE Connect user: So far, I have never seen it crash on any system. Judging that it is using libkdeconnectcore.so.23 I presume the software is quite old and it is likely fixed in a newer version. Perhaps you can install it using Flatpak, AppImage or something in the meanwhile.
Thank you for the bug report. This issue is fixed in more recent versions of KDE Connect. You can find more information in the linked bug report. *** This bug has been marked as a duplicate of bug 481760 ***