Bug 2392938 - MTP Wireless device detected in Lenovo Legion Pro 5 laptop from 2025
Summary: MTP Wireless device detected in Lenovo Legion Pro 5 laptop from 2025
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libmtp
Version: 42
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Linus Walleij
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-03 18:01 UTC by Jakub Jankiewicz
Modified: 2025-11-14 20:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
outout of sudo lsusb -v (61.62 KB, text/plain)
2025-09-03 18:01 UTC, Jakub Jankiewicz
no flags Details

Description Jakub Jankiewicz 2025-09-03 18:01:10 UTC
Created attachment 2105674 [details]
outout of sudo lsusb -v

Created attachment 2105674 [details]
outout of sudo lsusb -v

Description of problem:

I have a new laptop Lenovo Legion Pro 5 16IAX10 Ultra 7 255HX from 2025.
Fedora (xfce spin) detects one of the system devices as MTP showing Wireless Device on desktop. When you try to connect to it, bluetooth stops working.

Note that I used Grok to help me with debugging and trying different things.
It started when I asked about /etc/udev/rules.d directory to explain what it was.

We tried to disable MTP using the rules, we thought that the problematic was Foxconn / Hon Hai Wireless_Device that have Wireless_Device in the name. But with no success. The icon was still visible on the desktop even when adding:

(NOTE: identifiers from lsusb added later)

ATTR{idVendor}=="0489", ATTR{idProduct}=="e111", GOTO="libmtp_rules_end"

To this file:

/usr/lib/udev/rules.d/69-libmtp.rules

Here are output of few commands in terminal:

$ gio mount -l
...
Volume(0): Wireless Device
  Type: GProxyVolume (GProxyVolumeMonitorMTP)


This is the output of:

journalctl -xe | grep -i mtp

wrz 03 19:21:53 jcubic systemd[2065]: Starting gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor...
wrz 03 19:21:53 jcubic systemd[2065]: Started gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor.

here is the output of mtp-detect 

libmtp version: 1.1.19
Listing raw device(s)
Device 0 (VID=0489 and PID=e111) is a Vizio (for Lenovo) LIFETAB S9714.
   Found 1 device(s):
   Vizio (for Lenovo): LIFETAB S9714 (0489:e111) @ bus 3, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

After message Attempt to reset device it frozen for about a minute or longer.
It required to remove and add the bluetooth kernel module for the Bluetooth to work again.

And this is output of lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 17ef:f006 Lenovo Idea5003
Bus 003 Device 003: ID 048d:c195 Integrated Technology Express, Inc. ITE Device(8258)
Bus 003 Device 004: ID 046d:c542 Logitech, Inc. M185 compact wireless mouse
Bus 003 Device 005: ID 174f:11b5 Syntek Integrated Camera
Bus 003 Device 006: ID 0489:e111 Foxconn / Hon Hai Wireless_Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Adding lsusb -v as attachment.

Let me know if this something with Fedora or a Kernel issue.

Comment 1 Jakub Jankiewicz 2025-11-14 20:09:25 UTC
I've reported the bug to the Linux Kernel

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

and someone have found a repository with a hack that can be used to hide invalid MTP device:

https://github.com/LuanAdemi/mediatek7925e-bluetooth-fix

You may want to investigate how it was fixed, to add a proper fix.

They updated two system udev files that had invalid identifier.

Comment 2 Jakub Jankiewicz 2025-11-14 20:10:31 UTC
They just fixed the issue with Fedora 43


Note You need to log in before you can comment on or make changes to this bug.