bluetoothd crashed with SIGSEGV in g_slist_foreach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
-
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: bluez 4.99-2ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-2-generic x86_64
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 2 08:55:52 2012
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: ASUSTeK Computer Inc. UL50Ag
ProcCmdline: /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f7a490fc030 <g_slist_
PC (0x7f7a490fc030) ok
source "0x8(%rdi)" (0x00000079) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
g_slist_foreach () from /lib/x86_
g_slist_free_full () from /lib/x86_
?? ()
?? ()
g_main_
Title: bluetoothd crashed with SIGSEGV in g_slist_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.
dmi.board.name: UL50Ag
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: UL50Ag
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:22:43:D1:73:10 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:856 acl:0 sco:0 events:36 errors:0
TX bytes:886 acl:0 sco:0 commands:36 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 #1017650, 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.