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

[Øystein Tøsse Larsen]

Binary package hint: gnome-bluetooth

Logged back into gnome after suspend (through lock screen), and the applet had crashed. Have not used the bluetooth with or without the applet yet, don't know what may have caused it.

apt-cache policy gnome-bluetooth:
2.30.0-0ubuntu1

lsb_release -rd:
Description: Ubuntu lucid (development branch)
Release: 10.04

Will be back with more info if/when I get the time.
(Running clean install of Lucid Beta1 with no added packages, freshly updated today, on an Asus Eee PC 1101HA)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-bluetooth 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x091c4ef8 ***
Date: Wed Mar 31 19:30:45 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-bluetooth
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: bluetooth-applet assert failure: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x091c4ef8 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1230): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

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.