bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

Bug #974575 reported by Guy Taylor
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
Uname: Linux 3.2.0-21-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Thu Apr 5 20:30:36 2012
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: ASUSTeK Computer INC. 1000
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic-pae root=UUID=8c63ff47-6b54-4313-8ac8-39c5b4ea9918 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: 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.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000
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.:bvr1003:bd06/11/2009:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Guy Taylor (thebiggerguy) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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
Revision history for this message
Ivomar (ivomarlucio) wrote :

$ lsb_release -rd
    Description: Ubuntu 14.04.2 LTS
    Release: 14.04

$ apt-cache policy bluez
    bluez:
      Instalado: 4.101-0ubuntu13.1
      Candidato: 4.101-0ubuntu13.1
      Tabela de versão:
     *** 4.101-0ubuntu13.1 0
            500 http://br.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
            100 /var/lib/dpkg/status
         4.101-0ubuntu13 0
            500 http://br.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

I solved with

sudo apt-get build-dep bluez-tools
apt-get source --compile bluez-tools

Kisses from Brazil!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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