From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: Segfault on audio pairing To: Luiz Augusto von Dentz , Konrad Zapalowicz Cc: "linux-bluetooth@vger.kernel.org" References: <4239e483-1df9-8e18-fc07-d3ce755c8b16@phobeus.de> <20170823091739.GA7309@annapurna> From: Florian Sievert Message-ID: <6a441a10-6c11-dcd8-bde2-2f7b18840fdb@phobeus.de> Date: Wed, 30 Aug 2017 18:07:45 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi, the affected devices here are: 1) Bose Soundlink Mini 2) Anker SoundCore > Hi, > > On Wed, Aug 23, 2017 at 12:17 PM, Konrad Zapalowicz > wrote: >> On 08/21, Luiz Augusto von Dentz wrote: >>> 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 >> Florian, >> >> I can add that it fixes a crash that I have been observing with Sony >> MDR-1000X and possibly also with Sony SBH52. > It might be a good idea to compile a list of affected headsets so we > can probably add to the changelog when releasing. >