Bonjour

Je rencontre un problème avec le bluetooth sur mon laptop dell xps 13. Je ne peux connecter aucun périphérique bluetooth.
Voici ma configuration :
Linux localhost.localdomain 4.5.4-200.fc23.x86_64 #1 SMP Wed May 11 17:54:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost log]# blueman-report
Terminating blueman-applet
Describe your next action (keep empty if done): 

=====================================

Use this data in your report:

=====================================

blueman: 2.0.4
BlueZ: 5.39
Distribution: 
Traceback (most recent call last):
  File "/usr/bin/blueman-report", line 83, in <module>
    print("Desktop: " + os.environ.get('XDG_CURRENT_DESKTOP'))
TypeError: Can't convert 'NoneType' object to str implicitly

[root@localhost log]# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since mar. 2016-05-17 14:43:33 CEST; 38min ago
     Docs: man:bluetoothd(8)
 Main PID: 929 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─929 /usr/libexec/bluetooth/bluetoothd

mai 17 14:52:22 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 14:55:36 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 14:56:06 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 14:57:20 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 14:57:34 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 15:01:59 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 15:02:26 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 15:16:02 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 15:16:26 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
mai 17 15:20:16 localhost.localdomain bluetoothd[929]: Failed to set mode: Failed (0x03)
[root@localhost log]# bluetoothctl 
[NEW] Controller 80:56:F2:BD:33:32 ChromeLinux_96F0 [default]
[NEW] Device 00:1F:20:7E:9E:81 Logitech Bluetooth Mouse M555b
[NEW] Device C0:33:5E:27:70:E6 SI20662
[NEW] Device 1C:48:F9:E8:0D:5B Jabra EVOLVE 65
[NEW] Device EF:76:96:5E:27:07 MX Anywhere 2
[NEW] Device 00:1F:20:99:96:E6 Ultrathin Touch Mouse
[bluetooth]# show
Controller 80:56:F2:BD:33:32
	Name: localhost.localdomain
	Alias: ChromeLinux_96F0
	Class: 0x000000
	Powered: no
	Discoverable: yes
	Pairable: yes
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0527
	Discovering: no
là je vois "powered : no" et je me dis "Ben power on !"
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed
[bluetooth]# 

Et maintenant, je ne me dis plus rien... j'appelle un ami. Quelques pistes pour m'aider à deboguer ?

Merci !

Laurent
Pour anticiper certaines questions :

J'ai bien un controller bluetooth :
[root@localhost log]# lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QS77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
Le controller n'est pas "bloqué"
[root@localhost log]# rfkill list
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
[root@localhost log]# hciconfig -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 80:56:F2:BD:33:32  ACL MTU: 1022:8  SCO MTU: 183:5
	DOWN 
	RX bytes:322 acl:0 sco:0 events:7 errors:0
	TX bytes:21 acl:0 sco:0 commands:12 errors:5
	Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: 
	Link mode: SLAVE ACCEPT 
[root@localhost log]# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
J'essaierais bien une petite claque dans sa gueule, mais j'ai peur que ça marche plus après...
Bon... ben je pense que c'est un bug dans le Kernel puisque que quand je boote en 4.4.8 tout fonctionne correctement... A noter qu'en 4.4.9 hciconfig me renvoit toujours un timeout
Comment je peux remonter le bug ?
13 jours plus tard
Que retourne la commande:
sudo journalctl -b | grep -i blue
mai 30 11:35:39 localhost.localdomain kernel: usb 2-1.5: Product: Bluetooth USB Host Controller
mai 30 11:35:42 localhost.localdomain kernel: Bluetooth: Core ver 2.21
mai 30 11:35:42 localhost.localdomain kernel: Bluetooth: HCI device and connection manager initialized
mai 30 11:35:42 localhost.localdomain kernel: Bluetooth: HCI socket layer initialized
mai 30 11:35:42 localhost.localdomain kernel: Bluetooth: L2CAP socket layer initialized
mai 30 11:35:42 localhost.localdomain kernel: Bluetooth: SCO socket layer initialized
mai 30 11:37:42 localhost.localdomain systemd[1]: Starting Bluetooth service...
mai 30 11:37:42 localhost.localdomain bluetoothd[1031]: Bluetooth daemon 5.39
mai 30 11:37:42 localhost.localdomain bluetoothd[1031]: Starting SDP server
mai 30 11:37:42 localhost.localdomain kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
mai 30 11:37:42 localhost.localdomain kernel: Bluetooth: BNEP filters: protocol multicast
mai 30 11:37:42 localhost.localdomain kernel: Bluetooth: BNEP socket layer initialized
mai 30 11:37:42 localhost.localdomain bluetoothd[1031]: Bluetooth management interface 1.11 initialized
mai 30 11:37:42 localhost.localdomain bluetoothd[1031]: Failed to obtain handles for "Service Changed" characteristic
mai 30 11:37:43 localhost.localdomain systemd[1]: Started Bluetooth service.
mai 30 11:37:43 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 30 11:37:43 localhost.localdomain systemd[1]: Reached target Bluetooth.
mai 30 11:37:43 localhost.localdomain systemd[1]: Starting Bluetooth.
mai 30 11:37:43 localhost.localdomain NetworkManager[1321]: <info>  Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
mai 30 11:37:43 localhost.localdomain NetworkManager[1321]: <info>  use BlueZ version 5
mai 30 11:41:44 localhost.localdomain dbus[1003]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
mai 30 11:41:44 localhost.localdomain org.blueman.Mechanism[1003]: Unable to init server: Could not connect: Connection refused
mai 30 11:41:44 localhost.localdomain org.blueman.Mechanism[1003]: Unable to init server: Could not connect: Connection refused
mai 30 11:41:44 localhost.localdomain blueman-mechanism[2966]: Starting blueman-mechanism
mai 30 11:41:44 localhost.localdomain dbus[1003]: [system] Successfully activated service 'org.blueman.Mechanism'
mai 30 11:41:44 localhost.localdomain org.blueman.Mechanism[1003]: (blueman-mechanism:2966): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
mai 30 11:41:44 localhost.localdomain blueman-mechanism[2966]: loading Ppp
mai 30 11:41:44 localhost.localdomain blueman-mechanism[2966]: loading Rfcomm
mai 30 11:41:44 localhost.localdomain blueman-mechanism[2966]: loading Network
mai 30 11:41:44 localhost.localdomain blueman-mechanism[2966]: loading RfKill
mai 30 11:42:14 localhost.localdomain blueman-mechanism[2966]: Exiting
mai 30 11:47:10 localhost.localdomain kernel: Bluetooth: hci0 command 0x0c58 tx timeout
mai 30 11:47:12 localhost.localdomain kernel: Bluetooth: hci0 command 0x1004 tx timeout
mai 30 11:47:18 localhost.localdomain bluetoothd[1031]: Failed to set mode: Failed (0x03)
mai 30 13:21:52 localhost.localdomain python3[5454]: detected unhandled Python exception in '/usr/bin/blueman-applet'
mai 30 13:21:56 localhost.localdomain python3[5453]: detected unhandled Python exception in '/usr/bin/blueman-report'