Summary: | kded crashes in latest trunk | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | Robert Marmorstein <robert> |
Component: | bluetooth-daemon | Assignee: | Rafael Fernández López <ereslibre> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | afiestas, alexanders83, lamarque, mail |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Fix crash when no bluetooth adapter is activated. |
Description
Robert Marmorstein
2010-08-03 21:40:51 UTC
I also get a similar crash from bluedevil when I installed it just during that session (no kded using bluedevil): Application: Bluetooth (bluedevil-monolithic), signal: Aborted Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #5 0x00007f0a661ef1b5 in raise () from /lib/libc.so.6 #6 0x00007f0a661f05e0 in abort () from /lib/libc.so.6 #7 0x00007f0a675f8b64 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007f0a675f8cfe in qt_message(QtMsgType, char const*, __va_list_tag*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f0a675f8eb5 in qFatal(char const*, ...) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007f0a67a7d764 in QDBusArgumentPrivate::checkRead(QDBusArgumentPrivate*) () from /usr/lib64/qt4/libQtDBus.so.4 #11 0x00007f0a67a7dc8f in QDBusArgumentPrivate::checkReadAndDetach(QDBusArgumentPrivate*&) () from /usr/lib64/qt4/libQtDBus.so.4 #12 0x00007f0a67a7ddc9 in QDBusArgument::beginArray() const () from /usr/lib64/qt4/libQtDBus.so.4 #13 0x00007f0a68147ac0 in BlueDevil::Manager::Manager(QObject*) () from /usr/lib64/libbluedevil.so.1 #14 0x00007f0a6814847a in BlueDevil::Manager::self() () from /usr/lib64/libbluedevil.so.1 #15 0x0000000000407319 in Monolithic::generateDeviceEntries() () #16 0x0000000000408b43 in Monolithic::onlineMode() () #17 0x0000000000408d22 in Monolithic::Monolithic(QObject*) () #18 0x0000000000404ed0 in main () I observed this is caused by the fact, there is no org.bluez entry in dbus. This is caused by having no bluetooth adapter attached. Once I attach it (USB device), I get a org.bluez entry in dbus and I can start bluedevil. The same can be adopted to kded. no adapter attached -> crash. adapter attached -> kded starts without problems Bluedevil crashes kded4 at login here if my bluetooth controller is switched off. Created attachment 51130 [details]
Fix crash when no bluetooth adapter is activated.
This patch fix the crash. I think bluetooth authors must change their code to not rely on DBus calls. The reply is not always a valid reference and there are other places in (lib)bluedevil code where you use the reference without checking if it is valid.
*** Bug 247845 has been marked as a duplicate of this bug. *** (In reply to comment #3) > Created an attachment (id=51130) [details] > Fix crash when no bluetooth adapter is activated. > > This patch fix the crash. I think bluetooth authors must change their code to > not rely on DBus calls. The reply is not always a valid reference and there are > other places in (lib)bluedevil code where you use the reference without > checking if it is valid. Ereslibre will take a look at the patch ASAP, thank you! Hi, the Lamarque patch has been applied, should I close the bug? Thanks! Hi there Can anybody test this bug using libbluedevil 1.8? this should be fixed thanks to Lamarque patch. Thanks! Start to move bluedevil bugs into solid product as Albert and Kevin tell me. This bug seems to be fixed thanks to lamarque patch, so I'm going to close it. If you can reproduce it, feel free to re-open it. |