Bug 196354

Summary: bluetooth crashed aparently without any interaction
Product: [Unmaintained] kde-bluetooth Reporter: Rafael Carreras <rcarreras>
Component: generalAssignee: Tom Patzig <tom>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rafael Carreras 2009-06-13 17:44:24 UTC
Application that crashed: kbluetooth4
Version of the application: 0.3
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-8-generic i686
Distribution: Ubuntu karmic (development branch)

 -- Backtrace:
Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Segmentation fault
[KCrash Handler]
#6  0x07000000 in ?? ()
#7  0x0031aad6 in QDBusConnectionPrivate::activateCall (this=0x8464ac8, object=0x84a9258, flags=273, msg=@0x84ab3a0) at qdbusintegrator.cpp:753
#8  0x0031b704 in QDBusConnectionPrivate::activateObject (this=0x8464ac8, node=@0x84ab38c, msg=@0x84ab3a0, pathStartPos=18) at qdbusintegrator.cpp:1352
#9  0x0031b9ca in QDBusActivateObjectEvent::placeMetaCall (this=0x84ab360) at qdbusintegrator.cpp:1469
#10 0x062e5eee in QObject::event (this=0xbf90a1b0, e=0x84ab360) at kernel/qobject.cpp:1118
#11 0x062d543b in QCoreApplication::event (this=0xbf90a1b0, e=0x84ab360) at kernel/qcoreapplication.cpp:1434
#12 0x03725746 in QApplication::event (this=0xbf90a1b0, e=0x84ab360) at kernel/qapplication.cpp:2318
#13 0x0371fc1c in QApplicationPrivate::notify_helper (this=0x83d1ed0, receiver=0xbf90a1b0, e=0x84ab360) at kernel/qapplication.cpp:4057
#14 0x037273f4 in QApplication::notify (this=0xbf90a1b0, receiver=0xbf90a1b0, e=0x84ab360) at kernel/qapplication.cpp:4022
#15 0x00a3d04a in KApplication::notify (this=0xbf90a1b0, receiver=0xbf90a1b0, event=0x84ab360) at ../../kdeui/kernel/kapplication.cpp:302
#16 0x062d5b1b in QCoreApplication::notifyInternal (this=0xbf90a1b0, receiver=0xbf90a1b0, event=0x84ab360) at kernel/qcoreapplication.cpp:610
#17 0x062d65e8 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x83b28b8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0x062d67bd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#19 0x0630136f in postEventSourceDispatch (s=0x83d4120) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#20 0x05c92ad8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x05c96070 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x05c961a3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x06300f9c in QEventDispatcherGlib::processEvents (this=0x83cc8c8, flags={i = 37}) at kernel/qeventdispatcher_glib.cpp:324
#24 0x037c1975 in QGuiEventDispatcherGlib::processEvents (this=0x83cc8c8, flags={i = 37}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x062d40a9 in QEventLoop::processEvents (this=0xbf90911c, flags=) at kernel/qeventloop.cpp:149
#26 0x062d44f2 in QEventLoop::exec (this=0xbf90911c, flags={i = 5}) at kernel/qeventloop.cpp:200
#27 0x0031ea41 in QDBusConnectionPrivate::sendWithReply (this=0x84afd38, message=@0xbf90929c, sendMode=2, timeout=-1) at qdbusintegrator.cpp:1787
#28 0x0030860b in QDBusConnection::call (this=0x84b66a4, message=@0x1, mode=139104856, timeout=-1) at qdbusconnection.cpp:516
#29 0x003263af in QDBusAbstractInterface::callWithArgumentList (this=0x84bd9a8, mode=QDBus::BlockWithGui, method=@0xbf909414, args=@0xbf90933c) at qdbusabstractinterface.cpp:402
#30 0x00329e4f in QDBusAbstractInterface::call (this=0x84bd9a8, mode=QDBus::BlockWithGui, method=@0xbf909414, arg1=@0xbf9093fc, arg2=@0xbf9093f0, arg3=@0xbf9093e4, arg4=@0xbf9093d8, 
    arg5=@0xbf9093cc, arg6=@0xbf9093c0, arg7=@0xbf9093b4, arg8=@0xbf9093a8) at qdbusabstractinterface.cpp:655
#31 0x08066ce3 in _start ()

This bug may be a duplicate of or related to bug 172597

Reported using DrKonqi
Comment 1 Christophe Marin 2009-06-14 15:54:38 UTC

*** This bug has been marked as a duplicate of bug 181268 ***