Gnome-Bluetooth doesn't work after Gnome 2.28 update.

Szelek · 2009-10-13 08:54:22

It seems that gnome-bluetooth package is broken.
Before the update I have started bluetooth by Fn+F5. Now when the bluetooth is on the output looks like this

[szelek@IBM ~]$ bluetooth-applet 
** (bluetooth-applet:19014): WARNING **: Could not open RFKILL control device, please verify your installation
/home/szelek/.themes/AlunDark/gtk-2.0/gtkrc:98: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/home/szelek/.themes/AlunDark/gtk-2.0/gtkrc:99: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.

** (bluetooth-properties:19017): WARNING **: Could not open RFKILL control device, please verify your installation

** (bluetooth-properties:19017): WARNING **: Failed to change RFKILL state: Błędny deskryptor pliku

The button says: Turn Bluetooth On.
Bluetooth-preferences looks all the time the same. I can click on this button, it becomes grayed out (unavailable) but nothing happens afterwards.

I tried running bluetooth-wizard but it says that bluetooth is off even though it supposed to be turned on.

Maybe there are some problems with bluez configs after the update? Well I hope that someone have a solution for this one

aneiser · 2009-10-13 13:27:56

I experience the same problem after upgrading. Would be nice if someone had an idea...

combuster · 2009-10-13 13:37:18

Mine works ok, just browsed minisd on my motorola k1...

leeyee · 2009-10-13 14:59:07

well, I find the new gnome-bluetooth a little confusing. Before I was using blueman+bluez+gnome-bluetooth, and most functions were fine, i.e. send/receive files, dialup services(my phone is N70). However, now I uninstalled blueman, and I find gnome-bluetooth has much trouble in send/receive files(they may succeed some time but not always), browse device works partly(I can open directory tree of the phone, but cannot view the content, nor copy/paste files) and the dialup service is gone. Maybe the new GNOME release needs other assistances to enable dialup services with bluetooh cellphone?

mouse256 · 2009-10-15 15:43:08

I've got the same problem (dell studio 1555), it seems to be something udev related:
Running "bluetoothd -nd" prints "Unable to get on D-Bus", and then I found a reference to this post: http://markmail.org/message/sc37p3rauwvku5cb
Unfortunately, I could not get it solved, but maybe it can help somebody?

I've reinstalled bluez-gnome and it's working again (I need bluetooth for my mouse), but I don't consider that a definitive solution.

wonder · 2009-10-15 19:21:53

i do have the same problem as #1. i this bug on ubuntu which is fixed. https://bugs.launchpad.net/ubuntu/+sour … bug/436694
and the rules file is here: http://cvs.fedoraproject.org/viewvc/dev … iew=markup

can you try adding that rule? for me that is not solving the problem. does anyone know if we have acl supported?

Last edited by wonder (2009-10-15 19:22:31)

Szelek · 2009-10-16 12:23:25

sudo chmod 666 /dev/rfkill

solved the problem by now.

ammon · 2009-10-16 12:44:10

I cant recive files. And there is not confirmation when file is sended away. Only some warning. I does suceed to send, though.

Tudhalyas · 2009-10-18 14:18:21

I have a similar problem: I do not use bluez-gnome, just bluez and blueman, but after the dbus update I get this error in /var/log/errors.log:

Oct 18 15:39:07 paranor bluetoothd[3565]: Can't load plugin /usr/lib/bluetooth/plugins/netlink.so: /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug
Oct 18 15:39:07 paranor bluetoothd[3565]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Oct 18 15:39:07 paranor bluetoothd[3565]: probe failed with driver input-headset for device /org/bluez/3565/hci0/dev_00_22_66_D9_9B_C9

Also, when I try to launch bluetoothd manually, I get this...

[root@paranor ~]# 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

...while in errors.log I get these messages (after several attempts):

Oct 18 15:53:26 paranor bluetoothd[3914]: Unable to get on D-Bus
Oct 18 15:57:09 paranor bluetoothd[4156]: Unable to get on D-Bus
Oct 18 15:57:25 paranor obex-data-server: sdp_send_req_w4_rsp: Error sending data:Broken pipe
Oct 18 15:57:28 paranor bluetoothd[4181]: Unable to get on D-Bus
Oct 18 15:57:37 paranor bluetoothd[4198]: Unable to get on D-Bus
Oct 18 15:59:36 paranor bluetoothd[4224]: Unable to get on D-Bus
Oct 18 16:14:23 paranor bluetoothd[4271]: Unable to get on D-Bus
Oct 18 16:16:50 paranor bluetoothd[4295]: Unable to get on D-Bus

Can anybody help me? Thanks!!

syntaxerrormmm · 2009-10-21 13:27:39

Hi all,

I experienced both 'DBus' and 'rfkill' problems today with bluez 4.56-1 and gnome-bluetooth 2.28.1-1 and managed to fix both of them as follows.

Unable to get on D-Bus:
It seems (I'm not sure on this) that adding local user to the group 'lp' fixed the issue. Before that, I removed bluez and installed bluez-git from AUR and back to the default, so it's probably the latter action that fixed it.

Could not open RFKILL control device, please verify your installation:
As posted before, I've installed the rules for UDev modifying them a little as follows:

# 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"

Suggested filename should be something like /etc/udev/rules.d/gnome-bluetooth.rules and obviously user should be in 'uucp' group.

HTH, Thank you very much.

Last edited by syntaxerrormmm (2009-10-21 13:30:45)

mouse256 · 2009-10-21 15:04:02

thanks, this also works for me.
A bug report has been created so the package can be patched: http://bugs.archlinux.org/task/16767

Arch Linux

#1 2009-10-13 08:54:22

Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#2 2009-10-13 13:27:56

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#3 2009-10-13 13:37:18

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#4 2009-10-13 14:59:07

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#5 2009-10-15 15:43:08

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#6 2009-10-15 19:21:53

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#7 2009-10-16 12:23:25

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#8 2009-10-16 12:44:10

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#9 2009-10-18 14:18:21

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#10 2009-10-21 13:27:39

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

#11 2009-10-21 15:04:02

Re: Gnome-Bluetooth doesn't work after Gnome 2.28 update.

Board footer