public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Sievert <caleb@phobeus.de>
To: linux-bluetooth@vger.kernel.org
Subject: Segfault on audio pairing
Date: Mon, 21 Aug 2017 18:29:39 +0200	[thread overview]
Message-ID: <4239e483-1df9-8e18-fc07-d3ce755c8b16@phobeus.de> (raw)

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?

Many thanks in advance,
Florian


             reply	other threads:[~2017-08-21 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 16:29 Florian Sievert [this message]
2017-08-21 20:55 ` Segfault on audio pairing 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
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=4239e483-1df9-8e18-fc07-d3ce755c8b16@phobeus.de \
    --to=caleb@phobeus.de \
    --cc=linux-bluetooth@vger.kernel.org \
    /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