Summary: | after hardware switch bluetooth off, kbluetooth4 crashed with SIGSEGV | ||
---|---|---|---|
Product: | [Unmaintained] kde-bluetooth | Reporter: | josef.jedlicka |
Component: | kbluetoothd | Assignee: | Unknown <null> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | andresbajotierra, cfeck, david, georg.martius, giuseppe.calaprice, k6lw, pcuninka |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
josef.jedlicka
2009-02-18 11:14:34 UTC
As you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You may need to install the "libqt4-dbg" package. Thanks :) Most likely bug 182368 Bug 182368 have references to KDE-bluetooth function at #2 and #3, while this crash doesn't have them (it's only about QtDbus) ---- Bug 182368 backtrace: Thread 1 (process 6078): #0 0xb754cc5d in QDBusAbstractInterface::callWithArgumentList () from /usr/lib/libQtDBus.so.4 #1 0xb754ec5d in QDBusAbstractInterface::call () from /usr/lib/libQtDBus.so.4 #2 0x08065fc3 in ObexServer::stop (this=0x87c6a48) at /build/buildd/kdebluetooth-0.3/src/obexserver/obexserver.cpp:100 __PRETTY_FUNCTION__ = "void ObexServer::stop()" #3 0x080514ed in KBlueTray::qt_metacall (this=0xbffad964, _c=QMetaObject::InvokeMetaMethod, _id=28, _a=0xbffaca5c) at /build/buildd/kdebluetooth-0.3/obj-i486-linux-gnu/src/moc_trayicon.cpp:159 I have same problem. I also suffer a similar crash. When resuming from "suspend to ram" in Kubuntu 9.04 RC, KBluetooth4 consistently produces the following error: """ A Fatal Error Occurred The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV). Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc. """ There is a "details" expansion, which unfortunately says only: """ This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. """ The error can be reproduced by first suspending to ram and then resuming, it then produces the crash report. The KBluetooth4 applet, version 0.3 KDE 4.2.2, is running when this happens, and continues to run even after the SIGSEGV report. I don't know what other relevant information to post for the developers. If a developer leaves a comment as to what else is needed I will happily post the information. Ignore SIGSEGV on suspend/resume comment, I posted it to the wrong bug number. I have the same problem. KBluetooth4 crashes when I switch off it. "The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV)." I have a toshiba bluetooth module in my Dell Latitude ATG 620 which is turned off both in the BIOS and with the physical switch on the laptop. I keep getting numerous KBluetooth4 caused a 11 SIGSERV. Sorry I don't know what else to supply. The "details" claim there is no useful information in the backtrace. OS is Kubuntu 9.04. A recent upgrade from Ibex. Didn't have any pop-ups with Ibex. System was not going into or out of hibernation as I don't use that feature. Laptop is powered from AC. The "crash" doesn't seem to bother the rest of the system other than making me hit the ok button. ;> I can confirm this bug on a Thinkpad T61p (lsusb says: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller) with Ubuntu 9.04 and KDE 4.2.2 and KBluetooth4 Version 0.3. I started with gdb and run -nofork and then switched off the hardware switch. (also happens after resume from suspend). Here the output and the trace: [Thread debugging using libthread_db enabled] [New Thread 0xb5e44920 (LWP 1202)] kbluetooth4(1202) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ" kbluetooth4(1202) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/3118/hci0") kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/3118/hci0" kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/3118/hci0" kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/3118/hci0" kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created kbluetooth4(1202) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface kbluetooth4(1202) KBlueTray::onlineMode: online Mode kbluetooth4(1202) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/3118/hci0") kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/3118/hci0" kbluetooth4(1202) KBlueTray::onlineMode: adapter size 1 kbluetooth4(1202) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/3118/hci0" kbluetooth4(1202) KBlueTray::onlineMode: Adapter found "chugul-0" kbluetooth4(1202) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/3118/hci0" AGENT registered ! kbluetooth4(1202) ObexServer::ObexServer: "00:00:00:00:00:00" kbluetooth4(1202) ObexServer::serverCreated: obex server created kbluetooth4(1202) ObexServer::serverCreated: session interface created for: "/org/openobex/server12" kbluetooth4(1202) ObexServer::slotStarted: server started kbluetooth4(1202) KBlueTray::slotServerStarted: obex server started kbluetooth4(1202) BluezBluetoothManager::slotDeviceRemoved: interfaceRemoved "/org/bluez/3118/hci0" kbluetooth4(1202) Solid::Control::BluetoothManagerPrivate::_k_interfaceDestroyed: Interface detroyed kbluetooth4(1202) BluezBluetoothManager::removeInterface: Removing Interface "/org/bluez/3118/hci0" kbluetooth4(1202) KBlueTray::adapterRemoved: adapterRemoved: "/org/bluez/3118/hci0" kbluetooth4(1202) Solid::Control::BluetoothManager::buildDeviceList: UBI List () kbluetooth4(1202) KBlueTray::offlineMode: offline Mode kbluetooth4(1202) KBlueTray::offlineMode: Unregistering Agent kbluetooth4(1202) ObexServer::stop: obex server stopped Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb5e44920 (LWP 1202)] 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0xb7395c43 in QDBusConnectionPrivate::activateCall (this=0x82e1118, object=0x83315a8, flags=273, msg=@0x836a5b8) at qdbusintegrator.cpp:753 #2 0xb7396501 in QDBusConnectionPrivate::activateObject (this=0x82e1118, node=@0x836a5a4, msg=@0x836a5b8, pathStartPos=18) at qdbusintegrator.cpp:1375 #3 0xb73969fa in QDBusActivateObjectEvent::placeMetaCall (this=0x836a578) at qdbusintegrator.cpp:1469 #4 0xb728c3a0 in QObject::event (this=0xbfa700a0, e=0x836a578) at kernel/qobject.cpp:1118 #5 0xb727b3db in QCoreApplication::event (this=0xbfa700a0, e=0x836a578) at kernel/qcoreapplication.cpp:1426 #6 0xb6887379 in QApplication::event (this=0xbfa700a0, e=0x836a578) at kernel/qapplication.cpp:2334 #7 0xb6883e9c in QApplicationPrivate::notify_helper (this=0x8230f78, receiver=0xbfa700a0, e=0x836a578) at kernel/qapplication.cpp:4084 #8 0xb688c19e in QApplication::notify (this=0xbfa700a0, receiver=0xbfa700a0, e=0x836a578) at kernel/qapplication.cpp:3631 #9 0xb7aa294d in KApplication::notify () from /usr/lib/libkdeui.so.5 #10 0xb727ba3b in QCoreApplication::notifyInternal (this=0xbfa700a0, receiver=0xbfa700a0, event=0x836a578) at kernel/qcoreapplication.cpp:602 #11 0xb727c695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x820db38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #12 0xb727c88d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132 #13 0xb72a77ef in postEventSourceDispatch (s=0x8233110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #14 0xb61aeb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0xb61b20eb in ?? () from /usr/lib/libglib-2.0.so.0 #16 0xb61b2268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #17 0xb72a7438 in QEventDispatcherGlib::processEvents (this=0x8223428, flags={i = -1079578648}) at kernel/qeventdispatcher_glib.cpp:323 #18 0xb6925365 in QGuiEventDispatcherGlib::processEvents (this=0x8223428, flags={i = -1079578600}) at kernel/qguieventdispatcher_glib.cpp:202 #19 0xb727a06a in QEventLoop::processEvents (this=0xbfa6f118, flags={i = -1079578536}) at kernel/qeventloop.cpp:149 #20 0xb727a4aa in QEventLoop::exec (this=0xbfa6f118, flags={i = -1079578316}) at kernel/qeventloop.cpp:200 #21 0xb739999c in QDBusConnectionPrivate::sendWithReply (this=0x834dfe0, message=@0xbfa6f288, sendMode=<value optimized out>, timeout=-1) at qdbusintegrator.cpp:1787 #22 0xb7383551 in QDBusConnection::call (this=0x834492c, message=@0xbfa6f288, mode=QDBus::BlockWithGui, timeout=-1) at qdbusconnection.cpp:516 #23 0xb73a1f3b in QDBusAbstractInterface::callWithArgumentList (this=0x8344d50, mode=QDBus::BlockWithGui, method=@0xbfa6f434, args=@0xbfa6f368) at qdbusabstractinterface.cpp:402 #24 0xb73a5e8d in QDBusAbstractInterface::call (this=0x8344d50, mode=QDBus::BlockWithGui, method=@0xbfa6f434, arg1=@0xbfa6f41c, arg2=@0xbfa6f410, arg3=@0xbfa6f404, arg4=@0xbfa6f3f8, arg5=@0xbfa6f3ec, arg6=@0xbfa6f3e0,arg7=@0xbfa6f3d4, arg8=@0xbfa6f3c8) at qdbusabstractinterface.cpp:655 #25 0x08066ce3 in _start () Regards! Georg (In reply to comment #0) > Version: KDE: 4.1.4, KBluetooth4 - The KDE4 Bluetooth Framework 0.3 > (using KDE 4.1.4) > Compiler: ubuntu packages default > OS: Linux > Installed from: Ubuntu Packages > > General description: > If i turn off wireless networks (bluetooth, wifi) with hardware switch on my > laptop (HP Pavillion dv6000), kdebluetooth4 immidiately crashed with SIGSEGV > status. > > How to reproduce: > turn off wireless networks with hardware switch / button on hp pavillion laptop > > Expected behaviour: > dont crash :) or something like turn to offline mode > > Backtrace: > (no debugging symbols found) > (no debugging symbols found) > ... etc ... > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread 0xb61e76c0 (LWP 26731)] > (no debugging symbols found) > (no debugging symbols found) > ... etc ... > (no debugging symbols found) > 0xb806b430 in __kernel_vsyscall () > [Current thread is 0 (process 26731)] > > Thread 1 (Thread 0xb61e76c0 (LWP 26731)): > #0 0xb806b430 in __kernel_vsyscall () > #1 0xb6aa8f10 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 > #2 0xb6aa8d4e in sleep () from /lib/tls/i686/cmov/libc.so.6 > #3 0xb7c8c612 in ?? () from /usr/lib/libkdeui.so.5 > #4 0xb7c8d014 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 > #5 <signal handler called> > #6 0x65440a65 in ?? () > #7 0xb6cb9156 in ?? () from /usr/lib/libQtDBus.so.4 > #8 0xb6cb99b1 in ?? () from /usr/lib/libQtDBus.so.4 > #9 0xb6cb9eaa in ?? () from /usr/lib/libQtDBus.so.4 > #10 0xb775e771 in QObject::event () from /usr/lib/libQtCore.so.4 > #11 0xb774e7cb in QCoreApplication::event () from /usr/lib/libQtCore.so.4 > #12 0xb6e45206 in QApplication::event () from /usr/lib/libQtGui.so.4 > #13 0xb6e3f8ec in QApplicationPrivate::notify_helper () from > /usr/lib/libQtGui.so.4 > #14 0xb6e4772e in QApplication::notify () from /usr/lib/libQtGui.so.4 > #15 0xb7c1ed1d in KApplication::notify () from /usr/lib/libkdeui.so.5 > #16 0xb774ee61 in QCoreApplication::notifyInternal () from > /usr/lib/libQtCore.so.4 > #17 0xb774fae5 in QCoreApplicationPrivate::sendPostedEvents () from > /usr/lib/libQtCore.so.4 > #18 0xb774fcdd in QCoreApplication::sendPostedEvents () from > /usr/lib/libQtCore.so.4 > #19 0xb777982f in ?? () from /usr/lib/libQtCore.so.4 > #20 0xb65856f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 > #21 0xb6588da3 in ?? () from /usr/lib/libglib-2.0.so.0 > #22 0xb6588f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 > #23 0xb7779478 in QEventDispatcherGlib::processEvents () from > /usr/lib/libQtCore.so.4 > #24 0xb6ed9ea5 in ?? () from /usr/lib/libQtGui.so.4 > #25 0xb774d52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 > #26 0xb774d6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 > #27 0xb6cbc52b in ?? () from /usr/lib/libQtDBus.so.4 > #28 0xb6ca6a31 in QDBusConnection::call () from /usr/lib/libQtDBus.so.4 > #29 0xb6cc5dab in QDBusAbstractInterface::callWithArgumentList () from > /usr/lib/libQtDBus.so.4 > #30 0xb6cc7c5d in QDBusAbstractInterface::call () from /usr/lib/libQtDBus.so.4 > #31 0x08065f63 in _start () > #0 0xb806b430 in __kernel_vsyscall () I have problem with my bluetooth mouse : I can't use it..... Bluetooth support has been replaced by "BlueDevil" and the old code is no longer maintained. If you still have an issue with Bluetooth support in a recent KDE version, such as KDE 4.9.5 or 4.10, please report a new bug. Also, if this is a feature request that has not yet been implemented in BlueDevil, please add a comment. |