From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Rafael Avila de Espindola <rafael@espindo.la>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: git bluetoothd getting disconnected from dbus
Date: Mon, 11 May 2020 13:08:27 -0700 [thread overview]
Message-ID: <CABBYNZJj-cwY6dOf37GH4Yxi_P41CwRSN7sZ3b-vugACa_i8vw@mail.gmail.com> (raw)
In-Reply-To: <875zd33bsf.fsf@espindo.la>
Hi Rafael,
On Sun, May 10, 2020 at 11:11 AM Rafael Avila de Espindola
<rafael@espindo.la> wrote:
>
> I compiled a new version of bluez to try help test an
> issue
> (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/880), but
> now bluetoothd is being disconnected from dbus.
>
> This is on a fedora 32, so the dbus is actually
> https://github.com/bus1/dbus-broker.
>
> The bluz revision is 3146b7a0785758be2d4e894d44e99d29c0db983e.
>
> The behavior is that I can start bluetoothd with
>
> $ sudo ./src/bluetoothd -n --debug='*' -f ./src/main.conf
>
> and pulse audio with
>
> $ ./src/pulseaudio -p $(pwd)/src/ --daemonize=no -v -v -v
>
> Everything looks fine until I turn on a bluetooth device that was
> already paired and trusted. As far as I can tell, it connects correctly,
> but then the bluetoothd log shows
>
> May 10 10:18:41 raspberrypi.local bluetoothd[3127]: profiles/audio/transport.c:transport_update_playing() /org/bluez/hci0/dev_EC_81_93_4A_C7_7E/fd0 State=TRANSPORT_STATE_ACTIVE Playing=1
> May 10 10:18:41 raspberrypi.local bluetoothd[3127]: Disconnected from D-Bus. Exiting.
I suspect this is due to fd hand over, I usually have to
SELINUX=disabled to disable SELinux policies when running bluetoothd
from source because it seems there is some policy the prevents fd
passing over D-Bus, we should probably add this to HACKING if we
confirm that this is in fact SELinux policy.
> I can't quite figure out what is going on, but dbus-monitor around the
> time shows:
>
> signal time=1589131121.073746 sender=org.freedesktop.DBus -> destination=:1.65 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
> string "org.bluez"
> signal time=1589131121.073832 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
> string "org.bluez"
> string ":1.65"
> string ""
>
> Which is suspicious. I have attached the full logs starting just before
> the bluetooth speaker is turned on.
>
> What I have checked so far
>
> * I removed the system bluez and pulse audio
> * I checked that ./src/bluetooth.conf has been copied to /etc/dbus-1/system.d/bluetooth.conf
>
> Any suggestions as to where I should look next?
>
> Thanks,
> Rafael
>
>
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2020-05-11 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 18:06 git bluetoothd getting disconnected from dbus Rafael Avila de Espindola
2020-05-11 20:08 ` Luiz Augusto von Dentz [this message]
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=CABBYNZJj-cwY6dOf37GH4Yxi_P41CwRSN7sZ3b-vugACa_i8vw@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rafael@espindo.la \
/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;
as well as URLs for NNTP newsgroup(s).