I'd suggest checking /etc/dbus-1/system.d/bluetooth.conf for the
following lines:
policy at_console=true
allow send_destination=org.bluez/
/policy
This allows users with the at_console right access to the org.bluez bus.
The at_console right should be set by consolekit for local users by
Le 02/02/2014 12:12, Christopher Schramm a écrit :
I'd suggest checking /etc/dbus-1/system.d/bluetooth.conf for the
following lines:
policy at_console=true
allow send_destination=org.bluez/
/policy
This allows users with the at_console right access to the org.bluez bus.
The at_console
Hi Julien,
do you get the same access violation when calling the Inspect method
with e. g. d-feet [1]?
[1] http://packages.debian.org/jessie/d-feet
You can try the following in d-feet:
* Highlight the org.bluez system bus
* Extend the / object path
* Extend the
Hi,
Le 01/02/2014 09:30, Christopher Schramm a écrit :
You can try the following in d-feet:
* Highlight the org.bluez system bus
Clicking on it directly triggers:
org.bluez : GDBus.Error:org.freedesktop.DBus.Error.AccessDenied:
Rejected send message, 2 matched rules; type=method_call,
Hi Julien,
first of all this is not a blueman problem, but related to bluez in general.
To get dbus access to bluez as an unprivileged user you need to either
be in the bluetooth group or have consolekit set up (or modify the rules
in /etc/dbus-1/system.d/bluetooth.conf).
consolekit is a
Hi,
Le 01/02/2014 11:45, Christopher Schramm a écrit :
first of all this is not a blueman problem, but related to bluez in general.
To get dbus access to bluez as an unprivileged user you need to either
be in the bluetooth group or have consolekit set up (or modify the rules
in
Package: blueman
Version: 1.23-git201312311147-1
I hadn't used bluetooth on that box since quite long (can't remember
exactly, sorry) -- today it fails.
The error when I launch blueman-manager:
ERROR:dbus.proxies:Introspect error on org.bluez:/:
dbus.exceptions.DBusException:
7 matches
Mail list logo