Bug 446299 - KDE Connect daemon crashes after receiving notification
Summary: KDE Connect daemon crashes after receiving notification
Status: RESOLVED DUPLICATE of bug 425231
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-30 21:38 UTC by djorz
Modified: 2024-08-02 16:31 UTC (History)
2 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 djorz 2021-11-30 21:38:46 UTC
Application: kdeconnectd (1.4.0)

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-59.34-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.3"

-- Information about the crash:
Android phone received a notification and KDE Connect immediately crashed 

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault
[KCrash Handler]
#4  0x00007f91def2cf73 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f91e1376930 in ?? () from /usr/lib64/libKF5Notifications.so.5
#6  0x00007f91e137960d in ?? () from /usr/lib64/libKF5Notifications.so.5
#7  0x00007f91e137982f in ?? () from /usr/lib64/libKF5Notifications.so.5
#8  0x00007f91df0b5fcf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#9  0x00007f91df5b4dcf in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQt5DBus.so.5
#10 0x00007f91df0b6a62 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#11 0x00007f91e019df9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#12 0x00007f91e01a55b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#13 0x00007f91df0863a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#14 0x00007f91df088f67 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#15 0x00007f91df0e3e13 in ?? () from /usr/lib64/libQt5Core.so.5
#16 0x00007f91d8b7d694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f91d8b7da30 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f91d8b7dabc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f91df0e342f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#20 0x00007f91df0845fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#21 0x00007f91df08d800 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#22 0x00005649862dac8d in ?? ()
#23 0x00007f91de61a34d in __libc_start_main () from /lib64/libc.so.6
#24 0x00005649862daeda in _start ()
[Inferior 1 (process 2303) detached]
Comment 1 Nicolas Fella 2021-12-07 21:43:05 UTC
It's hard to tell much without a symbolized backtrace. 1.4 is quite old and there's a good chance this is fixed in a more recent version
Comment 2 cwo 2024-08-02 16:31:46 UTC
Thank you for the bug report! This issue has already been filed and is believed to be fixed in current versions of Plasma.

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