Bug 480179 - KDE Connect Daemon crashes
Summary: KDE Connect Daemon crashes
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: VHI crash
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: drkonqi
: 480181 480183 480184 480185 480197 480220 480226 480239 480244 481200 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-01-22 16:35 UTC by giotherobot
Modified: 2024-02-16 14:33 UTC (History)
19 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-2405181-0.html (811 bytes, text/html)
2024-01-24 05:51 UTC, Jacques Roux
Details

Note You need to log in before you can comment on or make changes to this bug.
Description giotherobot 2024-01-22 16:35:56 UTC
Application: kdeconnectd (23.08.4)

Qt Version: 5.15.12
Frameworks Version: 5.114.0
Operating System: Linux 6.5.0-14-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
After the latest updates the KDE Connect deamon (kdeconnectd) crashes continuously after unlocking my paired phone.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  Device::reloadPlugins (this=this@entry=0x558bd58b4ee0) at ./core/device.cpp:184
#5  0x00007f2944deb591 in Device::addLink (this=0x558bd58b4ee0, link=<optimized out>) at ./core/device.cpp:292
#6  0x00007f2944de63a1 in Daemon::onNewDeviceLink (this=0x7fff9282cc90, link=0x558bd59da6a0) at ./core/daemon.cpp:170
#7  0x00007f29436f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7fff9282b300, r=0x7fff9282cc90, this=0x558bd58a4770) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x558bd583d120, signal_index=3, argv=0x7fff9282b300) at kernel/qobject.cpp:3925
#9  0x00007f29436ede87 in QMetaObject::activate (sender=sender@entry=0x558bd583d120, m=m@entry=0x7f2944dfd7e0 <LinkProvider::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9282b300) at kernel/qobject.cpp:3985
#10 0x00007f2944dc5903 in LinkProvider::onConnectionReceived (this=this@entry=0x558bd583d120, _t1=<optimized out>, _t1@entry=0x558bd59da6a0) at ./obj-x86_64-linux-gnu/core/kdeconnectcore_autogen/CSWKE6ESUK/moc_linkprovider.cpp:178
#11 0x00007f2944dd07c4 in LanLinkProvider::addLink (this=this@entry=0x558bd583d120, socket=<optimized out>, deviceInfo=...) at ./core/backends/lan/lanlinkprovider.cpp:614
#12 0x00007f2944dd13cf in LanLinkProvider::encrypted (this=0x558bd583d120) at ./core/backends/lan/lanlinkprovider.cpp:377
#13 0x00007f29436f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7fff9282b600, r=0x558bd583d120, this=0x558bd59120f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate<false> (sender=0x558bd55a0470, signal_index=16, argv=0x7fff9282b600) at kernel/qobject.cpp:3925
#15 0x00007f29436ede87 in QMetaObject::activate (sender=sender@entry=0x558bd55a0470, m=m@entry=0x7f29433fa0e0 <QSslSocket::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985
#16 0x00007f29433646e4 in QSslSocket::encrypted (this=this@entry=0x558bd55a0470) at .moc/moc_qsslsocket.cpp:317
#17 0x00007f29433848b3 in QSslSocketBackendPrivate::continueHandshake (this=0x558bd58a1630) at ssl/qsslsocket_openssl.cpp:2045
#18 0x00007f294338b21b in QSslSocketBackendPrivate::startHandshake (this=this@entry=0x558bd58a1630) at ssl/qsslsocket_openssl.cpp:1480
#19 0x00007f294338b9e3 in QSslSocketBackendPrivate::transmit (this=0x558bd58a1630) at ssl/qsslsocket_openssl.cpp:1136
#20 0x00007f29436f4de8 in doActivate<false> (sender=0x558bd55a0490, signal_index=3, argv=0x7fff9282c860) at kernel/qobject.cpp:3937
#21 0x00007f29436ede87 in QMetaObject::activate (sender=sender@entry=0x558bd55a0490, m=m@entry=0x7f294395b960 <QIODevice::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985
#22 0x00007f29435e77c4 in QIODevice::readyRead (this=this@entry=0x558bd55a0490) at .moc/moc_qiodevice.cpp:190
#23 0x00007f294333a2ff in QAbstractSocketPrivate::emitReadyRead (channel=0, this=0x558bd597b310) at socket/qabstractsocket.cpp:1323
#24 QAbstractSocketPrivate::canReadNotification (this=0x558bd597b310) at socket/qabstractsocket.cpp:748
#25 0x00007f294334d439 in QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1274
#26 0x00007f294436c783 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x558bd57d7f30, e=0x7fff9282c9a0) at kernel/qapplication.cpp:3640
#27 0x00007f29436bd30a in QCoreApplication::notifyInternal2 (receiver=0x558bd57d7f30, event=0x7fff9282c9a0) at kernel/qcoreapplication.cpp:1064
#28 0x00007f2943717405 in socketNotifierSourceDispatch (source=0x558bd55d65d0) at kernel/qeventdispatcher_glib.cpp:107
#29 0x00007f2942120d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f2942176258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f294211e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f294371686e in QEventDispatcherGlib::processEvents (this=0x558bd55d6640, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#33 0x00007f29436bbc2b in QEventLoop::exec (this=this@entry=0x7fff9282cbb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x00007f29436c41d4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x0000558bd3637001 in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:186
[Inferior 1 (process 27947) detached]

