Application: kdeconnectd (0.1) KDE Platform Version: 4.14.3 Qt Version: 4.8.5 Operating System: Linux 3.11.10-21-desktop x86_64 Distribution: "openSUSE 13.1 (Bottle) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: i was asking to pair my pc and smartphone from my pc same crash occurs when asking pairing from my smartphone. hypothesis : some days before there were an update of kde from 4.14.2 to 4.14.3 and there was an update of kde connect to 0.7.3 -- Backtrace: Application: kdeconnect (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f298b84c880 (LWP 8692))] Thread 3 (Thread 0x7f2979391700 (LWP 8693)): #0 0x00007f2988f857bd in poll () from /lib64/libc.so.6 #1 0x00007f2985793604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f298579370c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f298970ad76 in QEventDispatcherGlib::processEvents (this=0x1956fc0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007f29896dcd0f in QEventLoop::processEvents (this=this@entry=0x7f2979390d60, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f29896dd005 in QEventLoop::exec (this=this@entry=0x7f2979390d60, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f29895dbfef in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536 #7 0x00007f29895de68f in QThreadPrivate::start (arg=0x19598b0) at thread/qthread_unix.cpp:338 #8 0x00007f298a70c0db in start_thread () from /lib64/libpthread.so.0 #9 0x00007f2988f8e58d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2976d09700 (LWP 8822)): #0 0x00007f2988f857bd in poll () from /lib64/libc.so.6 #1 0x00007f2985793604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f298579370c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f298970ad76 in QEventDispatcherGlib::processEvents (this=0x1a78680, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007f29896dcd0f in QEventLoop::processEvents (this=this@entry=0x7f2976d08d20, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f29896dd005 in QEventLoop::exec (this=this@entry=0x7f2976d08d20, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f29895dbfef in QThread::exec (this=this@entry=0x1a6bfd0) at thread/qthread.cpp:536 #7 0x00007f29896be513 in QInotifyFileSystemWatcherEngine::run (this=0x1a6bfd0) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007f29895de68f in QThreadPrivate::start (arg=0x1a6bfd0) at thread/qthread_unix.cpp:338 #9 0x00007f298a70c0db in start_thread () from /lib64/libpthread.so.0 #10 0x00007f2988f8e58d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f298b84c880 (LWP 8692)): [KCrash Handler] #6 QCA::Provider::Context::provider (this=this@entry=0x0) at qca_core.cpp:887 #7 0x00007f29881fc8ed in QCA::PublicKey::toPEM (this=this@entry=0x7ffff3fd1e50) at qca_publickey.cpp:874 #8 0x00007f298b466e83 in Device::sendOwnPublicKey (this=this@entry=0x18e0450) at /usr/src/debug/kdeconnect-kde-0.7.3/core/device.cpp:422 #9 0x00007f298b467250 in Device::requestPair (this=0x18e0450) at /usr/src/debug/kdeconnect-kde-0.7.3/core/device.cpp:202 #10 0x00007f298b453495 in Device::qt_static_metacall (_o=_o@entry=0x18e0450, _id=_id@entry=6, _a=_a@entry=0x7ffff3fd2190, _c=QMetaObject::InvokeMetaMethod) at /usr/src/debug/kdeconnect-kde-0.7.3/build/core/moc_device.cpp:98 #11 0x00007f298b453f53 in qt_static_metacall (_a=0x7ffff3fd2190, _id=6, _c=QMetaObject::InvokeMetaMethod, _o=0x18e0450) at /usr/src/debug/kdeconnect-kde-0.7.3/build/core/moc_device.cpp:155 #12 Device::qt_metacall (this=0x18e0450, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7ffff3fd2190) at /usr/src/debug/kdeconnect-kde-0.7.3/build/core/moc_device.cpp:156 #13 0x00007f2987f19ead in QDBusConnectionPrivate::deliverCall (this=this@entry=0x175c090, object=object@entry=0x18e0450, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:951 #14 0x00007f2987f1b039 in QDBusConnectionPrivate::activateCall (this=this@entry=0x175c090, object=0x18e0450, flags=241, msg=...) at qdbusintegrator.cpp:856 #15 0x00007f2987f1b7bf in QDBusConnectionPrivate::activateObject (this=0x175c090, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1447 #16 0x00007f2987f1bbeb in QDBusActivateObjectEvent::placeMetaCall (this=0x1aaa7d0) at qdbusintegrator.cpp:1541 #17 0x00007f29896f611e in QObject::event (this=0x18e0450, e=<optimized out>) at kernel/qobject.cpp:1203 #18 0x00007f2989c228ac in QApplicationPrivate::notify_helper (this=this@entry=0x1762040, receiver=receiver@entry=0x18e0450, e=e@entry=0x1aaa7d0) at kernel/qapplication.cpp:4562 #19 0x00007f2989c28e70 in QApplication::notify (this=this@entry=0x7ffff3fd2b20, receiver=receiver@entry=0x18e0450, e=e@entry=0x1aaa7d0) at kernel/qapplication.cpp:4348 #20 0x00007f298b02156a in KApplication::notify (this=0x7ffff3fd2b20, receiver=0x18e0450, event=0x1aaa7d0) at /usr/src/debug/kdelibs-4.14.3/kdeui/kernel/kapplication.cpp:311 #21 0x00007f29896de0ad in QCoreApplication::notifyInternal (this=0x7ffff3fd2b20, receiver=receiver@entry=0x18e0450, event=event@entry=0x1aaa7d0) at kernel/qcoreapplication.cpp:949 #22 0x00007f29896e10ff in sendEvent (event=0x1aaa7d0, receiver=0x18e0450) at kernel/qcoreapplication.h:231 #23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1712740) at kernel/qcoreapplication.cpp:1573 #24 0x00007f29896e15a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466 #25 0x00007f298970b493 in sendPostedEvents () at kernel/qcoreapplication.h:236 #26 postEventSourceDispatch (s=0x175c000) at kernel/qeventdispatcher_glib.cpp:280 #27 0x00007f2985793316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f2985793668 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f298579370c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f298970ad55 in QEventDispatcherGlib::processEvents (this=0x1718660, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #31 0x00007f2989cbf936 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x00007f29896dcd0f in QEventLoop::processEvents (this=this@entry=0x7ffff3fd2a20, flags=...) at kernel/qeventloop.cpp:149 #33 0x00007f29896dd005 in QEventLoop::exec (this=this@entry=0x7ffff3fd2a20, flags=...) at kernel/qeventloop.cpp:204 #34 0x00007f29896e213b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #35 0x00007f2989c2106c in QApplication::exec () at kernel/qapplication.cpp:3823 #36 0x000000000040126e in main (argc=1, argv=0x7ffff3fd2c58) at /usr/src/debug/kdeconnect-kde-0.7.3/kded/kdeconnectd.cpp:85 Reported using DrKonqi
how all this occurs . i use Calibre (an app to manage a books library) . with calibre i convert a pdf to epub then i record the epub book in smartphone in extsdcard/books/ using dolphin selector , navigating to kdeconnect , sdcard then books folder then i quit calibre. after a while i want to copy a file to my smartphone then with dolphin i go to kdeconnect then to extsdcard then dolphin lists only one folder "Books". i check in my smartphone there is no pb : Android , Books , DCIM ... folders . are there in atxsdcard then i want to browse kdeconnect/dcim or kdeconnect/internal memory (i don't remember well the conventionnal naming of kdeconnect) then dolphin says "this folder does not exist" (approximate message) then i restart my phone then pb still there then i restart my pc then pb still there then i suppress the pairing of my smartphone and pc then i delete .kde4/share/apps/kdeconnect/ contents then i ask for pairing my pc to my smartphone then kdeconnectd crashes
i open a session with another user then i pair with success smartphone and pc (i asked for pairing from smartphone) then i switch to the current user then i stop kdeconnectd then i delete .kde4/share/apps/kdeconnect/ and .kde4/share/config/kdeconnectrc then i restart kdeconnectd then i ask for pairing from pc then kdeconnectd crashes then i restart kdeconnectd then i ask for pairing from smartphone then success ! result : it remains a pb . we can't pair by asking for pairing from pc only from smartphone.
Well It might be bug earlier but now it works fine. Please reopen it if problem persists.