Bug 433845

Summary:	KDE connect crashed after being unable to receive files
Product:	[Applications] kdeconnect	Reporter:	Dan Dascalescu <ddascalescu+kde>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	cwo.kde, joostvanesch
Priority:	NOR
Version First Reported In:	1.10
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Dan Dascalescu 2021-03-02 09:07:20 UTC

I was trying to send 257 file from my Huawei P30 Pro to the laptop. After initiating the sending from the Android device, a receiving notification popped up, but was stuck at file 1 (even though it was only ~300KB). Seeing as that wasn't working, I right clicked the KDE Connect notification and chose "Browse this device" (which BTW should be a prominent option in the app, but it's absent). Then I was able to browse the DCIM/Camera directory and started copying files that way.

At that point I clicked the stop icon in the receiving notification, since it wasn't working anyway. KDE Connect crashed, and it took down with it the second copying process, which was going on fine.

As usual (bug 433843), the automatic Crash Reporter failed to load symbols, so here's the stack trace:

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

[New LWP 1496]
[New LWP 1506]
[New LWP 1515]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f9ec6a5faff in __GI___poll (fds=0x7fffd433a528, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f9ec2f498c0 (LWP 1461))]

Thread 4 (Thread 0x7f9ebadee700 (LWP 1515)):
#0  __GI___libc_read (nbytes=16, buf=0x7f9ebadedad0, fd=10) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=10, buf=0x7f9ebadedad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x00007f9ec568589f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f9ec563ccde in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f9ec563d132 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f9ec563d2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f9ec702cfbb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f9ec6fd11ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9ec6deba12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f9ec6decbac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f9ec5faf609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#11 0x00007f9ec6a6c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f9ebbfff700 (LWP 1506)):
#0  0x00007f9ec6a5faff in __GI___poll (fds=0x7f9eb4004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f9ec563d18e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f9ec563d2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f9ec702cfbb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f9ec6fd11ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f9ec6deba12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f9ec728cf4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f9ec6decbac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9ec5faf609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007f9ec6a6c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f9ec2388700 (LWP 1496)):
#0  0x00007f9ec6a5faff in __GI___poll (fds=0x7f9ec2387be8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f9ec5306c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f9ec530890a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f9ec28c0d58 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f9ec6decbac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f9ec5faf609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f9ec6a6c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f9ec2f498c0 (LWP 1461)):
[KCrash Handler]
#4  0x00007f9ec80d5ea0 in KJob::kill(KJob::KillVerbosity) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#5  0x00007f9ec80d5eec in KJob::kill(KJob::KillVerbosity) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#6  0x00007f9ec65a258f in ?? () from /lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#7  0x00007f9ec70096f0 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9ec65afab0 in ?? () from /lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9  0x00007f9ec65afff1 in ?? () from /lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#10 0x00007f9ec729955b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x00007f9ec7000239 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f9ec7b47dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f9ec7b50bb8 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f9ec6fd269a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9ec6fd4fa1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f9ec702d947 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f9ec563cf9d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f9ec563d220 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f9ec563d2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f9ec702cfa2 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f9ec6fd11ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f9ec6fd9354 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00005645ebd9bf87 in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:173
[Inferior 1 (process 1461) detached]

Comment 1 joostvanesch 2021-12-08 14:29:46 UTC

Created attachment 144352 [details]
New crash information added by DrKonqi

kdeconnectd (21.08.3) using Qt 5.15.2

- What I was doing when the application crashed:
Trying to send about 200 files from my phone to my laptop.
I got a notification on my laptop saying that one file was recieved but it stayed stuck there. 
That is when connect crashed

-- Backtrace (Reduced):
#6  KJob::kill (this=0x56101bac21b0, verbosity=KJob::Quietly) at /usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/src/lib/jobs/kjob.cpp:109
#7  0x00007fddd231c09c in KJob::kill (this=0x7fddbc01d850, verbosity=KJob::EmitResult) at /usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/src/lib/jobs/kjob.cpp:113
#8  0x00007fddd116d078 in doActivate<false> (sender=0x56101ba20a70, signal_index=3, argv=0x7ffc83cd55a0) at kernel/qobject.cpp:3898
[...]
#10 0x00007fddd0697733 in OrgKdeJobViewV2Interface::resumeRequested (this=<optimized out>) at /usr/src/debug/kjobwidgets-5.88.0-1.1.x86_64/build/src/jobviewiface.moc:231
#11 0x00007fddd069d1f3 in OrgKdeJobViewV2Interface::qt_metacall (this=0x56101ba20a70, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffc83cd56e0) at /usr/src/debug/kjobwidgets-5.88.0-1.1.x86_64/build/src/jobviewiface.moc:212

Comment 2 cwo 2024-07-31 13:58:32 UTC

Thank you for the bug report! Another bug report that seems to cover the same crash has a more informative stack trace, so I'm marking this as a duplicate of that one.

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