Application: kdeconnectd (1.4.0) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.11-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: I was working on the computer, but not interacting with KDE Connect nor with the phone. It was a crash out of the blue. The phone was charging, and also I was in the middle of a call (using a bluetooth headphone paired to the phone). But both of those events were started more than 10 minutes before the crash so I think it's unlikely they are related to the crash. The phone has Android version 10, and the KDE Connect app on it is at version 1.16.0. -- Backtrace: Application: KDE-Connect-Dienst (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x00007fe8eeb0a5f4 in std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<optimized out>) at /usr/include/c++/10/bits/atomic_base.h:426 #5 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger<int>::loadRelaxed (this=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #8 QString::operator= (this=0x55583e793ce8, other=...) at text/qstring.cpp:2408 #9 0x00007fe8f008d384 in LanLinkProvider::configureSslSocket (socket=0x7fe8d8006610, deviceId=..., isDeviceTrusted=<optimized out>) at /usr/src/debug/kde-connect-20.08.1-1.fc33.x86_64/core/backends/lan/lanlinkprovider.cpp:479 #10 0x00007fe8f0094b2c in CompositeUploadJob::newConnection (this=0x55583e727680) at /usr/src/debug/kde-connect-20.08.1-1.fc33.x86_64/core/backends/lan/compositeuploadjob.cpp:162 #11 0x00007fe8eec51386 in QtPrivate::QSlotObjectBase::call (a=0x7fff431e1110, r=0x55583e727680, this=0x55583e6d39a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate<false> (sender=0x55583e60f940, signal_index=3, argv=0x7fff431e1110) at kernel/qobject.cpp:3886 #13 0x00007fe8ee428fbb in QTcpServerPrivate::readNotification (this=0x7fe8d0011b00) at socket/qtcpserver.cpp:224 #14 0x00007fe8ee433c79 in QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1274 #15 0x00007fe8ef743ec3 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55583e5be8c0, e=0x7fff431e1250) at kernel/qapplication.cpp:3632 #16 0x00007fe8eec21bd8 in QCoreApplication::notifyInternal2 (receiver=0x55583e5be8c0, event=0x7fff431e1250) at kernel/qcoreapplication.cpp:1063 #17 0x00007fe8eec6f157 in socketNotifierSourceDispatch (source=0x55583e204f20) at kernel/qeventdispatcher_glib.cpp:107 #18 0x00007fe8ed28596f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x00007fe8ed2d7758 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #20 0x00007fe8ed282d43 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x00007fe8eec6e6f3 in QEventDispatcherGlib::processEvents (this=0x55583e212070, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x00007fe8eec2057b in QEventLoop::exec (this=0x7fff431e1460, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x00007fe8eec281b4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x000055583c707971 in main () [Inferior 1 (process 2252) detached] Possible duplicates by query: bug 429420, bug 427021, bug 425205, bug 424171, bug 422092. Reported using DrKonqi
Does this still happen with updated software?
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!
(In reply to Riccardo Robecchi from comment #1) > Does this still happen with updated software? No, it's been a while since I last had this problem.
(In reply to Thiago Jung Bauermann from comment #3) > (In reply to Riccardo Robecchi from comment #1) > > Does this still happen with updated software? > > No, it's been a while since I last had this problem. I'm marking this as fixed then. Thanks for the feedback.