Bug 195655

Summary: kbluetooth Crash after suspend to ram
Product: [Unmaintained] kde-bluetooth Reporter: Marek Tryliński <marek.trylinski>
Component: generalAssignee: Tom Patzig <tom>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marek Tryliński 2009-06-08 11:34:34 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-5-generic i686
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
i put my IBM X40 to suspend to RAM, after i woke it up - kbluetooth crashed

 -- Backtrace:
Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Segmentation fault
[KCrash Handler]
#6  0x0775cfcf in ?? ()
#7  0x00a68ad6 in QDBusConnectionPrivate::activateCall (this=0x8f7b0d0, object=0x8fc15a0, flags=273, msg=@0x8fbc1a8) at qdbusintegrator.cpp:753
#8  0x00a69704 in QDBusConnectionPrivate::activateObject (this=0x8f7b0d0, node=@0x8fbc194, msg=@0x8fbc1a8, pathStartPos=18) at qdbusintegrator.cpp:1352
#9  0x00a699ca in QDBusActivateObjectEvent::placeMetaCall (this=0x8fbc168) at qdbusintegrator.cpp:1469
#10 0x0135beee in QObject::event (this=0xbf879db0, e=0x8fbc168) at kernel/qobject.cpp:1118
#11 0x0134b43b in QCoreApplication::event (this=0xbf879db0, e=0x8fbc168) at kernel/qcoreapplication.cpp:1434
#12 0x01567746 in QApplication::event (this=0xbf879db0, e=0x8fbc168) at kernel/qapplication.cpp:2318
#13 0x01561c1c in QApplicationPrivate::notify_helper (this=0x8ef0380, receiver=0xbf879db0, e=0x8fbc168) at kernel/qapplication.cpp:4057
#14 0x015693f4 in QApplication::notify (this=0xbf879db0, receiver=0xbf879db0, e=0x8fbc168) at kernel/qapplication.cpp:4022
#15 0x0072304a in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0x0134bb1b in QCoreApplication::notifyInternal (this=0xbf879db0, receiver=0xbf879db0, event=0x8fbc168) at kernel/qcoreapplication.cpp:610
#17 0x0134c5e8 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8ed58b8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0x0134c7bd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#19 0x0137736f in postEventSourceDispatch (s=0x8ef6900) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#20 0x00cf6ad8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00cfa070 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00cfa1a3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x01376f9c in QEventDispatcherGlib::processEvents (this=0x8eef808, flags={i = 37}) at kernel/qeventdispatcher_glib.cpp:324
#24 0x01603975 in QGuiEventDispatcherGlib::processEvents (this=0x8eef808, flags={i = 37}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x0134a0a9 in QEventLoop::processEvents (this=0xbf878d1c, flags=) at kernel/qeventloop.cpp:149
#26 0x0134a4f2 in QEventLoop::exec (this=0xbf878d1c, flags={i = 5}) at kernel/qeventloop.cpp:200
#27 0x00a6ca41 in QDBusConnectionPrivate::sendWithReply (this=0x90ea500, message=@0xbf878e9c, sendMode=2, timeout=-1) at qdbusintegrator.cpp:1787
#28 0x00a5660b in QDBusConnection::call (this=0x8ef01b4, message=@0x1, mode=150738336, timeout=-1) at qdbusconnection.cpp:516
#29 0x00a743af in QDBusAbstractInterface::callWithArgumentList (this=0x8fea3e8, mode=QDBus::BlockWithGui, method=@0xbf879014, args=@0xbf878f3c) at qdbusabstractinterface.cpp:402
#30 0x00a77e4f in QDBusAbstractInterface::call (this=0x8fea3e8, mode=QDBus::BlockWithGui, method=@0xbf879014, arg1=@0xbf878ffc, arg2=@0xbf878ff0, arg3=@0xbf878fe4, arg4=@0xbf878fd8, 
    arg5=@0xbf878fcc, arg6=@0xbf878fc0, arg7=@0xbf878fb4, arg8=@0xbf878fa8) at qdbusabstractinterface.cpp:655
#31 0x08066ce3 in _start ()
Comment 1 Dario Andres 2009-06-09 01:24:16 UTC
Thanks

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