[SOLVED] bluez failing

Legogris · 2013-11-01 21:24:06

I have had my Logitech bluetooth keyboard working OK with bluez4 for a while, but now I upgraded to bluez - and no dice.

sudo bluetoothctl -a

[NEW] Controller 74:2F:68:6A:37:44 moon-0 [default]
[NEW] Device 00:07:61:76:8E:78 Logitech diNovo Edge
Agent registered
[bluetooth]# list
Controller 74:2F:68:6A:37:44 moon-0 [default]
[bluetooth]# show
Controller 74:2F:68:6A:37:44
        Name: moon
        Alias: moon-0
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: yes
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0509
        Discovering: no
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Blocked
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# devices
Device 00:07:61:76:8E:78 Logitech diNovo Edge
[bluetooth]# info 00:07:61:76:8E:78
Device 00:07:61:76:8E:78
        Name: Logitech diNovo Edge
        Alias: Logitech diNovo Edge
        Class: 0x002540
        Icon: input-keyboard
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v046DpB309d011B
[bluetooth]# connect 00:07:61:76:8E:78
Attempting to connect to 00:07:61:76:8E:78
Failed to connect: org.bluez.Error.Failed

systemctl status bluetooth:

bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Fri 2013-11-01 22:14:13 CET; 8min ago
     Docs: man:bluetoothd(8)
 Main PID: 370 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─370 /usr/lib/bluetooth/bluetoothd

Nov 01 22:14:12 moon systemd[1]: Starting Bluetooth service...
Nov 01 22:14:13 moon bluetoothd[370]: Bluetooth daemon 5.9
Nov 01 22:14:13 moon systemd[1]: Started Bluetooth service.
Nov 01 22:14:13 moon bluetoothd[370]: Starting SDP server
Nov 01 22:14:13 moon bluetoothd[370]: Bluetooth management interface 1.3 initialized
Nov 01 22:15:07 moon bluetoothd[370]: Failed to set mode: Blocked through rfkill (0x12)
Nov 01 22:20:52 moon bluetoothd[370]: Failed to set mode: Blocked through rfkill (0x12)
Nov 01 22:21:20 moon bluetoothd[370]: Failed to set mode: Blocked through rfkill (0x12)
Nov 01 22:21:50 moon bluetoothd[370]: connect: No route to host (113)
Nov 01 22:21:50 moon bluetoothd[370]: input-hid profile connect failed for 00:07:61:76:8E:78: Input/output error

hcitool scan:

Device is not available: No such device

I'm stuck here.

Last edited by Legogris (2013-11-02 10:03:29)

AndyRTR · 2013-11-02 08:27:06

Your hci0 device is "DOWN", you probably need to "hciconfig hci0 up" before trying to connect it.

progandy · 2013-11-02 09:32:43

The error log mentions rfkill. Did you unblock your device with rfkill unblock ...?

Legogris · 2013-11-02 10:02:25

D'oh - rfkill was exactly it, shoukd have been obvious I guess. Strange though, as I never powered it down or blocked it in the first place. Thanks!

R00KIE · 2013-11-02 14:13:29

It seems to be new (?) behavior. For me I'm not sure if it was blueman that used to power on my usb bluetooth adapter or if bluetoothd did it, but now I have to manually power on the adapter every reboot or every time I plug it. I have noticed this happens only after the update from bluez4 to bluez5.

progandy · 2013-11-02 19:05:49

You might want to use an udev rule to unblock it and set the power on.

R00KIE · 2013-11-03 03:58:49

I came up with something like this, not sure if it can be improved.

KERNEL=="hci[0-9]*", SUBSYSTEM=="bluetooth", RUN+="/usr/bin/hciconfig %k up"

Arch Linux

#1 2013-11-01 21:24:06

[SOLVED] bluez failing

#2 2013-11-02 08:27:06

Re: [SOLVED] bluez failing

#3 2013-11-02 09:32:43

Re: [SOLVED] bluez failing

#4 2013-11-02 10:02:25

Re: [SOLVED] bluez failing

#5 2013-11-02 14:13:29

Re: [SOLVED] bluez failing

#6 2013-11-02 19:05:49

Re: [SOLVED] bluez failing

#7 2013-11-03 03:58:49

Re: [SOLVED] bluez failing

Board footer