From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219854] New: Bluetooth devices can't connect after toggling Bluetooth unless they are re-paired
Date: Sun, 09 Mar 2025 17:48:57 +0000 [thread overview]
Message-ID: <bug-219854-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219854
Bug ID: 219854
Summary: Bluetooth devices can't connect after toggling
Bluetooth unless they are re-paired
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: linux-bugzilla@ericswpark.com
Regression: No
Created attachment 307785
--> https://bugzilla.kernel.org/attachment.cgi?id=307785&action=edit
dmesg output on Linux Mint during reproduction of bug
I noticed that my Bluetooth headsets would fail to reconnect to my NixOS laptop
running `6.13.5` if I toggled (disable -> enable) the BT module. When this
occurs, attempting to connect again via KDE's Bluetooth panel (or the Cinnamon
BT applet in case of Linux Mint) would fail with a "Connection Failed" error.
The only way to fix this is to unpair the devices, then re-pair them and
connect to them again. Then BT will continue to work until the module is
toggled and/or the laptop enters sleep (I guess the module gets power-cycled
during sleep).
Under Windows this does not occur. On a live Linux Mint boot running kernel
`6.8.0-51-generic` the same issue occurs. I am not sure if this is a regression
or not as I have not tested earlier versions of the kernel.
Attached `dmesg` output from the Linux Mint reproduction, after toggling the
module on and attempting to connect to the previously paired device.
I also posted about this on the NixOS forums here
(https://discourse.nixos.org/t/cant-reconnect-to-paired-bluetooth-devices-after-toggling-bt-unless-i-re-pair/61366)
and that post contains some screenshots of the issue occurring on KDE, as well
as `dmesg` output from the NixOS system (which seems to be more sparse compared
to the Linux Mint output).
This was tested on a ThinkPad T480 running the Intel Corporation Wireless 8265
/ 8275 (rev 78) card, on NixOS-unstable `6.13.5`. I tested two headsets (Buds2
Pro / Sony WH-1000XM5) and they both "fail" in the same way.
--
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:[~2025-03-09 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 17:48 bugzilla-daemon [this message]
2025-04-16 20:29 ` [Bug 219854] Bluetooth devices can't connect after toggling Bluetooth unless they are re-paired bugzilla-daemon
2025-04-16 20:29 ` bugzilla-daemon
2025-04-24 19:35 ` bugzilla-daemon
2025-04-24 20:03 ` 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-219854-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.