Application that crashed: kbluetooth4 Version of the application: 0.3 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.1 Operating System: Linux 2.6.28-13-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: When resuming from Suspend KBluetooth crashes with a segmentation fault. The bug also happens (with the same backtrace) when having kbluetooth4 running and doing an "/etc/init.d/bluetooth stop". -- Backtrace: Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Segmentation fault [KCrash Handler] #5 QObject::property (this=0xfc9110, name=0x7fa7a15ec580 "_qdbus_slotCache") at kernel/qobject.cpp:3306 #6 0x00007fa7a15b42fe in QDBusConnectionPrivate::activateCall (this=0xf0ccf0, object=0x7fa7a132f2fa, flags=273, msg=@0xeef470) at qdbusintegrator.cpp:753 #7 0x00007fa7a15b4d81 in QDBusConnectionPrivate::activateObject (this=0xf0ccf0, node=@0xeef448, msg=@0xeef470, pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1352 #8 0x00007fa7a15b5098 in QDBusActivateObjectEvent::placeMetaCall (this=0xeef400) at qdbusintegrator.cpp:1469 #9 0x00007fa7a12a8f28 in QObject::event (this=0x7fffab877240, e=0xeef400) at kernel/qobject.cpp:1118 #10 0x00007fa7a06f231a in QApplication::event (this=0x7fffab877240, e=0xeef400) at kernel/qapplication.cpp:2318 #11 0x00007fa7a06ecb9d in QApplicationPrivate::notify_helper (this=0xe85ff0, receiver=0x7fffab877240, e=0xeef400) at kernel/qapplication.cpp:4057 #12 0x00007fa7a06f4dea in QApplication::notify (this=0x7fffab877240, receiver=0x7fffab877240, e=0xeef400) at kernel/qapplication.cpp:4022 #13 0x00007fa7a2da563b in KApplication::notify (this=0x7fffab877240, receiver=0x7fffab877240, event=0xeef400) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #14 0x00007fa7a1298dfc in QCoreApplication::notifyInternal (this=0x7fffab877240, receiver=0x7fffab877240, event=0xeef400) at kernel/qcoreapplication.cpp:610 #15 0x00007fa7a1299a6a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xe5f320) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #16 0x00007fa7a12c28a3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #17 0x00007fa79c4ee20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x00007fa79c4f18e0 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x00007fa79c4f1a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x00007fa7a12c252f in QEventDispatcherGlib::processEvents (this=0xe5eb50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324 #21 0x00007fa7a078570f in QGuiEventDispatcherGlib::processEvents (this=0x7fa7a15ec580, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x00007fa7a12976a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1417193008}) at kernel/qeventloop.cpp:149 #23 0x00007fa7a1297a6d in QEventLoop::exec (this=0x7fffab875ad0, flags={i = -1417192384}) at kernel/qeventloop.cpp:200 #24 0x00007fa7a15b8226 in QDBusConnectionPrivate::sendWithReply (this=0xfe4b00, message=@0x7fffab875e00, sendMode=<value optimized out>, timeout=-1) at qdbusintegrator.cpp:1787 #25 0x00007fa7a15a1aa3 in QDBusConnection::call (this=0xfce5a0, message=@0x3, mode=4294967295, timeout=4362581) at qdbusconnection.cpp:516 #26 0x00007fa7a15bf6df in QDBusAbstractInterface::callWithArgumentList (this=0x1007710, mode=QDBus::BlockWithGui, method=<value optimized out>, args=@0x7fffab875f00) at qdbusabstractinterface.cpp:402 #27 0x00007fa7a15c33ac in QDBusAbstractInterface::call (this=0x1007710, mode=QDBus::BlockWithGui, method=@0x7fffab876030, arg1=@0x7fffab875ff0, arg2=@0x7fffab875fe0, arg3=@0x7fffab875fd0, arg4=@0x7fffab875fc0, arg5=@0x7fffab875fb0, arg6=@0x7fffab875fa0, arg7=@0x7fffab875f90, arg8=@0x7fffab875f80) at qdbusabstractinterface.cpp:655 #28 0x0000000000420e2e in _start () This bug may be a duplicate of or related to bug 199044 Reported using DrKonqi
Merging with bug 199044. Thanks *** This bug has been marked as a duplicate of bug 199044 ***