From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219385] BT mouse can not be found and/or connected in 6.12-rc3
Date: Mon, 14 Oct 2024 08:30:36 +0000 [thread overview]
Message-ID: <bug-219385-62941-A0LuROcb0y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219385-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219385
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de,
| |regressions@leemhuis.info
--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Mark, thank you for the report. There are two more reports on the list with the
same findings as you:
1. Connection issue since 81b3e33bb054 ("Bluetooth: btusb: Don't fail external
suspend requests")
2. Commit 610712298b11 ("btusb: Don't fail external suspend requests") breaks
BT upon resume on my laptop
I think, the plan is to revert the commit.
[1]:
https://lore.kernel.org/linux-bluetooth/020c69d7-ad86-44d3-a508-22ff949ee7ec@gmail.com/T/#t
[2]:
https://lore.kernel.org/linux-bluetooth/a34d2761-dad4-4ae7-8787-6bbf05538318@panix.com/T/#t
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-10-14 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 8:19 [Bug 219385] New: BT mouse can not be found and/or connected in 6.12-rc3 bugzilla-daemon
2024-10-14 8:30 ` bugzilla-daemon [this message]
2024-10-15 15:34 ` [Bug 219385] " bugzilla-daemon
2024-10-17 23:51 ` bugzilla-daemon
2024-10-18 1:37 ` bugzilla-daemon
2024-10-19 12:36 ` bugzilla-daemon
2024-10-20 2:14 ` bugzilla-daemon
2024-10-24 9:09 ` 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-219385-62941-A0LuROcb0y@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