Description of problem: Previously working samsung android devices not longer are mountable Version-Release number of selected component (if applicable): libmtp-1.1.18-2.fc34.x86_64 How reproducible: Consistently Steps to Reproduce: 1. run dmesg -w 2. plug android device into usb port 3. See device was recognized by kernel 4. open nautilus 5. click on android device Actual results: Nautilus reports Unable to access "SAMSUNG Android" Unable to open MTP device "001,004" Expected results: See Internal and Card directories Additional info: Same issue is reported when attempting to use gio mount -d '/dev/bus/usb/001/004'
Same issue happens in KDE spin: 1. Plug in Galaxy S9 to USB-C port 2. Following shows up in dmesg: [ 4919.366200] usb 1-1: new high-speed USB device number 4 using xhci_hcd [ 4919.503891] usb 1-1: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= c.00 [ 4919.503906] usb 1-1: New USB device strings: Mfr=7, Product=8, SerialNumber=9 [ 4919.503913] usb 1-1: Product: SAMSUNG_Android [ 4919.503919] usb 1-1: Manufacturer: SAMSUNG [ 4919.503925] usb 1-1: SerialNumber: xxxxxxxxxxx [ 4937.608473] usb 1-1: reset high-speed USB device number 4 using xhci_hcd 3. Ensure following USB options are enabled on phone (probably default): USB controlled by: This phone Use USB for: Transferring files/Android Auto 4. Open Dolphin 5. Click on SAMSUNG_Android in list of devices 6. Following message appears: Top: No storage media found. Make sure your device is unlocked and has MTP enabled in its USB connection settings. main section: No MTP-compatible devices found 7. No errors show up in dmesg
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.