From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219514] PC does not resume from suspend, bisect points to btusb/mediatek
Date: Mon, 06 Jan 2025 08:53:05 +0000 [thread overview]
Message-ID: <bug-219514-62941-zRCML3FzjY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219514-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219514
Bojan Kseneman (bojan@kseneman.si) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bojan@kseneman.si
--- Comment #8 from Bojan Kseneman (bojan@kseneman.si) ---
If you also need to kill wifi you should replace the "rfkill block bluetooth"
with "rfkill block all" in the script, it should kill both BT & Wifi
Anyway, I've installed kernel 6.12.8 today and disabled the service and cannot
reproduce this issue anymore. Can someone else also confirm this?
--
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:[~2025-01-06 8:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 19:43 [Bug 219514] New: PC does not resume from suspend, bisect points to btusb/mediatek bugzilla-daemon
2024-11-19 19:45 ` [Bug 219514] " bugzilla-daemon
2024-12-15 21:06 ` bugzilla-daemon
2024-12-15 21:14 ` [Bug,219514] " bluez.test.bot
2024-12-30 19:22 ` [Bug 219514] " bugzilla-daemon
2025-01-02 23:55 ` bugzilla-daemon
2025-01-04 5:36 ` bugzilla-daemon
2025-01-04 6:48 ` bugzilla-daemon
2025-01-04 15:27 ` bugzilla-daemon
2025-01-06 8:53 ` bugzilla-daemon [this message]
2025-01-06 10:18 ` bugzilla-daemon
2025-01-06 13:09 ` bugzilla-daemon
2025-01-06 14:41 ` bugzilla-daemon
2025-01-07 9:05 ` bugzilla-daemon
2025-01-07 21:02 ` bugzilla-daemon
2025-01-09 18:15 ` bugzilla-daemon
2025-02-07 21:22 ` bugzilla-daemon
2025-02-07 21:24 ` bugzilla-daemon
2025-02-17 15:22 ` bugzilla-daemon
2025-02-17 15:27 ` 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-219514-62941-zRCML3FzjY@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.