Reported using DrKonqi
Comment 1 Nicolas Fella 2024-01-22 22:42:16 UTC
*** Bug 480183 has been marked as a duplicate of this bug. ***
Comment 2 Nicolas Fella 2024-01-22 22:42:27 UTC
*** Bug 480184 has been marked as a duplicate of this bug. ***
Comment 3 Nicolas Fella 2024-01-22 22:42:50 UTC
*** Bug 480181 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas Fella 2024-01-22 22:43:01 UTC
*** Bug 480185 has been marked as a duplicate of this bug. ***
Comment 5 Riccardo Robecchi 2024-01-22 23:02:00 UTC
The crash happens with the phone locked and with the screen turned off, so that is not the issue. It seems like Frameworks 5.114.0 introduced some change which simply makes the KDE Connect daemon crash.
The crash happens on X11 as well.
Comment 6 Nicolas Fella 2024-01-22 23:22:50 UTC
> kdeconnect.core: KPluginFactory could not load the plugin: "kdeconnect_findthisdevice" "Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_findthisdevice.so: (libKF5PulseAudioQt.so.3: cannot open shared object file: No such file or directory)"

This is a Neon issue
Comment 7 Nicolas Fella 2024-01-23 00:44:27 UTC
*** Bug 480197 has been marked as a duplicate of this bug. ***
Comment 8 DDR 2024-01-23 05:35:15 UTC
I'm seeing this myself, restarting after a recent update in the past two-three days here.
Comment 9 Nicolas Fella 2024-01-23 12:16:37 UTC
*** Bug 480220 has been marked as a duplicate of this bug. ***
Comment 10 Jonathan Riddell 2024-01-23 12:24:36 UTC
update release that should fix it
Comment 11 Nicolas Fella 2024-01-23 14:35:30 UTC
*** Bug 480226 has been marked as a duplicate of this bug. ***
Comment 12 Nicolas Fella 2024-01-23 18:57:25 UTC
*** Bug 480239 has been marked as a duplicate of this bug. ***
Comment 13 Jacques Roux 2024-01-24 05:51:56 UTC
Created attachment 165180 [details]
attachment-2405181-0.html

The update release works.
Thanks

On Tue, 23 Jan 2024 at 14:24, Jonathan Riddell <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=480179
>
> --- Comment #10 from Jonathan Riddell <jr@jriddell.org> ---
> update release that should fix it
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 14 Nicolas Fella 2024-01-26 13:10:34 UTC
*** Bug 480244 has been marked as a duplicate of this bug. ***
Comment 15 Robert Oldham 2024-01-31 03:17:52 UTC
The update works for me. Thank you for fixing it!
Comment 16 Nicolas Fella 2024-02-16 14:09:10 UTC
*** Bug 481200 has been marked as a duplicate of this bug. ***