web-dev-qa-db-fra.com

Fonctionnalité Bluetooth perdue après la mise à niveau de 17.04 à 17.10

Il y a un jour ou avant que je mette à jour du 17.04 au 17.10, j'ai été capable de connecter mon ordinateur avec mon casque via Bluetooth. Maintenant je ne peux pas. Je pensais que j'avais peut-être besoin d'installer Bluetooth Manager et l'adaptateur Bluetooth à partir du gestionnaire de logiciels, mais cela n'a pas aidé. Quelqu'un peut-il suggérer un code que je peux utiliser via le terminal pour réinstaller les pilotes Bluetooth ou tout ce qui ne fonctionne pas afin que je puisse utiliser à nouveau la fonction Bluetooth sur mon ordinateur? Dans les paramètres, Bluetooth, il est indiqué de connecter un dongle pour utiliser le Bluetooth maintenant. Il ne l'a pas dit auparavant. 

brian @ brian-Gazelle-Professional: ~ $ Etat Bluetooth du service Sudo 
 [Sudo] mot de passe pour brian: 
 ● bluetooth.service - service Bluetooth 
 Chargé: chargé (/ lib/systemd/system/bluetooth.service; activé; préréglage fournisseur 
 actif: inactif (mort) 
 Docs: man: bluetoothd (8) 
 
 brian @ brian- Gazelle-Professional: ~ $ dmesg | grep -i blue 
 [1837.682565] audit: type = 1400 audit (1509035362.629: 112): apparmor = "STATUS" operation = "profile_load" profile = "non confiné" name = " snap.bluez.bluetoothctl "pid = 5534 comm =" apparmor_parser "
 [1837.739136] audit: type = 1400 audit (1509035362.686: 113): apparmor =" STATUS "operation =" profile_load "profile =" non défini "nom = "snap.bluez.bluez" pid = 5536 comm = "apparmor_parser" 
 [1837.796899] audit: type = 1400 audit (1509035362.743: 114): apparmor = "STATUS" operation = "profile_load" profile = "non défini "name =" snap.bluez.btmgmt "pid = 5538 comm =" apparmor_parser "
 [1837.855706] audit: type = 1400 audit (150903536 2.802: 115): apparmor = "STATUS" operation = "profile_load" profile = "non confiné" name = "snap.bluez.btmon" pid = 5540 comm = "apparmor_parser" 
 [1837.906840] audit: type = 1400 audit (1509035362.853: 116): apparmor = "STATUS" operation = "profile_load" profile = "non confiné" name = "snap.bluez.hciattach" pid = 5542 comm = "apparmor_parser" 
 [1837.960018] audit: type = 1400 audit (1509035362.906: 117): apparmor = "STATUS" operation = "profile_load" profile = "unconfined" name = "snap.bluez.hciconfig" pid = 5544 comm = "apparmor_parser" 
 [1838.017010] audit : type = 1400 audit (1509035362.963: 118): apparmor = "STATUS" operation = "profile_load" profile = "unconfined" name = "snap.bluez.hcidump" pid = 5546 comm = "apparmor_parser" 
 [1838.071942 ] audit: type = 1400 audit (1509035363.018: 119): apparmor = "STATUS" operation = "profile_load" profile = "unconfined" name = "snap.bluez.hcitool" pid = 5548 comm = "apparmor_parser" 
 [1838.121894] audit: type = 1400 audit (1509035363.068: 120): apparmor = "STATUS" operation = "profile_load" pro file = "unconfined" name = "snap.bluez.obex" pid = 5550 comm = "apparmor_parser" 
 [1838.170836] audit: type = 1400 audit (1509035363.117: 121): apparmor = "STATUS" operation = " profile_load "profile =" non confiné "name =" snap.bluez.obexctl "pid = 5552 comm =" apparmor_parser "
upgradesoundbluetoothsettingsbluez
2
B. Kunzelmann

J'ai mis à jour Kubuntu de 17.04 à 17.10 hier.

Généralement, le même problème pour moi, je ne peux plus connecter mon haut-parleur Bluetooth (RYGHT TANK) même si mon service Bluetooth est en cours d'exécution.

Voici mes résultats Sudo service bluetooth status et dmesg | grep -i blue:

soul@soul-ZBOX-ID88-ID89-ID90:~$ Sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2017-10-27 23:50:19 CEST; 5min ago
     Docs: man:bluetoothd(8)
 Main PID: 11613 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─11613 /usr/lib/bluetooth/bluetoothd

oct. 27 23:50:18 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Bluetooth daemon 5.46
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Starting SDP server
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Bluetooth management interface 1.14 initialized

soul@soul-ZBOX-ID88-ID89-ID90:~$ dmesg | grep -i blue
[   21.008903] Bluetooth: Core ver 2.22
[   21.008918] Bluetooth: HCI device and connection manager initialized
[   21.008920] Bluetooth: HCI socket layer initialized
[   21.008922] Bluetooth: L2CAP socket layer initialized
[   21.008927] Bluetooth: SCO socket layer initialized
[   31.455093] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   31.455095] Bluetooth: BNEP filters: protocol multicast
[   31.455098] Bluetooth: BNEP socket layer initialized
[  116.012720] Bluetooth: RFCOMM TTY layer initialized
[  116.012730] Bluetooth: RFCOMM socket layer initialized
[  116.012738] Bluetooth: RFCOMM ver 1.11

Un écran d’impression du message après une tentative de connexion: échec de connexion

Une idée?

EDIT (11/05):

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2017-11-05 09:42:42 CET; 7h ago
     Docs: man:bluetoothd(8)
 Main PID: 958 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─958 /usr/lib/bluetooth/bluetoothd

nov. 05 09:42:40 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
nov. 05 09:42:40 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Bluetooth daemon 5.46
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Starting SDP server
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Bluetooth management interface 1.14 initialized
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
nov. 05 16:32:46 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available
nov. 05 16:32:54 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available
nov. 05 16:33:02 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available

EDIT (11/05) (après avoir installé pulseaudio-module-bluetooth):

soul@soul-ZBOX-ID88-ID89-ID90:~$ service bluetooth status
    ● bluetooth.service - Bluetooth service
       Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
       Active: active (running) since Sun 2017-11-05 17:05:04 CET; 3min 32s ago
         Docs: man:bluetoothd(8)
     Main PID: 875 (bluetoothd)
       Status: "Running"
        Tasks: 1 (limit: 4915)
       CGroup: /system.slice/bluetooth.service
               └─875 /usr/lib/bluetooth/bluetoothd

    nov. 05 17:04:57 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
    nov. 05 17:04:58 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Bluetooth daemon 5.46
    nov. 05 17:05:04 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
    nov. 05 17:05:04 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Starting SDP server
    nov. 05 17:05:05 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Bluetooth management interface 1.14 initialized
    nov. 05 17:06:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource
    nov. 05 17:06:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink
    nov. 05 17:07:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
    nov. 05 17:07:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: connect error: Connection refused (111)
    nov. 05 17:07:26 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: connect error: Connection refused (111)

EDIT (11/05 got it!): Je me suis retrouvé avec une solution:

Sudo apt install kmix
reboot

ensuite

Sudo apt install pulseaudio-module-bluetooth
reboot
pactl load-module module-bluetooth-discover

(La dernière commande peut échouer)

Ensuite, supprimez tous vos périphériques Bluetooth enregistrés et reliez-les.

N'oubliez pas de placer les périphériques Bluetooth en haut de la liste de la configuration audio: Kmix configuration

3
s.aaliy