Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218952] bluetooth and wireplumber stop working after some time - dmesg report BUG
Date: Wed, 08 Jul 2026 12:58:35 +0000	[thread overview]
Message-ID: <bug-218952-62941-yUUMWyzL4H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218952-62941@https.bugzilla.kernel.org/>

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

--- Comment #8 from Nicolas BARANGER (nicolas.baranger@3xo.fr) ---
Hi  

I'm sorry I cannot confirm or infirm as I don't have the affected hardware
anymore, but I can confirm I don't have this issue on my 2 new Dell laptops:  


- Dell Precision 3590  
- Dell ProMax 16    

And XPS15 7590 is not affected (not XPS 9570 which was affected).    


Please note that it could be hardware / firmware related as I had a similar
issue a few months ago on Win11 Enterprise edition installed on one partition
of my corporate Dell ProMax 16, and it had beed fixed by Dell Support Assist
firmware update (in the meantime I didn't constat this issue while using Debian
13 on this laptop)   


Maybe @martin@hignett.net still have the hardware to test...     

Regards
Nicolas

-- 
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:[~2026-07-08 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  6:21 [Bug 218952] New: bluetooth and wireplumber stop working after some time - dmesg report BUG bugzilla-daemon
2024-06-11  7:21 ` [Bug 218952] " bugzilla-daemon
2024-06-11 17:10 ` bugzilla-daemon
2024-08-08 11:36 ` bugzilla-daemon
2024-11-06  8:58 ` bugzilla-daemon
2025-07-11 14:58 ` bugzilla-daemon
2025-07-11 15:01 ` bugzilla-daemon
2026-07-08  8:33 ` bugzilla-daemon
2026-07-08 12:58 ` bugzilla-daemon [this message]
2026-07-08 18:43 ` 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-218952-62941-yUUMWyzL4H@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