All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219854] Bluetooth devices can't connect after toggling Bluetooth unless they are re-paired
Date: Thu, 24 Apr 2025 19:35:29 +0000	[thread overview]
Message-ID: <bug-219854-62941-ap4F5XCRB5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219854-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219854

Eric Park (linux-bugzilla@ericswpark.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |UNREPRODUCIBLE

--- Comment #2 from Eric Park (linux-bugzilla@ericswpark.com) ---
I tried different kernel versions today to see if this was a regression, but
after changing through kernels 5.15.x, 6.1.x, 6.12.21, and 6.13.9, I was unable
to reproduce the issue. In fact, after switching back to the latest kernel
version available on NixOS (6.14.0) the same two headsets that I used continue
to connect properly, even when toggling Bluetooth power and suspending the
entire laptop. Closing as the bug cannot be reproduced anymore.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2025-04-24 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09 17:48 [Bug 219854] New: Bluetooth devices can't connect after toggling Bluetooth unless they are re-paired bugzilla-daemon
2025-04-16 20:29 ` [Bug 219854] " bugzilla-daemon
2025-04-16 20:29 ` bugzilla-daemon
2025-04-24 19:35 ` bugzilla-daemon [this message]
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-ap4F5XCRB5@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.