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 dependency of policykit-1, which in terms is recommended by the blueman package and thus the setup should work out of the box if recommendations are followed. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org