Application: kbluetooth (0.4) KDE Platform Version: 4.4.2 (KDE 4.4.2) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.34-rc5 i686 Distribution (Platform): Gentoo Packages -- Information about the crash: Happend before with the same reasons (if that is the reason) when I was "away" with switch user. But without usefull backtrace so I recompiled all the bluez* with debug enabled. Seems that now it is more verbose. The crash can be reproduced some of the time. -- Backtrace: Application: KBluetooth (kbluetooth), signal: Segmentation fault [KCrash Handler] #6 0xb6c8df0b in QObject::connect (sender=0x95fd3d8, signal=0x8078100 "2result(KJob*)", receiver=0xbfc38be4, method=0x8078080 "1slotFileReceiveComplete(KJob*)", type=Qt::AutoConnection) at kernel/qobject.cpp:2510 #7 0x08056c15 in KBlueTray::slotServerSessionTransferStarted (this=0xbfc38be4, job=0x95fd3d8) at /home/porttmp/portage/net-wireless/kbluetooth-9999/work/kbluetooth-9999/src/trayicon.cpp:780 #8 0x08055456 in KBlueTray::qt_metacall (this=0xbfc38be4, _c=QMetaObject::InvokeMetaMethod, _id=50, _a=0xbfc37378) at /home/porttmp/portage/net-wireless/kbluetooth-9999/work/kbluetooth-9999_build/src/moc_trayicon.cpp:174 #9 0xb6c7acdd in QMetaObject::metacall (object=0xbfc38be4, cl=QMetaObject::InvokeMetaMethod, idx=50, argv=0xbfc37378) at kernel/qmetaobject.cpp:237 #10 0xb6c8adb7 in QMetaObject::activate (sender=0x9515c50, m=0x80750b8, local_signal_index=2, argv=<value optimized out>) at kernel/qobject.cpp:3285 #11 0x08053b35 in ObexServerSession::transferStarted (this=0x9515c50, _t1=0x95fd3d8) at /home/porttmp/portage/net-wireless/kbluetooth-9999/work/kbluetooth-9999_build/src/moc_obexserversession.cpp:119 #12 0x0806c4b2 in ObexServerSession::slotTransferStarted (this=0x9515c50, filename=..., local_path=..., total_bytes=639230) at /home/porttmp/portage/net-wireless/kbluetooth-9999/work/kbluetooth-9999/src/obexserver/obexserversession.cpp:110 #13 0x08054679 in ObexServerSession::qt_metacall (this=0x9515c50, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfc374e8) at /home/porttmp/portage/net-wireless/kbluetooth-9999/work/kbluetooth-9999_build/src/moc_obexserversession.cpp:94 #14 0xb6db9c8e in QDBusConnectionPrivate::deliverCall (this=0x9530680, object=0x9515c50, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:904 #15 0xb6dc5ae7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x95fd420, object=0x9515c50) at qdbusintegrator_p.h:101 #16 0xb6c86276 in QObject::event (this=0x9515c50, e=0x95fd420) at kernel/qobject.cpp:1240 #17 0xb60ff22f in QApplicationPrivate::notify_helper (this=0x93e9438, receiver=0x9515c50, e=0x95fd420) at kernel/qapplication.cpp:4300 #18 0xb61078cf in QApplication::notify (this=0xbfc38cac, receiver=0x9515c50, e=0x95fd420) at kernel/qapplication.cpp:4183 #19 0xb7372721 in KApplication::notify (this=0xbfc38cac, receiver=0x9515c50, event=0x95fd420) at /home/porttmp/portage/kde-base/kdelibs-4.4.2/work/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302 #20 0xb6c73c62 in QCoreApplication::notifyInternal (this=0xbfc38cac, receiver=0x9515c50, event=0x95fd420) at kernel/qcoreapplication.cpp:704 #21 0xb6c74bf4 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x93cc850) at kernel/qcoreapplication.h:215 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x93cc850) at kernel/qcoreapplication.cpp:1345 #23 0xb6c74e2e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #24 0xb6ca3f70 in QCoreApplication::sendPostedEvents (s=0x93edf90) at kernel/qcoreapplication.h:220 #25 postEventSourceDispatch (s=0x93edf90) at kernel/qeventdispatcher_glib.cpp:276 #26 0xb5673b9f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 Possible duplicates by query: bug 229076. Reported using DrKonqi
Created attachment 43557 [details] New crash information added by DrKonqi Seems that I can reproduce that. Don't know how, since I'm „away”. (; This is some nasty bug that I tried to reproduce before, but without any usefull backtrace. Seems that bluez with debug support added some more usefull info here.
*** This bug has been marked as a duplicate of bug 270702 ***