From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220682] New: Bluetooth adapter (MediaTek MT7925, USB ID 0489:e111) stops working after user logs in to the GNOME
Date: Sat, 18 Oct 2025 17:50:30 +0000 [thread overview]
Message-ID: <bug-220682-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220682
Bug ID: 220682
Summary: Bluetooth adapter (MediaTek MT7925, USB ID 0489:e111)
stops working after user logs in to the GNOME
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: alex.jakimov@gmail.com
Regression: No
Created attachment 308826
--> https://bugzilla.kernel.org/attachment.cgi?id=308826&action=edit
Logs
Bluetooth adapter (MediaTek MT7925, USB ID 0489:e111) stops working after user
logs in to the GNOME desktop on a Lenovo Yoga Pro 7 running Fedora 42. The
problem is timing-sensitive and appears to be caused by a software-level
conflict, as the hardware works correctly on Windows 11. Attempts to resolve
the issue with standard workarounds, including kernel module reloading via
systemd and udev, adjusting kernel parameters with GRUB
(btusb.enable_autosuspend=0), and configuring power management with TLP, have
failed. Logs show the bluetooth.target being stopped post-login and reveal
potential communication errors (ACL packet for unknown connection handle).
Relevant log entries
1. Hardware identification via lsusb:
text
Bus 003 Device 002: ID 0489:e111 Foxconn / Hon Hai Wireless_Device
Use code with caution.
2. Kernel and boot environment:
text
uname -r
6.14.0-63.fc42.x86_6
GRUB_CMDLINE_LINUX="rhgb quiet btusb.enable_autosuspend=0"
Use code with caution.
3. Initial successful bluetoothd startup (post-login failure):
text
Oct 18 20:31:29 fedora kernel: Bluetooth: MGMT ver 1.23
Oct 18 20:31:29 fedora bluetoothd[2491]: Battery Provider Manager created
Oct 18 20:31:29 fedora kernel: hid-generic 0005:046D:B035.0002: input,hidraw1:
BLUETOOTH HID v0.06 Mouse [MX Master 3S B] on 84:9e:56:33:6b:2a
Oct 18 20:31:34 fedora kernel: hid-generic 0005:046D:B369.0003: input,hidraw2:
BLUETOOTH HID v0.16 Keyboard [MX Keys Mini] on 84:9e:56:33:6b:2a
Oct 18 20:31:45 2a01-5a8-301-815b--1009.v6.vivacom.bg kernel: Bluetooth: RFCOMM
TTY layer initialized
Oct 18 20:31:54 2a01-5a8-301-815b--1009.v6.vivacom.bg systemd[1]: Stopped
target bluetooth.target - Bluetooth Support.
Use code with caution.
4. ACL packet error showing low-level communication issue:
text
Oct 18 20:31:30 fedora kernel: Bluetooth: hci0: ACL packet for unknown
connection handle 3837
Use code with caution.
5. Corrected module reload fails, showing btmtk is not the right module for
this device:
text
Oct 18 20:23:29 2a01-5a8-301-815b--1009.v6.vivacom.bg kernel: usbcore:
deregistering interface driver btusb
Oct 18 20:23:29 2a01-5a8-301-815b--1009.v6.vivacom.bg kernel: btusb: unknown
parameter 'btmtk' ignored
Oct 18 20:23:29 2a01-5a8-301-815b--1009.v6.vivacom.bg kernel: usbcore:
registered new interface driver btusb
Use code with caution.
Steps to reproduce
Boot Fedora 42 on the Lenovo Yoga Pro 7.
Log in to the GNOME desktop.
Observe that the Bluetooth adapter disappears shortly after login.
Run journalctl -b | grep -i "bluetooth" to confirm the bluetooth.target was
stopped and the ACL packet for unknown connection handle error is present.
--
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-10-18 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 17:50 bugzilla-daemon [this message]
2025-10-18 17:52 ` [Bug 220682] Bluetooth adapter (MediaTek MT7925, USB ID 0489:e111) stops working after user logs in to the GNOME bugzilla-daemon
2025-10-18 17:53 ` bugzilla-daemon
2025-10-20 14:16 ` bugzilla-daemon
2026-01-07 9:43 ` bugzilla-daemon
2026-01-16 12:52 ` bugzilla-daemon
2026-01-16 12:55 ` 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-220682-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox