Summary: | Crashed after resume from suspend | ||
---|---|---|---|
Product: | [Unmaintained] kbluetooth | Reporter: | Pascal d'Hermilly <pascal> |
Component: | general | Assignee: | Tom Patzig <tom> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | afiestas, andresbajotierra, dendraya, dima, finex, gaddman, kde-bugs, marcus, metamorfozis |
Priority: | NOR | ||
Version: | 0.4 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Pascal d'Hermilly
2009-07-05 17:05:04 UTC
Bug 188690 could be related to this. Yes, only difference seems to be that this is on KDE 4.3 RC1 and that the stack trace is should reflect the code better. The second backtrace at bug 188690 has some other functions related to Obex and Kbluetooth libraries, but this one hasn't them. (I wonder if that could be a different issue) Thanks *** Bug 200134 has been marked as a duplicate of this bug. *** *** Bug 200739 has been marked as a duplicate of this bug. *** I think we should mark this as confirmed Confirmed on Debian KDE 4.3, kdebluetooth 1:0.3-1. Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4), signal: Segmentation fault [KCrash Handler] #5 0x00000000000004e0 in ?? () #6 0x00007f9f1453f827 in QObject::property (this=0x81b200, name=0x7f9f148823f0 "_qdbus_slotCache") at kernel/qobject.cpp:3292 #7 0x00007f9f1484a97e in QDBusConnectionPrivate::activateCall (this=0x79db30, object=0x81b200, flags=273, msg=...) at qdbusintegrator.cpp:753 #8 0x00007f9f1484b3e1 in QDBusConnectionPrivate::activateObject (this=0x79db30, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1347 #9 0x00007f9f1484b6f8 in QDBusActivateObjectEvent::placeMetaCall (this=0x810c80) at qdbusintegrator.cpp:1464 #10 0x00007f9f1453cee8 in QObject::event (this=0x7fff08c622c0, e=0x810c80) at kernel/qobject.cpp:1110 #11 0x00007f9f139aadfa in QApplication::event (this=0x7fff08c622c0, e=0x810c80) at kernel/qapplication.cpp:2317 #12 0x00007f9f139a57ad in QApplicationPrivate::notify_helper (this=0x65c470, receiver=0x7fff08c622c0, e=0x810c80) at kernel/qapplication.cpp:4056 #13 0x00007f9f139ad80a in QApplication::notify (this=0x7fff08c622c0, receiver=0x7fff08c622c0, e=0x810c80) at kernel/qapplication.cpp:4021 #14 0x00007f9f16064b2b in KApplication::notify (this=0x7fff08c622c0, receiver=0x7fff08c622c0, event=0x810c80) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x00007f9f1452d49c in QCoreApplication::notifyInternal (this=0x7fff08c622c0, receiver=0x7fff08c622c0, event=0x810c80) at kernel/qcoreapplication.cpp:610 #16 0x00007f9f1452e0e4 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x635b50) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x635b50) at kernel/qcoreapplication.cpp:1247 #18 0x00007f9f14555ef3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #19 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210 #20 0x00007f9f105ea7aa in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0x00007f9f105eddf8 in ?? () from /usr/lib/libglib-2.0.so.0 #22 0x00007f9f105edfac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0x00007f9f14555b7f in QEventDispatcherGlib::processEvents (this=0x635360, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #24 0x00007f9f13a3c5ef in QGuiEventDispatcherGlib::processEvents (this=0x81b200, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x00007f9f1452bd62 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #26 0x00007f9f1452c134 in QEventLoop::exec (this=0x7fff08c60b50, flags=...) at kernel/qeventloop.cpp:201 #27 0x00007f9f1484e7e6 in QDBusConnectionPrivate::sendWithReply (this=0x836710, message=..., sendMode=<value optimized out>, timeout=-1) at qdbusintegrator.cpp:1782 #28 0x00007f9f14838713 in QDBusConnection::call (this=0x8494f0, message=..., mode=8457456, timeout=4362837) at qdbusconnection.cpp:516 #29 0x00007f9f14855a7f in QDBusAbstractInterface::callWithArgumentList (this=0x824c30, mode=QDBus::BlockWithGui, method=<value optimized out>, args=...) at qdbusabstractinterface.cpp:402 #30 0x00007f9f1485967c in QDBusAbstractInterface::call (this=0x824c30, mode=QDBus::BlockWithGui, method=..., arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...) at qdbusabstractinterface.cpp:655 #31 0x0000000000420f1a in _start () *** Bug 203391 has been marked as a duplicate of this bug. *** surely this can be marked as confirmed. *** Bug 205488 has been marked as a duplicate of this bug. *** *** Bug 206586 has been marked as a duplicate of this bug. *** *** Bug 207765 has been marked as a duplicate of this bug. *** Hi, can you test if this bug is reproducible in the 0.4 version of kbluetooth? Thanks! Well this bug is duplicated of other ~+X bugs, and they're closed now as well as this one is going to be :p IF anybody is able to reproduce this bug by using kbluetooth 0.4 version just reopen the bug again. Thanks! |