From: Szymon Janc <szymon.janc@codecoup.pl>
To: jay@systech.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez 5.49 Segmentation Fault
Date: Thu, 22 Mar 2018 21:04:05 +0100 [thread overview]
Message-ID: <3101238.RsEhQVg2kc@ix> (raw)
In-Reply-To: <e4a2aaba-6888-6c44-b48d-e954514263b4@systech.com>
Hi Jay,
On Thursday, 22 March 2018 20:31:23 CET Jay Foster wrote:
> I am experiencing problems with the latest 5.49 version of the bluez
> bluetooth daemon. Attempting to configure the Discoverable property of
> an adapter causes the bluetoothd to segmentation fault. This works
> correctly for version 5.48 and earlier.
>
> The following command demonstrates the bug.
>
> dbus-send --system --dest=org.bluez --print-reply /org/bluez/hci0
> org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1
> string:Discoverable variant:boolean:true
I'm not able to reproduce this on 5.49 tag. Could you run bluetoothd under
valgrind and provide the output?
--
pozdrawiam
Szymon Janc
next prev parent reply other threads:[~2018-03-22 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 19:31 Bluez 5.49 Segmentation Fault Jay Foster
2018-03-22 20:04 ` Szymon Janc [this message]
2018-03-22 20:21 ` Jay Foster
2018-03-22 20:29 ` Jay Foster
2018-03-22 21:09 ` Jay Foster
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=3101238.RsEhQVg2kc@ix \
--to=szymon.janc@codecoup.pl \
--cc=jay@systech.com \
--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