public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Zapalowicz <konrad.zapalowicz@canonical.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Florian Sievert <caleb@phobeus.de>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	pwaago@cisco.com
Subject: Re: Segfault on audio pairing
Date: Wed, 23 Aug 2017 12:37:58 +0200	[thread overview]
Message-ID: <20170823103758.GB7309@annapurna> (raw)
In-Reply-To: <CABBYNZ+1BOM-RssKMNp23rFA4R4HQrsu-cG=rNHM_kpmJkjutw@mail.gmail.com>

On 08/23, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Wed, Aug 23, 2017 at 12:17 PM, Konrad Zapalowicz
> <konrad.zapalowicz@canonical.com> wrote:
> > On 08/21, Luiz Augusto von Dentz wrote:
> >> Hi Florian,
> >>
> >> On Mon, Aug 21, 2017 at 7:29 PM, Florian Sievert <caleb@phobeus.de> 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.

Good idea. From my side:

1) Sony MDR-1000X
2) Sony SBH52

There was also a report from Per who used a Plantronics headset however
I'm not sure what is the status with the above patch applied.

/K

> 
> -- 
> Luiz Augusto von Dentz

  reply	other threads:[~2017-08-23 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 16:29 Segfault on audio pairing Florian Sievert
2017-08-21 20:55 ` Luiz Augusto von Dentz
2017-08-23  9:17   ` Konrad Zapalowicz
2017-08-23  9:23     ` Luiz Augusto von Dentz
2017-08-23 10:37       ` Konrad Zapalowicz [this message]
2017-08-30 16:07       ` Florian Sievert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170823103758.GB7309@annapurna \
    --to=konrad.zapalowicz@canonical.com \
    --cc=caleb@phobeus.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=pwaago@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox