Pairing: passcode dialogue disappears in <1 second

[PaulSchulz]

UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard
aside for a week (not use it), then reconnect after the laptop had been rebooted after an update
and daily use.

I will post the things that I tried, just in case:
  1) There is something I messed that someone else can suggest; and
  2) it occurs for someone else.

I suspect that it will happen again at some stage.

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

I am seeing this issue in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1

Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html

I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec).

System details
-----
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
-----
ii bluez 5.68-0ubuntu1.1 amd64 Bluetooth tools and daemons
------
Bluetooth Device

Logitech - Logi POP Keys (see link below)

[PaulSchulz (paulschulz)]

Related to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000

[PaulSchulz (paulschulz)]

I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1

Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html

I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec).

[PaulSchulz (paulschulz)]

- This occurs on my daily use laptop which has been upgraded from 23.04 -> 23.10

- I have just tried to pair on another laptop with freshly installed 23.10
  - The dialog displaying the pairing code persists
    and I can pair correctly with same keyboard (it can pair with 3 separate devices)
  - bluez 5.68-0ubuntu1.1

[PaulSchulz (paulschulz)]

Some things that I have tried which didn't immediately fix the problem.
----
Resetting the bluez package did NOT fix the problem.
  Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.

  sudo apt remove --purge bluez
  rm -rf /var/lib/bluetooth
  sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto

The bluetooth system needs to be started, and this empties the list of discovered bluetoothe devices,
but the popup for the keyboard auth number still disappears quickly again.

[PaulSchulz (paulschulz)]

FIX (Maybe?)

I put the keyboard aside for (about) a week. During this time the laptop when through a usual
 'apt update/apt upgrade' process and reboot.

When I tried to subsequently re-pair the keyboard, the 'passcode dialog' stayed visible,
and the keyboard paired.

Considerations:
- This laptop is not the fastest (i5-3210M CPU @ 2.50GHz), and this time I waited after
  entering the passcode (and pressinbg enter) for the pairing to be successful.
  This took maybe 5-10 sec. I may not have been as patient in the first case and quit
  the pairing dialog to try again.

- Deleting the detected entry for the keyboard in the Bluetooth list and getting it
  to be detected again, did not help.

[Daniel van Vugt (vanvugt)]

Incomplete: Waiting for the bug to reoccur... It sounds to me like a kernel or hardware problem though, in which the device itself is believed to have disappeared, and so would the dialog.

[PaulSchulz (paulschulz)]

Strangeness (technical term) happened again, with the hardware Logitech Keyboard.

The device gets a (slightly) different name in the Bluetooth GUI dialog "Logi POP @ []"

Running 'bluetoothctl' when it is working, I see:
[CHG] Device D2:91:D2:B9:6B:B4 Name: Logi POP Keys
[CHG] Device D2:91:D2:B9:6B:B4 Alias: Logi POP Keys

at another time (when not working):
[CHG] Device D2:91:D2:B9:6B:B4 Name: Logi POP @
[CHG] Device D2:91:D2:B9:6B:B4 Alias: Logi POP @

The GUI displays "Logi POP @ []", where [] is a binary unicode character: [0 0, 0 E] (2x2 block)

[PaulSchulz (paulschulz)]

Odd bluetooth devce name.

[Daniel van Vugt (vanvugt)]

I'm not sure whether to call this a GUI bug or a feature. It depends on whether the device changing its name, but keeping the same ID, should affect your ability to pair with it.