bluetoothd crashed with SIGSEGV in g_slist_append()

Bug #867591 reported by Dereck Wonnacott
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Crashed on insertion of my USB BT dongle.

Also interesting note I got a prompt by ubuntu-bug to use hci-dump to record debug data, but it wasn't installed by default and I had to go looking for it. it would be nice to have the package name in the prompt.

Also the dump program quits whenever I take my dongle out and will not start unless it's already plugged in. So I can't record the debug data while i plug it in. :(

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Tue Oct 4 11:16:08 2011
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: TOSHIBA TECRA A11
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=c9cb3867-8b9d-4110-ac8c-ec11f8014e88 ro quiet splash nomodeset video=uvesafb:mode_option=1600x900-24,mtrr=3,scroll=ywrap vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f91a802c799 <g_slist_append+41>: mov %r12,(%rax)
 PC (0x7f91a802c799) ok
 source "%r12" ok
 destination "(%rax)" (0x7f91a8780ce5) in non-writable VMA region: 0x7f91a86ff000-0x7f91a87a1000 r-xp /usr/sbin/bluetoothd
SegvReason: writing VMA /usr/sbin/bluetoothd
Signal: 11
SourcePackage: bluez
StacktraceTop:
 g_slist_append () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_dbus_register_interface ()
 ?? ()
 ?? ()
 ?? ()
Title: bluetoothd crashed with SIGSEGV in g_slist_append()
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (3 days ago)
UserGroups:

dmi.bios.date: 12/03/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 2.90
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.90:bd12/03/2010:svnTOSHIBA:pnTECRAA11:pvrPTSE3U-0N806X:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A11
dmi.product.version: PTSE3U-0N806X
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
  UP RUNNING
  RX bytes:454 acl:0 sco:0 events:17 errors:0
  TX bytes:81 acl:0 sco:0 commands:17 errors:0

Revision history for this message
Dereck Wonnacott (dereck) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_slist_append (list=0x0, data=0x7f91a9c60e00) at /build/buildd/glib2.0-2.30.0/./glib/gslist.c:255
 add_interface (destroy=0, user_data=<optimized out>, properties=0x0, signals=0x0, methods=0x7f91a89a1c40, name=0x7f91a8779d70 "org.freedesktop.DBus.Introspectable", data=<optimized out>) at gdbus/object.c:516
 object_path_ref (path=0x7f91a878ab5a "/org/bluez/test", connection=0x7f91a9c5a010) at gdbus/object.c:546
 g_dbus_register_interface (connection=0x7f91a9c5a010, path=0x7f91a878ab5a "/org/bluez/test", name=0x7f91a878ab42 "org.bluez.TelephonyTest", methods=0x7f91a89a4700, signals=0x7f91a89a4880, properties=0x0, user_data=0x0, destroy=0) at gdbus/object.c:682
 telephony_init () at audio/telephony.c:408

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
Konrad Zapałowicz (kzapalowicz) wrote :

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: New → Invalid
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.