I can now confirm that this is due to an issue between obex-data-server and BlueZ 5. It is basically https://bugs.debian.org/774796 and not really a blueman issue.
The problem is that obex-data-server tries to use the /var/run/sdp socket, which in BlueZ 5 is a) disabled by default and b) limited to owner and group access. The solution is to run bluetoothd with the --compat option to enable the socket, run obex-data-server as root to be able to access the socket, and allow unprivileged access to the org.openobex bus to enable users to access obex-data-server nevertheless. fin4478 has some detailed instructions on how to modify the configuration files to achieve this, but I do not want to copy his content as I do not know if he wants it to be published. I'm sure he will provide it himself here. The fix from a maintainer's perspective is to change the bluez package to start bluetoothd with the --compat option and the obex-data-server to start the daemon with root privileges. This is a really "noisy" solution, though. The fix from a developer's perspective is to replace the deprecated obex-data-server with bluez-obexd in blueman which is on it's way upstream anyway. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
