Bug 472528 - KDE Connect crashes when calling the phone and displaying a notification
Summary: KDE Connect crashes when calling the phone and displaying a notification
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 23.04.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
: 455832 459411 471249 485284 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-07-23 10:53 UTC by Debraym Tea
Modified: 2024-08-04 11:52 UTC (History)
6 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 Debraym Tea 2023-07-23 10:53:50 UTC
Application: kdeconnectd (23.04.3)

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 5.14.21-150500.53-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.5"
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
The phone received a call and a call notification was displayed on the computer, deciding to skip it kde connect crashed with an error.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Фоновая служба KDE Connect (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  KNotification::id (this=this@entry=0x56130559baf0) at /usr/src/debug/knotifications-5.108.0-lp155.290.1.x86_64/src/knotification.cpp:519
#5  0x00007fa994b89a3a in KNotificationManager::notifyPluginFinished (this=<optimized out>, notification=0x56130559baf0) at /usr/src/debug/knotifications-5.108.0-lp155.290.1.x86_64/src/knotificationmanager.cpp:228
#6  0x00007fa9937589bb in QtPrivate::QSlotObjectBase::call (a=0x7ffc70d95a60, r=0x7fa994bc9090 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7  doActivate<false> (sender=0x5613056d77f0, signal_index=3, argv=0x7ffc70d95a60) at kernel/qobject.cpp:3925
#8  0x00007fa993751d82 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7fa994bc73e0 <KNotificationPlugin::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc70d95a60) at kernel/qobject.cpp:3985
#9  0x00007fa994b7ff1f in KNotificationPlugin::finished (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/knotifications-5.108.0-lp155.290.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173
#10 0x00007fa994bae99a in NotifyByAudio::finishNotification (this=this@entry=0x5613056d77f0, notification=notification@entry=0x56130559baf0, id=<optimized out>) at /usr/src/debug/knotifications-5.108.0-lp155.290.1.x86_64/src/notifybyaudio_canberra.cpp:189
#11 0x00007fa994baeb00 in NotifyByAudio::finishCallback (this=0x5613056d77f0, id=<optimized out>, error_code=<optimized out>) at /usr/src/debug/knotifications-5.108.0-lp155.290.1.x86_64/src/notifybyaudio_canberra.cpp:159
#12 0x00007fa99374f39b in QObject::event (this=0x5613056d77f0, e=0x7fa980048ae0) at kernel/qobject.cpp:1347
#13 0x00007fa9942d081c in QApplicationPrivate::notify_helper (this=this@entry=0x561304f95f60, receiver=receiver@entry=0x5613056d77f0, e=e@entry=0x7fa980048ae0) at kernel/qapplication.cpp:3640
#14 0x00007fa9942d75df in QApplication::notify (this=<optimized out>, receiver=0x5613056d77f0, e=0x7fa980048ae0) at kernel/qapplication.cpp:3164
#15 0x00007fa99371b4e3 in QCoreApplication::notifyInternal2 (receiver=0x5613056d77f0, event=0x7fa980048ae0) at kernel/qcoreapplication.cpp:1064
#16 0x00007fa99371b6be in QCoreApplication::sendEvent (receiver=receiver@entry=0x5613056d77f0, event=event@entry=0x7fa980048ae0) at kernel/qcoreapplication.cpp:1462
#17 0x00007fa99371df01 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x561304f7a0d0) at kernel/qcoreapplication.cpp:1821
#18 0x00007fa99371e488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680
#19 0x00007fa99377e263 in postEventSourceDispatch (s=0x56130505daa0) at kernel/qeventdispatcher_glib.cpp:277
#20 0x00007fa9905c282b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fa9905c2bd0 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fa9905c2c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fa99377d90c in QEventDispatcherGlib::processEvents (this=0x561305060580, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x00007fa993719d4a in QEventLoop::exec (this=this@entry=0x7ffc70d960b0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:235
#25 0x00007fa993723587 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375
#26 0x00007fa993b703fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870
#27 0x00007fa9942d0775 in QApplication::exec () at kernel/qapplication.cpp:2832
#28 0x00005613046c6efe in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdeconnect-kde-23.04.3-lp155.66.2.x86_64/daemon/kdeconnectd.cpp:185
[Inferior 1 (process 2060) detached]

The reporter indicates this bug may be a duplicate of or related to bug 471249.

Reported using DrKonqi
Comment 1 Nicolas Fella 2024-04-09 21:31:03 UTC
*** Bug 471249 has been marked as a duplicate of this bug. ***
Comment 2 Nicolas Fella 2024-04-09 21:31:07 UTC
*** Bug 455832 has been marked as a duplicate of this bug. ***
Comment 3 Nicolas Fella 2024-04-09 21:31:23 UTC
*** Bug 485284 has been marked as a duplicate of this bug. ***
Comment 4 Albert Vaca Cintora 2024-04-12 07:31:52 UTC
This should be fixed in KDE Connect version 1.30.1 for Android, which we just pushed. It might take a couple days for you to get the update, though. Sorry for the inconvenience :(
Comment 5 Albert Vaca Cintora 2024-04-12 07:33:11 UTC
Ah, wait, nope. The crash I fixed was on the Android side. This is on the desktop. Reopening.
Comment 6 cwo 2024-08-04 11:51:23 UTC
*** This bug has been marked as a duplicate of bug 459411 ***
Comment 7 cwo 2024-08-04 11:52:03 UTC
Oops sorry, that was supposed to be the other way around
Comment 8 cwo 2024-08-04 11:52:50 UTC
*** Bug 459411 has been marked as a duplicate of this bug. ***