bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

Bug #856895 reported by Jim Raredon
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
New
Undecided
Unassigned

Bug Description

It looks like a duplicate of bug #739746, but this is on Oneiric updated to Beta2.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 22 19:38:20 2011
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: ASUSTeK Computer Inc. G74Sx
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=0cd12c16-5898-4b1d-9d8b-d3bad986c3f1 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fa945972bdb: movl $0x1,0x240(%rbp)
 PC (0x7fa945972bdb) ok
 source "$0x1" ok
 destination "0x240(%rbp)" (0x00000240) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G74Sx.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G74Sx
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG74Sx.201:bd04/27/2011:svnASUSTeKComputerInc.:pnG74Sx:pvr1.0:rvnASUSTeKComputerInc.:rnG74Sx:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G74Sx
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 74:2F:68:53:61:AD ACL MTU: 1022:8 SCO MTU: 121:3
  DOWN
  RX bytes:461 acl:0 sco:0 events:19 errors:0
  TX bytes:76 acl:0 sco:0 commands:18 errors:0

Revision history for this message
Jim Raredon (decoy-umd) wrote :
Revision history for this message
Jim Raredon (decoy-umd) wrote :

I forgot to mention:

This happens right after every login.

It occurs regardless if Bluetooth is ON or OFF.

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #834569, 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
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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