Bug 274696

*** Bug 275048 has been marked as a duplicate of this bug. ***

Created attachment 62713 [details]
New crash information added by DrKonqi

bluedevil-wizard (0.1) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

paired with a BTM-222 bluetooth module.
right after pairing finished, crash happens.
Pairing finished successfully.
Crash happens all the time I pair with this device. Does not have a different bluetooth device to test with.

-- Backtrace (Reduced):
#8  0x00007f749296f095 in _dbus_abort () at dbus-sysdeps.c:94
#9  0x00007f7492966015 in _dbus_warn_check_failed (format=0x7f74929752f0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:289
#10 0x00007f749295a184 in dbus_message_get_sender (message=<value optimized out>) at dbus-message.c:3320
#11 0x00007f7496e3f38a in q_dbus_message_get_sender (message=<value optimized out>, error=0x7fff9e0a9cd0) at qdbus_symbols_p.h:213
#12 QDBusMessagePrivate::toDBusMessage (message=<value optimized out>, error=0x7fff9e0a9cd0) at qdbusmessage.cpp:152

uff I don't know what to do with this backtrace... it shows nothing at bluedevil level.

Can you try to reproduce this bug with a recent distribution? maybe something with kernel 3.0 ? with a livecd it should be good enough.

Thanks!

Created attachment 64739 [details]
New crash information added by DrKonqi

bluedevil-wizard (0.1) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

- What I was doing when the application crashed:

Much earlier, I had been using various bluetooth tools (hcidump, hcitool, et. al.) to try and figure out what the bluetooth system was doing.  After a break, I discovered the bluetooth icon in the system tray.

I had just been attempting to pair a Mindstorms NXT to my openSuSE 11.4 system, using the Bluetooth applet in the tray at the bottom right of the desktop.  After several failed attempts, the pairing completion was "Successful", and then a crash report popped up.

The Bluetooth applet continued to operate successfully (as it appeared to me), despite the popup.

According to the stack trace, it looks like there is some __ dbus __ notification/registration problem causing the crash.  Actually, it looks like a programming error formatting an error/warning message.

Reading between the lines, it looks like the Bluetooth app sent a msg to/over dbus which was misformatted, crashing dbus.  I'd bet this msg only occurs upon successful bluetooth pairing.

Since dbus is implicated, here is some of the nearby /var/log/messages:

Oct 20 10:59:50 c4 bluetoothd[2897]: Discovery session 0xb788e950 with :1.77 activated
Oct 20 11:00:01 c4 bluetoothd[2897]: Stopping discovery
Oct 20 11:00:29 c4 rtkit-daemon[4059]: Supervising 0 threads of 0 processes of 0 users.
Oct 20 11:00:30 c4 avahi-daemon[2663]: Failed to open /usr/share/dbus-1/interfaces/org.freedesktop.Avahi.Server.xml: Permission denied
Oct 20 11:00:30 c4 avahi-daemon[2663]: Failed to load introspection data.
Oct 20 11:00:30 c4 avahi-daemon[2663]: Failed to open /usr/share/dbus-1/interfaces/org.freedesktop.Avahi.ServiceBrowser.xml: Permission denied
Oct 20 11:00:30 c4 avahi-daemon[2663]: Failed to load introspection data.
Oct 20 11:01:49 c4 rtkit-daemon[4059]: Supervising 0 threads of 0 processes of 0 users.
Oct 20 11:01:49 c4 avahi-daemon[2663]: Failed to open /usr/share/dbus-1/interfaces/org.freedesktop.Avahi.Server.xml: Permission denied
Oct 20 11:01:49 c4 avahi-daemon[2663]: Failed to load introspection data.
Oct 20 11:01:49 c4 avahi-daemon[2663]: Failed to open /usr/share/dbus-1/interfaces/org.freedesktop.Avahi.ServiceBrowser.xml: Permission denied
Oct 20 11:01:49 c4 avahi-daemon[2663]: Failed to load introspection data.
Oct 20 11:03:20 c4 bluetoothd[2897]: Invalid PIN length (0) from agent
Oct 20 11:03:55 c4 bluetoothd[2897]: Invalid PIN length (0) from agent
Oct 20 11:06:12 c4 bluetoothd[2897]: Discovery session 0xb789f248 with :1.78 activated
Oct 20 11:06:27 c4 bluetoothd[2897]: Invalid PIN length (0) from agent
Oct 20 11:06:41 c4 bluetoothd[2897]: Stopping discovery

(at this point, I started this bug report.)

-- Backtrace (Reduced):
#10 0xb5bf2005 in _dbus_abort () at dbus-sysdeps.c:94
#11 0xb5be7911 in _dbus_warn_check_failed (format=0xb5bf7ec0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:289
#12 0xb5bda146 in dbus_message_get_sender (message=0x0) at dbus-message.c:3320
#13 0xb709be86 in q_dbus_message_get_sender (message=..., error=0xbfc708a0) at qdbus_symbols_p.h:213
#14 QDBusMessagePrivate::toDBusMessage (message=..., error=0xbfc708a0) at qdbusmessage.cpp:152

Created attachment 64848 [details]
New crash information added by DrKonqi

bluedevil-wizard (0.1) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

- What I was doing when the application crashed:

I initiated pairing.  After pairing was completed (according to screen) crash occurred.  I was able to get a much deeper trace by doing this operation as root.

-- Backtrace (Reduced):
#10 0xb5ad4005 in _dbus_abort () at dbus-sysdeps.c:94
#11 0xb5ac9911 in _dbus_warn_check_failed (format=0xb5ad9ec0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:289
#12 0xb5abc146 in dbus_message_get_sender (message=0x0) at dbus-message.c:3320
#13 0xb6f7de86 in q_dbus_message_get_sender (message=..., error=0xbfb4e600) at qdbus_symbols_p.h:213
#14 QDBusMessagePrivate::toDBusMessage (message=..., error=0xbfb4e600) at qdbusmessage.cpp:152

Can anybody still reproduce this bug with latest version?

Nobody replied so I'm going to guess that this is fixed.

If you can still reproduce the bug please, re-open i t!