FS#16767 - [gnome-bluetooth] not working (with fix)
Attached to Project:
Arch Linux
Opened by Tom Billiet (mouse256) - Wednesday, 21 October 2009, 15:03 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 08 April 2010, 23:50 GMT
Opened by Tom Billiet (mouse256) - Wednesday, 21 October 2009, 15:03 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 08 April 2010, 23:50 GMT
|
Details
Description: gnome-bluetooth is not working for quite some
people, as discussed in
http://bbs.archlinux.org/viewtopic.php?pid=641198. The solution is also in the topic.
symptoms: bluetoothd -nd bluetoothd[4295]: Bluetooth daemon 4.56 bluetoothd[4295]: Enabling debug information bluetoothd[4295]: parsing main.conf bluetoothd[4295]: discovto=0 bluetoothd[4295]: pairto=0 bluetoothd[4295]: pageto=8192 bluetoothd[4295]: name=%h-%d bluetoothd[4295]: class=0x000100 bluetoothd[4295]: discov_interval=0 bluetoothd[4295]: Key file does not have key 'DeviceID' bluetoothd[4295]: Unable to get on D-Bus bluetooth-applet ** (bluetooth-applet:19014): WARNING **: Could not open RFKILL control device, please verify your installation Solution: (thanks to syntaxerrormmm, works also for me) Add a file /etc/udev/rules.d/xx-gnome-bluetooth.rules with the following content: # Get access to /dev/rfkill for group 'uucp' # See https://bugzilla.redhat.com/show_bug.cgi?id=514798 KERNEL=="rfkill", ENV{ACL_MANAGE}="1", GROUP="uucp" maybe also add an install message that you have to add your user to the uucp group. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 08 April 2010, 23:50 GMT
Reason for closing: Won't implement
Thursday, 08 April 2010, 23:50 GMT
Reason for closing: Won't implement
gnome-bluetooth doesn't work and it is not in testing: I should expect a package in extra should just work, stop. Implement it how you like, I don't mind. Oh, another thing: uucp membership is already required for using bluetooth serial connections as user.
@fabioamd: Have you added yourself to 'uucp' group?
As for my previous statements, I sincerely apologize. I understand that maybe not anyone is involved in Arch Linux project shares my point of view. What I really want is to see an OS that works out of the box and "upstream rejected that" or the like simply don't fit the purpose.
I've been investigating a little in ACL later and it can be a solution (also, I've learned something new); in any case, you have to inform the user that some changes are needed and how to make them.
It seems you have another (better) solution for this problem (with the use of ACL's). Can you give some details about it, I will be glad to try it out.
http://pastebin.com/m7dbd44cc