Ubuntu
bluez package

bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

Bug #977125 reported by Shock on 2012-04-09

This bug report is a duplicate of: Bug #857702: bluetoothd crashed with SIGSEGV in g_main_context_dispatch(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	New	Undecided	Unassigned

Bug Description

I don't know what triggered the crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Mon Apr 9 13:52:15 2012
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK Computer INC. 901
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bluez
Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-02-27 (41 days ago)
UserGroups:

dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1703
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1703:bd10/14/2008:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Tags:

Revision history for this message

Shock (mmiron) wrote on 2012-04-09:

BootDmesg.txt Edit (56.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (26.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (517 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.3 KiB, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (190 bytes, text/plain; charset="utf-8")
StacktraceTop.txt Edit (176 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (108.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (247.4 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (158 bytes, text/plain; charset="utf-8")
hciconfig.txt Edit (203 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (242 bytes, text/plain; charset="utf-8")
syslog.txt Edit (11.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-09: This bug is a duplicate

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.

visibility:	private → public
visibility:	private → public
tags:	removed: need-i386-retrace

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #857702 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntubluez package