bluetooth-applet crashes on resume after suspend: bluetooth-applet assert failure: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x08c55a68 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-bluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-bluetooth
Resuming my laptop (a dell latitude d620) after a suspend, the bluetooth-applet crashes with the following error:
*** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x08c55a68 ***
The applet was not showing either before or after the suspend, and no bluetooth devices are in use. The bluetooth indicator led on the laptop is still on, though.
1) 'lsb_release -rd'
Description: Ubuntu lucid (development branch)
Release: 10.04
2) apt-cache policy gnome-bluetooth
gnome-bluetooth:
Installed: 2.30.0-0ubuntu1
Candidate: 2.30.0-0ubuntu1
Version table:
*** 2.30.0-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-bluetooth 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x08c55a68 ***
Date: Wed Mar 31 20:57:34 2010
ExecutablePath: /usr/bin/
ProcCmdline: bluetooth-applet
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: gnome-bluetooth
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
?? () from /lib/tls/
?? () from /lib/tls/
Title: bluetooth-applet assert failure: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x08c55a68 ***
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare vboxusers
XsessionErrors:
(polkit-
(Do:2152): Wnck-CRITICAL **: wnck_set_
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.