Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43535 - [bluez] DBus denies access to org.bluez.Agent due to incorrect default config
Attached to Project:
Arch Linux
Opened by Andras Sevcsik (sevcsik) - Wednesday, 21 January 2015, 22:48 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 16 February 2015, 19:45 GMT
Opened by Andras Sevcsik (sevcsik) - Wednesday, 21 January 2015, 22:48 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 16 February 2015, 19:45 GMT
|
DetailsDescription:
When I try to pair my A2DP headset, blueman fails with error "stream setup failed". Looking at the logs, I saw this message: bluetoothd[375]: Agent /org/blueman/agent/adapter/hci0 replied with an error: org.freedesktop.DBus.Error.AccessDenied, Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=375 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="org.bluez.Agent" member="R equestPinCode" error name="(unset)" requested_reply="0" destination=":1.121" (uid=1001 pid=14860 comm="/usr/bin/python2 /usr/bin/blueman-applet ") Jan 21 23:15:14 sevcsik-desktop dbus[360]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=375 comm="/usr/lib/bluetooth/bluetoothd -n ") interface="org.bluez.Agent" member="RequestPinCode" error name="(unset)" requested_reply="0" destination=":1.121" (uid=1001 pid=14860 co mm="/usr/bin/python2 /usr/bin/blueman-applet ") I looked /etc/dbus-1/system.d/bluetooth.conf doesn't have a policy rule for "org.bluez.Agent", only "org.bluez.Agent1". Adding an allow rule to "org.bluez.Agent" solves the problem. Bluez version: 5.27-1 Steps to reproduce: Try to connect to a device with blueman using bluez5.27-1. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Monday, 16 February 2015, 19:45 GMT
Reason for closing: No response
Monday, 16 February 2015, 19:45 GMT
Reason for closing: No response
http://git.kernel.org/cgit/bluetooth/bluez.git/commit/src/bluetooth.conf?id=c5b2e6b07236827955d8fe08dcad51d31124e2a9
I guess using blueman breaks the device id here. Blueman is afaik not capable to work with bluez v5!