Bug 847860

The bluez5 branch from git://anongit.kde.org/libbluedevil is not working either for me.

erm, one need to recompile also bluedevil main package after so name change ...
trying in home:adrianSuSE:branches:KDE:Distro:Factory

it builds, but it does not change the not found adapters.

What about to ship also or only bluez 4 when version 5 is not working on the desktop yet?

Adrian,

Unfortunately Bluez4 is not co-installable with Bluez5. The Gnome version which is being shipped with 13.1 required Bluez5. 

We know that Bluedevil currently in KDE does not support Bluez5 yet.  Working is ongoing in the Bluez5 branch for both bluedevil and libbluedevil, as you already have seen. 

The upstream developer is working on adding the support, but he is focused on the Fedora schedule which doesn't really help us. 

So most likely 13.1 will be shipped without working Bluetooth support in KDE and we will provide a maintenance update as soon as it is ready. 

Alternatively we could ship with the git snapshots for the Bluez5 branch, but the upstream developer clearly indicated that he will not accept any bugreports for it.

*** Bug 846801 has been marked as a duplicate of this bug. ***

A git snapshot of Bluedevil has been delivered, however it has severely reduced functionality. On my ThinkPad X220, Bluetooth mouse support is non-existent.

*** Bug 849318 has been marked as a duplicate of this bug. ***

(:, RC2 bluetooth don't work.

I am reading that probably OS 13.1 will be delivered without a KDE working Bluetooth. This is annoying... I have great pressure to put this version in operation as soon as the final version is out. But with this bug seems not be possible. Question: when can we estimate to get a maintenance update of OS 13.1 with an operational bluetooth in KDE ? THX to all the Opensuse team.

Hi all. Bluetooth is working for me in 13.1 XFCE configured with
"bluetoothctl". Audio is not working. bluetooth module in pulseaudio doesn't register. If you observe problems, I'd propose to post an output (as root) of "hwinfo --bluetooh", "hciconfig -a" and check rfkill as well. And use (as user) bluetoothctl. Sometimes the controller is down after suspend, or reboot.

# hwinfo --bluetooth
07: USB 00.0: 11500 Bluetooth Device                            
  [Created at usb.122]
  Unique ID: doL0.7ZaCi_rwqr7
  Parent ID: FKGF.4Nx_qoDfSd7
  SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0
  SysFS BusID: 2-1.6:1.0
  Hardware Class: bluetooth
  Model: "HP Integrated Module"
  Hotplug: USB
  Vendor: usb 0x03f0 "HP"
  Device: usb 0x231d "HP Integrated Module"
  Revision: "3.06"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v03F0p231Dd0306dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

# hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 70:F3:95:81:BE:7D  ACL MTU: 1021:8  SCO MTU: 64:1
        DOWN 
        RX bytes:484 acl:0 sco:0 events:20 errors:0
        TX bytes:323 acl:0 sco:0 commands:20 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 

# rfkill list all
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hp-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
4: hp-wwan: Wireless WAN
        Soft blocked: no
        Hard blocked: no

# hciconfig hci up
# hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 70:F3:95:81:BE:7D  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING PSCAN 
        RX bytes:992 acl:0 sco:0 events:44 errors:0
        TX bytes:911 acl:0 sco:0 commands:44 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
        Name: 'probook'
        Class: 0x0c010c
        Service Classes: Rendering, Capturing
        Device Class: Computer, Laptop
        HCI Version: 2.1 (0x4)  Revision: 0x132
        LMP Version: 2.1 (0x4)  Subversion: 0x4203
        Manufacturer: Broadcom Corporation (15)

#groups vlado
vlado : users audio cdrom wheel
#bluetoothctl 
[NEW] Controller 70:F3:95:81:BE:7D probook [default]
[NEW] Device 00:1A:45:BA:86:CF Jabra BT8040
[NEW] Device 18:46:17:EC:BE:15 vlado.tab
[bluetooth]#

Regarding: Bluetooth is working for me in 13.1 XFCE configured with
"bluetoothctl".

I just want to point out that this report is about the GUI tools in first place. So for the end-user using our default desktop there is no working blutooth support atm.

Also, even after configuring it manual via bluez and pa command line tools connections getting lost suddenly. So, right now we can claim openSUSE 13.1 blutooth free :)

For an end-user of XFCE the most disappointing thing is the missing bluetooth GUI.

So as a temporary workaround I use the KDE4 applet bluedevil-monolithic. 

Because this applet works in XFCE probably as good as in KDE4 I added an entry of /usr/bin/bluedevil-monolithic to the list of other applications which will be automatic started during XFCE login procedure. With bluedevil-monolithic the end-user can avoid to handle with the CLI-based bluetoothctl. 

And yes, this entry must be created for every XFCE user. 

(Can't say anything about the dependancy chain, because first I installed KDE4 and later as the second desktop I installed XFCE. Don't know how many modules bluedevil-monolithic needs if XFCE runs as single desktop.)

I can confirm that bluetooth problems still exists in 13.1 (KDE). I can connect my Microsoft bluetooth keyboard manually with bluetoothctl, but it only reconnects after login. Is there any start-up script which could start this bluetoot before user login?

