From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219898] BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt
Date: Thu, 20 Mar 2025 21:09:57 +0000 [thread overview]
Message-ID: <bug-219898-62941-vsJIJx4pTj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219898-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219898
--- Comment #8 from Hunter M (miller.hunterc@gmail.com) ---
After further testing, issue does occur utilizing bluetoothctl as well. On the
first Pair attempt, org.bluez.Error.AuthenticationCanceled occurs.
On the second attempt, pairing is successful.
This issue can be duplicated by removing the /var/lib/bluetooth/<adapter
address>/<remote device address>/ folder and restarting the bluetooth.service
(systemctl restart bluetooth).
Seems that without the cached attributes/info, this issue arises. However, if
the BLE peripheral attributes/info is stored in /var/lib/bluetooth/<adapter
address>/<remote device address>/ folder, the issue does not occur.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2025-03-20 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 14:51 [Bug 219898] New: BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt (utilizing software-controlled bluez API via Dbus) bugzilla-daemon
2025-03-19 14:53 ` [Bug 219898] " bugzilla-daemon
2025-03-19 14:55 ` bugzilla-daemon
2025-03-19 14:56 ` bugzilla-daemon
2025-03-19 15:02 ` bugzilla-daemon
2025-03-20 20:22 ` bugzilla-daemon
2025-03-20 20:23 ` bugzilla-daemon
2025-03-20 20:41 ` [Bug 219898] BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt bugzilla-daemon
2025-03-20 21:09 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219898-62941-vsJIJx4pTj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).