bluetoothd crashed with SIGSEGV in g_slist_foreach()

Bug #1017650 reported by Andrei
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Medium
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: bluez 4.99-2ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jun 25 22:24:11 2012
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: ASUSTeK Computer Inc. UL50Ag
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-1-generic root=UUID=da260481-40cb-4bac-a256-0cf4228fed94 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f305a8bced0 <g_slist_foreach+16>: mov 0x8(%rdi),%rbx
 PC (0x7f305a8bced0) ok
 source "0x8(%rdi)" (0x000000e9) 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_64-linux-gnu/libglib-2.0.so.0
 g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
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.asset.tag: ATN12345678901234567
dmi.board.name: UL50Ag
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.:bvr206:bd08/13/2009:svnASUSTeKComputerInc.:pnUL50Ag:pvr1.0:rvnASUSTeKComputerInc.:rnUL50Ag:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL50Ag
dmi.product.version: 1.0
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:2651 acl:18 sco:0 events:214 errors:0
  TX bytes:267619 acl:324 sco:0 commands:43 errors:0

Revision history for this message
Andrei (andrei-doom) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_slist_foreach (list=0xe1, list@entry=0x7f305bcc9af0, func=0x7f305a8a74f0 <g_free>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.33.2/./glib/gslist.c:839
 g_slist_free_full (list=0x7f305bcc9af0, free_func=<optimized out>) at /build/buildd/glib2.0-2.33.2/./glib/gslist.c:177
 client_free (data=0x7f305bcc5fb0) at audio/unix.c:113
 client_cb (cond=<optimized out>, data=0x7f305bcc5fb0, chan=<optimized out>) at audio/unix.c:1767
 g_main_dispatch (context=0x7f305bcac070) at /build/buildd/glib2.0-2.33.2/./glib/gmain.c:2539

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in bluez (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Have you seen this particular crash again since? Any idea what actions may have triggered it?

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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