bluetoothd assert failure: *** glibc detected *** /usr/sbin/bluetoothd: free(): invalid pointer: 0x00007f85326853e8 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bluez
crash at boot.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bluez 4.91-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/sbin/
Date: Wed Apr 20 19:05:15 2011
ExecutablePath: /usr/sbin/
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Dell Inc. MXC062
ProcCmdline: /usr/sbin/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: bluez
StacktraceTop:
raise (sig=6) at ../nptl/
abort () at abort.c:92
__libc_message (do_abort=2, fmt=0x7f853244b400 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (av=<value optimized out>, p=0x7f85326853d8) at malloc.c:6283
_int_free (av=<value optimized out>, p=0x7f85326853d8) at malloc.c:4795
Title: bluetoothd assert failure: *** glibc detected *** /usr/sbin/
UpgradeStatus: Upgraded to natty on 2011-04-01 (26 days ago)
UserGroups:
dmi.bios.date: 07/10/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.
dmi.board.vendor: Dell Inc.
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: MXC062
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:16:CF:D8:D1:A4 ACL MTU: 1017:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:663 acl:0 sco:0 events:22 errors:0
TX bytes:346 acl:0 sco:0 commands:22 errors:0
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 #644524, 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.