The default ebuild of net-wireless/bluedevil-1.0 would just not detect my bluetooth device. I noticed that dbus does not allow a regular user to connect to bluetoothd: Jan 21 01:04:07 draget dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.8" (uid=1000 pid=5701 comm="/usr/bin/bluedevil-monolithic) interface="org.bluez.Adapter" member="GetProperties" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=5377 comm="/usr/sbin/bluetoothd)) Jan 21 01:04:07 draget dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.19" (uid=1000 pid=6625 comm="/usr/bin/bluedevil-helper) interface="org.bluez.Manager" member="DefaultAdapter" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=5377 comm="/usr/sbin/bluetoothd)) Jan 21 01:04:07 draget dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.19" (uid=1000 pid=6625 comm="/usr/bin/bluedevil-helper) interface="org.bluez.Manager" member="DefaultAdapter" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=5377 comm="/usr/sbin/bluetoothd)) Checking my /etc/dbus-1/system.d/bluetooth.conf configuration I noticed that only root and users in the 'lp' group can access it. Maybe a suid mechanism or an ebuild POST message would clear things up. 'Please add every user that should be allowed to control the bluetooth device to the 'lp' group.' Not sure how upstreams handles this. Reproducible: Always Steps to Reproduce:
As it seems to be a wrapper around bluez, probably the same way bleuz does - preferably via consolekit. Still, this looks more like a support question than a bug report.
Please add the output of emerge --info Which bluez and kde versions are you using?
No reply for two months.
