bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Testing Precise Alpha 2 20120201.1, live session.
I get the crash just after loading the desktop.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-0ubuntu6
ProcVersionSign
Uname: Linux 3.2.0-12-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CasperVersion: 1.302
Date: Wed Feb 1 19:43:07 2012
ExecutablePath: /usr/sbin/
InterestingModules: bnep rfcomm btusb bluetooth
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201)
MachineType: ASUSTeK Computer INC. 1015PEM
ProcCmdline: /usr/sbin/
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb76d5ded: movl $0x1,0x240(%edi)
PC (0xb76d5ded) ok
source "$0x1" ok
destination "0x240(%edi)" (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/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.
dmi.board.name: 1015PE
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: 1015PEM
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 74:F0:6D:AD:0B:FD 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.