https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c1 --- Comment #1 from Adrian Schröter <adrian@suse.com> 2013-10-28 11:55:23 UTC --- The bluez5 branch from git://anongit.kde.org/libbluedevil is not working either for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c3 Adrian Schröter <adrian@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |vbotka@suse.com --- Comment #3 from Adrian Schröter <adrian@suse.com> 2013-10-28 13:22:45 UTC --- 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? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c4 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tittiatcoke@gmail.com --- Comment #4 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-10-30 10:32:28 UTC --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c6 Richard Fenoglio Jr <fenoglior@rialfe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fenoglior@rialfe.com --- Comment #6 from Richard Fenoglio Jr <fenoglior@rialfe.com> 2013-11-12 17:12:57 UTC --- A git snapshot of Bluedevil has been delivered, however it has severely reduced functionality. On my ThinkPad X220, Bluetooth mouse support is non-existent. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c8 Dmitry Ashkadov <dmitry.ashkadov@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmitry.ashkadov@gmail.com --- Comment #8 from Dmitry Ashkadov <dmitry.ashkadov@gmail.com> 2013-11-12 17:57:40 UTC --- (:, RC2 bluetooth don't work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c10 Vladimir Botka <vbotka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |vbotka@suse.com InfoProvider|vbotka@suse.com | --- Comment #10 from Vladimir Botka <vbotka@suse.com> 2013-11-22 08:21:58 UTC --- 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]# -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c12 Dieter Brozio <dibro@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dibro@gmx.de --- Comment #12 from Dieter Brozio <dibro@gmx.de> 2013-11-24 17:38:07 UTC --- 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.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c14 --- Comment #14 from Vladimir Botka <vbotka@suse.com> 2013-11-27 07:42:27 UTC --- (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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c16 --- Comment #16 from Vladimir Botka <vbotka@suse.com> 2013-11-27 09:14:28 UTC ---

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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847860 https://bugzilla.novell.com/show_bug.cgi?id=847860#c18 --- Comment #18 from Vladimir Botka <vbotka@suse.com> 2013-11-27 10:22:18 UTC --- (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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.