bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Bluetooth crashes every time on startup and bluetooth-applet is not loaded.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-9-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Jan 19 20:11:19 2012
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120117)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK Computer INC. 1000H
ProcCmdline: /usr/sbin/
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb773bd66: movl $0x0,0x240(%eax)
PC (0xb773bd66) ok
source "$0x0" ok
destination "0x240(%eax)" (0x00000240) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
?? ()
?? ()
?? () from /lib/i386-
g_main_
?? () from /lib/i386-
Title: bluetoothd crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1000H
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:22:43:B2:27:6D ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:473 acl:0 sco:0 events:19 errors:0
TX bytes:80 acl:0 sco:0 commands:19 errors:0
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #857702, 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.