Problème Ubuntu Gnome Bluetooth

Problème Ubuntu Gnome Bluetooth - Installation - Linux et OS Alternatifs

Marsh Posté le 14-08-2014 à 12:05:41    

Bonjour,
 
Cela fait depuis longtemps que j'ai Linux Ubuntu (tout est relatif : 1 ans). Et aucun problème.
 
J'ai décidé de passer à Ubuntu Gnome 14.04 LTS et là j'ai un petit problème.
 
Après la réinstallation (seulement du swap & / ) le Bluetooth ne fonctionne pas.
 
Voici le problème :
1/ Je vais dans paramètres
2/ Bluetooth
3/ J'active le Bluetooth et là... Il s'active puis se désactive instantanément
 
J'ai beau fouiller dans les paramètres et reboot : Je ne trouve pas.
 
Voici le fichier des paramètres dans /etc/bluetooth à l'état d'origine
 

Code :
  1. [General]
  3. # List of plugins that should not be loaded on bluetoothd startup
  4. #DisablePlugins = network,input
  6. # Default adaper name
  7. # %h - substituted for hostname
  8. # %d - substituted for adapter id
  9. Name = %h-%d
  11. # Default device class. Only the major and minor device class bits are
  12. # considered.
  13. Class = 0x000100
  15. # How long to stay in discoverable mode before going back to non-discoverable
  16. # The value is in seconds. Default is 180, i.e. 3 minutes.
  17. # 0 = disable timer, i.e. stay discoverable forever
  18. DiscoverableTimeout = 0
  20. # How long to stay in pairable mode before going back to non-discoverable
  21. # The value is in seconds. Default is 0.
  22. # 0 = disable timer, i.e. stay pairable forever
  23. PairableTimeout = 0
  25. # Use some other page timeout than the controller default one
  26. # which is 16384 (10 seconds).
  27. PageTimeout = 8192
  29. # Automatic connection for bonded devices driven by platform/user events.
  30. # If a platform plugin uses this mechanism, automatic connections will be
  31. # enabled during the interval defined below. Initially, this feature
  32. # intends to be used to establish connections to ATT channels.
  33. AutoConnectTimeout = 60
  35. # What value should be assumed for the adapter Powered property when
  36. # SetProperty(Powered, ...) hasn't been called yet. Defaults to true
  37. InitiallyPowered = true
  39. # Remember the previously stored Powered state when initializing adapters
  40. RememberPowered = false
  42. # Use vendor id source (assigner), vendor, product and version information for
  43. # DID profile support. The values are separated by ":" and assigner, VID, PID
  44. # and version.
  45. # Possible vendor id source values: bluetooth, usb (defaults to usb)
  46. #DeviceID = bluetooth:1234:5678:abcd
  48. # Do reverse service discovery for previously unknown devices that connect to
  49. # us. This option is really only needed for qualification since the BITE tester
  50. # doesn't like us doing reverse SDP for some test cases (though there could in
  51. # theory be other useful purposes for this too). Defaults to true.
  52. ReverseServiceDiscovery = true
  54. # Enable name resolving after inquiry. Set it to 'false' if you don't need
  55. # remote devices name and want shorter discovery cycle. Defaults to 'true'.
  56. NameResolving = true
  58. # Enable runtime persistency of debug link keys. Default is false which
  59. # makes debug link keys valid only for the duration of the connection
  60. # that they were created for.
  61. DebugKeys = false
  63. # Enable the GATT functionality. Default is false
  64. EnableGatt = false


 
Est-ce-que vous avez des solutions ? Ou le même problème ?
Merci d'avance
 
EDIT : Config = Asus série Zenbook UX32A
 
Rbn


Message édité par rbn le 14-08-2014 à 12:12:33
Reply

Marsh Posté le 14-08-2014 à 12:05:41   

Reply

Marsh Posté le 16-08-2014 à 09:29:09    

Un "rfkill list" dans un terminal te donne quoi? Est-ce que tu peux activer le bluetooth avec "rfkill unblock bluetooth"?

Message cité 1 fois
Reply

Marsh Posté le 16-08-2014 à 10:20:44    

djam a écrit :

Un "rfkill list" dans un terminal te donne quoi? Est-ce que tu peux activer le bluetooth avec "rfkill unblock bluetooth"?


 
Un 'rfkill list' donne ça :
 
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: asus-wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: asus-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: no
 
Et avec rfkill "unblock bluetooth" le bluetooth s'active parfaitement ! Donc merci beaucoup !
 
Juste 1 truc : Comment faire pour que le bluetooth s'active directement de gnome ?
 
Merci encore !

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed