Bluetooth settings panel shows duplicate device entries after failing to connect

[canadaduane]

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="21.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.10"
VERSION_ID="21.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=impish
UBUNTU_CODENAME=impish
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

gir1.2-gnomebluetooth-1.0/impish,now 3.34.5-3 amd64 [installed,automatic]
gnome-bluetooth/impish,now 3.34.5-3 amd64 [installed,automatic]
libgnome-bluetooth13/impish,now 3.34.5-3 amd64 [installed,automatic]
libmm-glib0/impish,now 1.16.6-2 amd64 [installed,automatic]
modemmanager/impish,now 1.16.6-2 amd64 [installed,automatic]
pulseaudio-module-bluetooth/impish,now 1:15.0+dfsg1-1ubuntu2 amd64 [installed,automatic]
rfkill/impish-updates,now 2.36.1-8ubuntu2 amd64 [installed,automatic]
totem-plugins/impish,now 3.38.1-1ubuntu1 amd64 [installed,automatic]

Issue/Bug Description:

When using the Settings/Bluetooth pane, and while trying to connect a Bose 700 headset that is NOT in "new bluetooth connect mode", it (correctly) fails to establish a connection; however, rather than showing an error (e.g. "Failed to connect") a duplicate Bose 700 bluetooth device entry is shown. Repeating this process produces more and more duplicate entries.

Steps to reproduce (if you know):

1. Turn on a Bose 700 headset
2. Go to Settings/Bluetooth and see the "LE-Bose NC 700 HP" entry
3. Click the "LE-Bose NC 700 HP" entry
4. No connection is established, and an additional "LE-Bose NC 700 HP" entry is added to the list (there are now 2 "LE-Bose NC 700 HP" entries.)

Expected behavior:

What I would expect to happen is that an error message (or ideally--instructions!) would pop up and tell me what I'm doing wrong so I can correct it. Also, duplicate device entries made it additionally confusing.

Other Notes:

I did finally discover that the cause of the issue was that I had not held down the "bluetooth connect" button on my headset, and so the attempts to connect were failing.

[Aaron-Hartwig]

I hit the same thing today with the same headset.

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os