bluetooth-applet crashed when laptop's connectivity switch was turned off: bluetooth-applet assert failure: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x081443c0 ***

Hello,

is someone able to reproduce to reproduce the problem under valgrind and to provide a valgrind log?
(please refer to https://wiki.ubuntu.com/Valgrind for providing it)

Thanks a lot.

Crashed on boot up from hibernation

No Valgrind logs, but it is now easer to reproduce. Simply click on the BT icon and select "Turn off Bluetooth". The icon then greys for a second and then crashes.

This is after updating Lucid on Mar 31 2010.

I'm getting this error too (bluetooth-applet crashing when I disable the BT adapter) on my Toshiba Portege A600. It brings up a window explaining that apport can't collect data about assertion crashes, but if someone explains the steps to get some useful information I will do so as it's 100% reproducible at this moment in time.

Toshiba Portege A600, running up to date Lucid as of today.

OK, I just tried following the Valgrind instructions I missed above. However, this time, bluetooth-applet started OK, and I was able to turn Bluetooth on and off via the applet with no crashes.

I've attached the log anyway in case it's useful, but please note that this is actually a successful run, not a crash run. I plan to simulate a crash run by changing the startup programs entry to include valgrind temporarily as I've found this 100% reproducible from a cold start.

I can't get it to crash with Valgrind, I've tried:

reboot -> disable BT -> applet crash -> start with Valgrind from CLI -> disable/enable BT

and also

reboot without applet enabled -> start with Valgrind from CLI -> disable/enable BT

both of these scenarios worked OK. However as soon as I put the bluetooth-applet back into my startup programs (running as normal without Valgrind) and reboot, disabling BT crashes the applet straight away again.

I got this today

bluetooth-applet assert failure: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x09b67d30 ***

I just simply removed my bt-usb-dongle from the back of my laptop.

It had been connected to my iPhone earlier today, but i belive that the connection was disconnected at this point.

This bug was fixed in the package gnome-bluetooth - 2.30.0-0ubuntu2

---------------
gnome-bluetooth (2.30.0-0ubuntu2) lucid; urgency=low

  * debian/patches/03-fix-killswitch-memleak.patch:
    - the change is in the new version so drop this one, it still applies but
      create double g_free which leads to crashes (lp: #552140)
 -- Sebastien Bacher <email address hidden> Thu, 01 Apr 2010 11:15:51 +0200

Same here, but I did not touch the switch ...

Oops sorry, I've to upgrade to new Version - still use "gnome-bluetooth 2.30.0-0ubuntu1"

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #551744, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.