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

Bug #552166 reported by Mario Limonciello
114
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

Crashed when choosing to disable bluetooth.

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): 0x096a0bf0 ***
Date: Tue Mar 30 18:56:55 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100212)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 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): 0x096a0bf0 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:26111): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:26196): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-display-properties:26235): Gtk-WARNING **: Ignoring the separator setting
 (gnome-display-properties:26235): Gtk-WARNING **: No object called:
 (gnome-terminal:26531): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Revision history for this message
Mario Limonciello (superm1) wrote :
Matt Zimmerman (mdz)
visibility: private → public
visibility: public → private
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.