From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <4239e483-1df9-8e18-fc07-d3ce755c8b16@phobeus.de> References: <4239e483-1df9-8e18-fc07-d3ce755c8b16@phobeus.de> From: Luiz Augusto von Dentz Date: Mon, 21 Aug 2017 23:55:22 +0300 Message-ID: Subject: Re: Segfault on audio pairing To: Florian Sievert Cc: "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Florian, On Mon, Aug 21, 2017 at 7:29 PM, Florian Sievert wrote: > Hi all, > > I run into an issue with bluetooth when trying to connect to an audio > speaker on my Fedora 26 system. I was able to reproduce this at least on > two other Fedora systems with different hardware and thus opened up an > issue in redhat's bugzilla: > > https://bugzilla.redhat.com/show_bug.cgi?id=1469961 > > While performing a discussion on the fedora user mailing list, some guy > confirmed the issue as well and pointed out that some similiar Arch > Linux does exist: > > https://bugs.archlinux.org/task/53442 > > I was pointed to this mailing list to raise the issue and asking for > further advisory on debugging this segfault. The issue is 100% > reproducable here on my system and seems just to occur when connecting > an audio speaker via bluetooth to the system. All other bluetooth > devices seems to be working fine. Some logs and the segfault are > attached to the redhat issue. So how may I help to narrow down this > segfault? There have been at least one fix related to some headset that are using GATT: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=5252296b725ef159992be5372f60721bd9adca48 -- Luiz Augusto von Dentz