bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Starting up a fully updated precise beta (as of March 22, 18:00 MET), just after login
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSign
Uname: Linux 3.2.0-19-
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Mar 23 06:26:24 2012
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120311)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcCmdline: /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb7721da6: movl $0x0,0x240(%eax)
PC (0xb7721da6) 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: Upgraded to precise on 2012-03-22 (0 days ago)
UserGroups:
dmi.bios.date: 08/04/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.01
dmi.board.
dmi.board.name: 3387
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 36.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 74:DE:2B:71:F5:56 ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING PSCAN
RX bytes:1339 acl:0 sco:0 events:56 errors:0
TX bytes:735 acl:0 sco:0 commands:56 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.