We believe that should be fixed by those commits

* https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/e807cbd8
 client: Fix bluetooth_client_set_trusted() not working 

(that would probably explain the LinkKey section missing from the
config)

* https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/4f1e0b35
' lib: Always try to pair pointer devices '

Those fixes are in 3.32 in disco and I've uploaded a bionic SRU now
https://launchpadlibrarian.net/418989286/gnome-bluetooth_3.28.0-2ubuntu0.2_source.changes

(the SRU needs to be reviewed/accepted next)

** Description changed:

+ * Impact
+ Bluetooth pointer devices are not always correctly paired, which leads to 
have them failing to connect or not auto-reconnecting
+ 
+ *  Test case
+ Pair a bluetooth mouse, it should re-connect automatically after 
suspend/resume or reboot cycles
+ 
+ * Regression potential
+ The change makes all devices go through pairing with the standard code that 
should work fine but we should keep an eye if it confuses some devices and lead 
to prompt for a PIN when that shouldn't be needd
+ 
+ ------------------------------------------
+ 
  This affects at least 2 different bluetooth mice(both logitech)
- The behavior is that initial config when using the gui works but that the 
resulting 
+ The behavior is that initial config when using the gui works but that the 
resulting
  "/var/lib/bluetooth/<controler mac>/<device mac>/info" file does not contain 
a [LinkKey] section as the mouse does not require a pin.
  This mouse was connection on reboot under 16.04 so it's a new bug for 18.04
  
  When setting up the mouse using bluetoothctl the info file is correctly
  written with a [LinkKey] section and everything works,
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-bluetooth 3.28.0-2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 29 11:27:27 2018
  InstallationDate: Installed on 2018-06-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: bluez (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-bluetooth (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-bluetooth (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1779289

Title:
  [regression] bluetooth mouse not reconnected on reboot

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Bluetooth pointer devices are not always correctly paired, which leads to 
have them failing to connect or not auto-reconnecting

  *  Test case
  Pair a bluetooth mouse, it should re-connect automatically after 
suspend/resume or reboot cycles

  * Regression potential
  The change makes all devices go through pairing with the standard code that 
should work fine but we should keep an eye if it confuses some devices and lead 
to prompt for a PIN when that shouldn't be needd

  ------------------------------------------

  This affects at least 2 different bluetooth mice(both logitech)
  The behavior is that initial config when using the gui works but that the 
resulting
  "/var/lib/bluetooth/<controler mac>/<device mac>/info" file does not contain 
a [LinkKey] section as the mouse does not require a pin.
  This mouse was connection on reboot under 16.04 so it's a new bug for 18.04

  When setting up the mouse using bluetoothctl the info file is
  correctly written with a [LinkKey] section and everything works,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-bluetooth 3.28.0-2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 29 11:27:27 2018
  InstallationDate: Installed on 2018-06-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to