Ubuntu
bluez package

bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()

Bug #1705077 reported by Cristian Aravena Romero on 2017-07-18

This bug report is a duplicate of: Bug #1493498: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch. Edit Remove

This bug affects 1 person

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

Bug Description

Hello,

Config Bluetoothd.

Regards,
--
Cristian

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: bluez 5.45-0ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 18 12:02:06 2017
ExecutablePath: /usr/lib/bluetooth/bluetoothd
InstallationDate: Installed on 2017-07-05 (12 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcCmdline: /usr/lib/bluetooth/bluetoothd
ProcEnviron:
LANG=es_CL.UTF-8
LANGUAGE=es_CL:es
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x55802f9df42e: mov 0x8(%rsi),%rbp
PC (0x55802f9df42e) ok
source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading 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: Upgraded to artful on 2017-07-05 (12 days ago)
UserGroups:

dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
hciconfig:
hci0: Type: Primary Bus: USB
  BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING PSCAN
  RX bytes:3574167 acl:39 sco:0 events:510356 errors:0
  TX bytes:254435767 acl:1033259 sco:0 commands:97 errors:0

Tags:

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2017-07-18:

CurrentDmesg.txt Edit (67.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (646 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (39.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (659 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (917 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (8.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Registers.txt Edit (740 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (161.1 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (163 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (246 bytes, text/plain; charset="utf-8")
syslog.txt Edit (4.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-07-18:

StacktraceTop:
avdtp_sep_set_state ()
session_cb ()
g_main_context_dispatch () from /tmp/apport_sandbox_Md0h97/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_iterate.isra () from /tmp/apport_sandbox_Md0h97/lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /tmp/apport_sandbox_Md0h97/lib/x86_64-linux-gnu/libglib-2.0.so.0

Revision history for this message

Apport retracing service (apport) wrote on 2017-07-18: Stacktrace.txt

Stacktrace.txt Edit (679 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-07-18: StacktraceSource.txt

StacktraceSource.txt Edit (488 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-07-18: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (725 bytes, text/plain)

Changed in bluez (Ubuntu):
importance:	Undecided → Medium
summary:	- bluetoothd crashed with SIGSEGV in g_main_context_dispatch() + bluetoothd crashed with SIGSEGV in avdtp_sep_set_state()
tags:	removed: need-amd64-retrace

Cristian Aravena Romero (caravena) on 2017-07-18

information type:

Private → Public

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2017-07-19:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1689452, so it 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. Feel free to continue to report any other bugs you may find.