(In reply to comment #13)
> I can confirm that bluetooth problems still exists in 13.1 (KDE). I can connect
> my Microsoft bluetooth keyboard manually with bluetoothctl, but it only
> reconnects after login. Is there any start-up script which could start this
> bluetoot before user login?

Very probably the controller is down. You can check it from the terminal 1) Ctrl-ALt-F1 2)login as root 3)hciconfig -a

If so, you can bring it up #hciconfig hci0 up. There are some discussions how-to solve this systematically
https://bbs.archlinux.org/viewtopic.php?id=166362

(In reply to comment #14)
> (In reply to comment #13)
> > I can confirm that bluetooth problems still exists in 13.1 (KDE). I can connect
> > my Microsoft bluetooth keyboard manually with bluetoothctl, but it only
> > reconnects after login. Is there any start-up script which could start this
> > bluetoot before user login?
> 
> Very probably the controller is down. You can check it from the terminal 1)
> Ctrl-ALt-F1 2)login as root 3)hciconfig -a

This command tells:

hci1:   Type: BR/EDR  Bus: USB
        BD Address: 00:07:61:E3:72:65  ACL MTU: 1017:7  SCO MTU: 64:1
        DOWN 
        RX bytes:471 acl:0 sco:0 events:18 errors:0
        TX bytes:76 acl:0 sco:0 commands:18 errors:0
        Features: 0xff 0xfe 0x8d 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF 
        Link mode: SLAVE ACCEPT 

hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN 
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:3 acl:0 sco:0 commands:1 errors:0
        Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DH1 HV1 
        Link policy: 
        Link mode: SLAVE ACCEPT
> 
> If so, you can bring it up #hciconfig hci0 up. There are some discussions
> how-to solve this systematically
> https://bbs.archlinux.org/viewtopic.php?id=166362

adding a /etc/udev/rules.d/10-local.rules with this content: 

# Set bluetooth power up
ACTION=="add", KERNEL=="hci1", RUN+="dbus-send --system --type=method_call --print-reply=literal --dest=org.bluez /org/bluez/hci1 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true"

did not change a thing. Keyboard is avaible a few seconds after login.

> adding a /etc/udev/rules.d/10-local.rules with this content: 
> 
> # Set bluetooth power up
> ACTION=="add", KERNEL=="hci1", RUN+="dbus-send --system --type=method_call
> --print-reply=literal --dest=org.bluez /org/bluez/hci1
> org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered
> variant:boolean:true"
> 
> did not change a thing. Keyboard is avaible a few seconds after login.

dbus might not be available when the controler is registred. Probably plain "hciconfig hci1 up" might fit the purpose better.

(In reply to comment #16)

> dbus might not be available when the controler is registred. Probably plain
> "hciconfig hci1 up" might fit the purpose better.

I did try this. No change :(

Did not resolve my problem. Any other hint?

(In reply to comment #17)
> Did not resolve my problem. Any other hint?

Yes. As a hint. Wana try this one :)

I've tried the systemd service below as of the comment 
http://archlinuxarm.org/forum/viewtopic.php?f=31&t=5935
,but unfortunately didn't succeed.

# systemctl daemon-reload
# systemctl start bluetooth-up
The command didn't return and journalctl says
Nov 27 11:14:24 probook systemd[1]: Starting Bring Up Bluetooth...

Very probably I'm missing something.


# cat /usr/lib/systemd/system/bluetooth-up.service
[Unit]
Description=Bring Up Bluetooth
After=bluetooth.target

[Service]
Type=oneshot
ExecStart=/usr/bin/hciconfig hci0 up
# TimeoutSec=0
# StandardInput=tty
# RemainAfterExit=yes

[Install]
WantedBy=bluetooth.target

Is there any further solution to activate bluetooth keyboard at login prompt?

I can confirm that the bluedevil assistant works for me in version 1.3.8 with bluez 5.11 from KDE unstable.

Technically we need to update both bluez and bluedevil to make this work.

I am not sure if we want to do this for 13.1 which ends support in 1 month...

@Stefan: do you want to do the update of bluez to 5.11 or later?

This problem is not persistent on any later openSUSE releases.

What exactly do we need from bluez 5.11? A bugfix or added functionality?

And is the kde fix supposed to be delivered as an maintenance update or is this just for those that more or less illegally and totally unsupportedly (according to richards opinion on opensuse-factory ;-P) install packages from "random buildservice repositories?

(take the above with a grain of salt ;))

If you want to put out a maint. update that needs this, then I'd rather like to backport the fix if possible instead of updating.
If it's for packages from (example) KDE:STABLE:BACKPORTS, then we could put newer bluez for 13.1 into that repository and not risk breakage for GNOME users.

TBH I am not sure what fixes are needed. That's why it was never probably completed.

The bluetooth started working when the bluez is updated to 5.10 and later and bluedevil 1.3.7 or later.

But in my PoV it was fixed in 13.2 and later so we can just point user to use those releases if you think it is too dangerous and close this bug as won'tfix.

Ok, let's close this as WONTFIX (or rather "RESOLVED UPSTREAM", as it's fixed in a later version).

And bluedevil in 13.1 is too old anyway.