bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Unknown event. Computer had just started and I had just logged in. No bluetooth interaction by the user had taken place, however the internal bluetooth chip was enabled and a previously paired set of bluetooth speakers was in the vicinity.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSign
Uname: Linux 3.2.0-21-
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Thu Apr 5 20:30:36 2012
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: ASUSTeK Computer INC. 1000
ProcCmdline: /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bluez
Title: bluetoothd crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1003
dmi.board.
dmi.board.name: 1000
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: 1000
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
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.