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

[Leandro]

Binary package hint: gnome-bluetooth

Bluetooth's icon in system try dont be visible.

ubuntu 10.04

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
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: *** glibc detected *** bluetooth-applet: double free or corruption (fasttop): 0x095711e8 ***
CheckboxSubmission: ac516ca40689bec40b2cf497fac25185
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Wed Mar 31 13:52:30 2010
ExecutablePath: /usr/bin/bluetooth-applet
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.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): 0x095711e8 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1478): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (rhythmbox:1659): Rhythmbox-WARNING **: Could not open device /dev/radio0
 (rhythmbox:1659): Gdk-WARNING **: /build/buildd/gtk+2.0-2.20.0/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[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.