[regression] bluetooth mouse not reconnected on reboot

Status changed to 'Confirmed' because the bug affects multiple users.

Bug affected also a disco dingo

Thanks.

That reminds me, make sure you don't have 'tlp' installed. Because that would be bug 1574311 instead.

Thanks.

Confirm, the tlp not installed.

Mouse: Acer MT1BF
One more thing, the use of bluetoothctl is not resolving issue.

Its look like the issue is on usage the connect/pair command.

When use a bluetoothctl 'connect' command, the connection is established, with info:

[CHG] Device <device mac> ServicesResolved: yes
[CHG] Device <device mac> Paired: yes
Connection successful

but the [LinkKey] section is not stored in 'info' file.

When use a bluetoothctl 'pair' command, the connection is established, with info:

[CHG] Device <device mac> ServicesResolved: yes
[CHG] Device <device mac> Paired: yes
Pairing successful

and the [LinkKey] section is on the 'info' file.

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)

BTLE persition mouse. There were problems with pair and repeated connection.( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413 ) All decided this way: https://gist.github.com/Mygod/f390aabf53cf1406fc71166a47236ebf

Hello dudsen, or anyone else affected,

Accepted gnome-bluetooth into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.28.0-2ubuntu0.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Accepted. Does it make sense to get this fix into cosmic as well?

Cosmic is neither a lTS nor the current stable, doesn't seem worth spending energy on it at this point

Hello,

The package in bionic-proposed has fixed the issue for me on Ubuntu 18.04.2 with a Logitech M535 mouse.

After installing the update I had to re-pair the mouse (I was expecting to have to do this anyway). The mouse now connects automatically after:
- waking up the laptop from sleep
- turning the bluetooth mouse off and on

In both instances without the fix I would have had to pair the mouse with the laptop again.

With the proposed fix installed, I discovered no regressions, my other bluetooth peripherals work as expected (previously paired keyboard and headphones connected automatically when turned on).

-Alex

Sorry, I forgot to add the package version to my previous comment (is there no way to edit a comment?): I've tested with gnome-bluetooth 3.28.0-2ubuntu0.2 from bionic-proposed.

The verification of the Stable Release Update for gnome-bluetooth has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package gnome-bluetooth - 3.28.0-2ubuntu0.2

---------------
gnome-bluetooth (3.28.0-2ubuntu0.2) bionic; urgency=medium

  * debian/patches/git_set_trusted.patch,
    debian/patches/git_pair_pointer.patch:
    - backport upstream commits to fix marking of device trusted on pairing
      not always working (leading to auto-reconnect not working).
      Always try to pair pointer devices also, that's expected by most
      recent devices, removing the specific list of devices which should
      use the default PIN and do that for all devices (lp: #1779289)

 -- Sebastien Bacher <email address hidden> Fri, 12 Apr 2019 15:06:49 +0200