Hi Rafal, On Thu, May 31, 2018 at 1:26 AM, Rafał Bilski <rafalbilski@xxxxxxxxxx> wrote: > Default dbus configuration doesn't allow calling methods on system bus. Only > sending signals is allowed. > If "mpris-proxy" isn't running "/usr/lib/gsd-media-keys" translates > keystrokes from "profiles/audio/avctp.c:handle_panel_passthrough()" > to dbus method calls on session bus. This is allowed on dbus by default. > If "mpris-proxy" is running "bluetoothd" executes dbus' method calls on > system bus. These apparently are rejected by default. > > diff --git a/src/bluetooth.conf b/src/bluetooth.conf > index 0c0b221bb..1cafab631 100644 > --- a/src/bluetooth.conf > +++ b/src/bluetooth.conf > @@ -8,6 +8,7 @@ > <!-- ../system.conf have denied everything, so we just punch some holes > --> > <policy user="root"> > + <allow send_type="method_call"/> > <allow own="org.bluez"/> > <allow send_destination="org.bluez"/> > <allow send_interface="org.bluez.Agent1"/> > I think the correct fix would be to add the interface (org.mpris.MediaPlayer2.Player) we are using to communicate with the player. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
