From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218264] New: Potential kernel regression with bluetooth pairing on specific radios
Date: Thu, 14 Dec 2023 15:35:26 +0000 [thread overview]
Message-ID: <bug-218264-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218264
Bug ID: 218264
Summary: Potential kernel regression with bluetooth pairing on
specific radios
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: marco.rodolfi@tuta.io
Regression: No
I had a Logitech K480 paired with my Steam Deck (RTL8822CE) from a previous
successful pair on Linux 6.4.x/6.5.x, not sure on the specific version. Since
Fedora updated to 6.6.x and I accidentally lost the pairing key I can't in no
way be able to associate. It connects fine but just fails with
bluez.authenticationfailure. I've opened a bug report in the bluez issues page
https://github.com/bluez/bluez/issues/654 and after testing on another computer
with a different bluetooth radio (RTL8771) + kernel 6.6.5 and bluez 5.70 the
keyboard connected immediately and requiring me to insert the passcode
correctly. I'm writing this from this specific keyboard.
I'm still not sure if it's the kernel driver fault or bluez fault.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-12-14 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:35 bugzilla-daemon [this message]
2023-12-17 7:32 ` [Bug 218264] Potential kernel regression with bluetooth pairing on specific radios bugzilla-daemon
2023-12-17 14:54 ` bugzilla-daemon
2023-12-17 15:51 ` bugzilla-daemon
2023-12-17 18:32 ` bugzilla-daemon
2023-12-21 12:43 ` bugzilla-daemon
2023-12-21 14:12 ` bugzilla-daemon
2024-02-08 16:00 ` bugzilla-daemon
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-218264-62941@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).