Bug 201851 - Crashes after resumption from hibernation
Summary: Crashes after resumption from hibernation
Status: RESOLVED FIXED
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.4
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Tom Patzig
URL:
Keywords:
: 226352 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-29 05:15 UTC by Ralph Janke
Modified: 2010-02-11 23:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralph Janke 2009-07-29 05:15:00 UTC
Application that crashed: kbluetooth4
Version of the application: 0.3
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-14-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I just logged in after hibernation, and the application crashed.

 -- Backtrace:
Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Segmentation fault
[KCrash Handler]
#6  0xb7423090 in QMetaObject::disconnect (sender=0x924c608, signal_index=-1, receiver=0x9259918, method_index=4) at kernel/qobject.cpp:2789
#7  0xb7546004 in QDBusAdaptorConnector::disconnectAllSignals (this=0x9259918, obj=0x924c608) at qdbusabstractadaptor.cpp:238
#8  0xb75466b2 in QDBusAdaptorConnector::addAdaptor (this=0x9259918, adaptor=0x92f7958) at qdbusabstractadaptor.cpp:218
#9  0xb7546787 in QDBusAdaptorConnector::polish (this=0x9259918) at qdbusabstractadaptor.cpp:258
#10 0xb7546933 in QDBusAdaptorConnector::qt_metacall (this=0x9259918, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9326790) at qdbusabstractadaptor.cpp:365
#11 0xb741c8fb in QMetaCallEvent::placeMetaCall (this=0x9326760, object=0x9259918) at kernel/qobject.cpp:489
#12 0xb741e3a0 in QObject::event (this=0x9259918, e=0x9326760) at kernel/qobject.cpp:1118
#13 0xb6a15e9c in QApplicationPrivate::notify_helper (this=0x9206608, receiver=0x9259918, e=0x9326760) at kernel/qapplication.cpp:4084
#14 0xb6a1e19e in QApplication::notify (this=0xbffc71f0, receiver=0x9259918, e=0x9326760) at kernel/qapplication.cpp:3631
#15 0xb7c545cd in KApplication::notify (this=0xbffc71f0, receiver=0x9259918, event=0x9326760) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#16 0xb740da3b in QCoreApplication::notifyInternal (this=0xbffc71f0, receiver=0x9259918, event=0x9326760) at kernel/qcoreapplication.cpp:602
#17 0xb740e695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91e6b38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0xb740e88d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132
#19 0xb74397ef in postEventSourceDispatch (s=0x920a710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#20 0xb633bb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb633f0eb in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb633f268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb7439438 in QEventDispatcherGlib::processEvents (this=0x91e6d10, flags={i = -1073975240}) at kernel/qeventdispatcher_glib.cpp:323
#24 0xb6ab7365 in QGuiEventDispatcherGlib::processEvents (this=0x91e6d10, flags={i = -1073975192}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0xb740c06a in QEventLoop::processEvents (this=0xbffc70e0, flags={i = -1073975128}) at kernel/qeventloop.cpp:149
#26 0xb740c4aa in QEventLoop::exec (this=0xbffc70e0, flags={i = -1073975064}) at kernel/qeventloop.cpp:200
#27 0xb740e959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#28 0xb6a15d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#29 0x08051a5e in _start ()

Reported using DrKonqi
Comment 1 Alex Fiestas 2009-09-23 20:21:25 UTC
Hi, this bug should be fixed in 0.4 version, can you test it?

Thanks!
Comment 2 Alex Fiestas 2009-11-09 19:01:36 UTC
Well, this bug seems to be fixed now :) reopen it if it is not.
Comment 3 Jonathan Thomas 2010-02-11 23:49:57 UTC
*** Bug 226352 has been marked as a duplicate of this bug. ***