Application: kdeconnectd (1.4.0) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-62-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I was copying a folder of 100 pictures with KDE Connect via my smartphone. I was copying from my phone to the laptop. I didn't change any setting. the copy process was blocking on one picture. So I stopped the process. I restrated to copy files but with less pictures around 5. KDE Connect crashed and stop the copy. Note : The copy process was freezing for some previous pictures, so I update all my application and Linux base as purposed by "Discover". The copy was working fine, excepting for some pictures the process was blocking but no crashing. -- Backtrace: Application: Démon KDE Connect (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x0000000000000067 in ?? () #5 0x00007ff114c8228d in KJob::kill (this=0x563a8eb121a0, verbosity=KJob::Quietly) at ./src/lib/jobs/kjob.cpp:106 #6 0x00007ff114c8228d in KJob::kill (this=0x563a8ebdab80, verbosity=verbosity@entry=KJob::EmitResult) at ./src/lib/jobs/kjob.cpp:106 #7 0x00007ff112d74c19 in KUiServerJobTracker::Private::_k_killJob (this=<optimized out>) at ./src/kuiserverjobtracker.cpp:62 #8 0x00007ff112d74d39 in KUiServerJobTracker::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/src/KF5JobWidgets_autogen/include/moc_kuiserverjobtracker.cpp:125 #9 0x00007ff1145194b9 in doActivate<false> (sender=0x563a94f6abb0, signal_index=3, argv=0x7ffc454c77f0) at kernel/qobject.cpp:3882 #10 0x00007ff114513f92 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7ff112f8ba20 <OrgKdeJobViewV2Interface::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #11 0x00007ff112d827e8 in OrgKdeJobViewV2Interface::cancelRequested (this=<optimized out>) at ./obj-x86_64-linux-gnu/src/jobviewiface.moc:225 #12 OrgKdeJobViewV2Interface::qt_static_metacall (_o=_o@entry=0x563a94f6abb0, _id=_id@entry=0, _a=_a@entry=0x7ffc454c7a00, _c=QMetaObject::InvokeMetaMethod) at ./obj-x86_64-linux-gnu/src/jobviewiface.moc:139 #13 0x00007ff112d82cd3 in OrgKdeJobViewV2Interface::qt_static_metacall (_a=0x7ffc454c7a00, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x563a94f6abb0) at ./obj-x86_64-linux-gnu/src/jobviewiface.moc:211 #14 OrgKdeJobViewV2Interface::qt_metacall (this=0x563a94f6abb0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffc454c7a00) at ./obj-x86_64-linux-gnu/src/jobviewiface.moc:212 #15 0x00007ff1149d55b8 in QDBusConnectionPrivate::deliverCall (this=<optimized out>, object=<optimized out>, msg=..., metaTypes=..., slotIdx=<optimized out>) at qdbusintegrator.cpp:1001 #16 0x00007ff11451157b in QObject::event (this=0x563a94f6abb0, e=0x7ff0f809f250) at kernel/qobject.cpp:1339 #17 0x00007ff1158fe9ac in QApplicationPrivate::notify_helper (this=this@entry=0x563a8e54ad40, receiver=receiver@entry=0x563a94f6abb0, e=e@entry=0x7ff0f809f250) at kernel/qapplication.cpp:3685 #18 0x00007ff115905bb0 in QApplication::notify (this=0x7ffc454c80e0, receiver=0x563a94f6abb0, e=0x7ff0f809f250) at kernel/qapplication.cpp:3431 #19 0x00007ff1144de4a8 in QCoreApplication::notifyInternal2 (receiver=0x563a94f6abb0, event=0x7ff0f809f250) at kernel/qcoreapplication.cpp:1075 #20 0x00007ff1144de67e in QCoreApplication::sendEvent (receiver=receiver@entry=0x563a94f6abb0, event=event@entry=0x7ff0f809f250) at kernel/qcoreapplication.cpp:1470 #21 0x00007ff1144e1121 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x563a8e549640) at kernel/qcoreapplication.cpp:1815 #22 0x00007ff1144e16b8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1674 #23 0x00007ff11453e103 in postEventSourceDispatch (s=0x563a8e5a81e0) at kernel/qeventdispatcher_glib.cpp:277 #24 0x00007ff10df8c417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007ff10df8c650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007ff10df8c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007ff11453d7ac in QEventDispatcherGlib::processEvents (this=0x563a8e5a0fb0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x00007ff1144dcd2a in QEventLoop::exec (this=this@entry=0x7ffc454c8020, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #29 0x00007ff1144e64a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383 #30 0x0000563a8d53558d in main (argc=<optimized out>, argv=<optimized out>) at ./daemon/kdeconnectd.cpp:180 Possible duplicates by query: bug 330323, bug 325348, bug 325256, bug 324380, bug 324100. Reported using DrKonqi
Created attachment 130672 [details] New crash information added by DrKonqi kdeconnectd (1.4.0) using Qt 5.14.2 - What I was doing when the application crashed: I was trying to copy 10 files from my Android phone but the copy stopped with the first file. My phone showed an alert from KDE Connect saying that the transfer failed but in KDE desktop the notification was just like stuck so I decided to stop it and that was the exact moment when KDE Connect crashed. -- Backtrace (Reduced): #4 KJob::kill (this=0x563a58a221f0, verbosity=KJob::Quietly) at ./src/lib/jobs/kjob.cpp:106 #5 0x00007fd4d543635d in KJob::kill (this=0x563a58a5fed0, verbosity=verbosity@entry=KJob::EmitResult) at ./src/lib/jobs/kjob.cpp:106 #6 0x00007fd4d23d6c19 in KUiServerJobTracker::Private::_k_killJob (this=<optimized out>) at ./src/kuiserverjobtracker.cpp:62 #7 0x00007fd4d23d6d39 in KUiServerJobTracker::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/src/KF5JobWidgets_autogen/include/moc_kuiserverjobtracker.cpp:125 #8 0x00007fd4d3b9d4b9 in doActivate<false> (sender=0x563a58a057c0, signal_index=3, argv=0x7ffc1b696b80) at kernel/qobject.cpp:3882
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Created attachment 153764 [details] attachment-15296-0.html Sorry, I don't remember what was the crash, so you can close the topic. Kind regards. Elsa Zapata Le mer. 12 oct. 2022, 05:49, Justin Zobel <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=423927 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" > when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug.