Description of problem: libmtp gets an error while browsing some folders in Nautilus on a Samsung Android device connected by USB Bug 1225601 (F22) is exactly the same and still present in Fedora 24, I am not able to reopen it there, so I am opening it here. Version-Release number of selected component (if applicable): $ rpm -q libmtp libmtp-1.1.11-1.fc24.x86_64 How reproducible: Steps to Reproduce: 1. Connect my MTP device to USB 2. Browse to the SDCard/DCIM/Camera Folder on Nautilus 3. Wait for the folder content to display Actual results: A dialog pops out saying "This location could not be displayed. Sorry, could not display all the contents of “Camera”: libmtp error: could not get object handles." Expected results: Files contained in the folder are displayed Additional info: does not happen on all folders, maybe only on crowded ones (timeout problem?)
I'm also having the same problem. Wondering if it's an libmtp problem.
Having the same problem on F25. I was able to read the contents of my 128GB SD card and copy music files over to it when it was empty. But as I was copying, I got a copy error and now I'm getting the Nautilus popup error "libmtp error: could not get object handles.." libmtp-1.1.11-1.fc25.x86_64
I'm getting the same error on a 16GB SD card. This is with a Samsung S2 Tablet.
This error is not Nautilus dependent. It happens with the caja file browser from the Mate desktop as well as the thunar file browser. Whenever I try to copy this one directory of music files from my mtp device to my F25 system it fails with "libmpt: could not get object handles".
Still present in Fedora 25 libmtp-1.1.13-1.fc25.x86_64
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
libmtp-1.1.14-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2178545be6
libmtp-1.1.14-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-1ed1cb828f
libmtp-1.1.14-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-1ed1cb828f
libmtp-1.1.14-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2178545be6
libmtp-1.1.14-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
libmtp-1.1.14-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Fedora Update System from comment #11) > libmtp-1.1.14-1.fc26 has been pushed to the Fedora 26 stable repository. If > problems still persist, please make note of it in this bug report. Reopening against F26 because still happens with 1.1.14-1.fc26 (folder with 124 files inside)
I can point out that after deleting 4 files the problem seems to be gone.
After a few other tries, I found out that the problem triggers if the folder contains 124 items, but does not if there are 123 files inside. The total size for the 123 files is 24.6 MB. The 124th file is 74.3 kB sized.
Happens to me too after upgrading to F27. F26 worked fine, same phone, less than 20 files in a folder. libmtp-1.1.14-1.fc27.x86_64 gvfs-mtp.x86_64 1.34.1-1.fc27 Steps to Reproduce: 1. plugin unlocked Android phone via USB 2. get prompted on phone to use USB transfer files, accept 3. "Android" appears in Nautilus 4. click on it to mount Actual results: spins for 10-30 seconds, then shows Folder is empty Expected results: show "Internal Storage" drive, as it used to work in Fedora 26 (same phone, Nokia 5) Additional info: 850.682469] usb 3-2: new high-speed USB device number 6 using xhci_hcd [ 850.809948] usb 3-2: New USB device found, idVendor=2e04, idProduct=c025 [ 850.809952] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 850.809955] usb 3-2: Product: Android [ 850.809957] usb 3-2: Manufacturer: Android [ 850.809959] usb 3-2: SerialNumber: D1AGAD1762440107 [ 850.812560] usb-storage 3-2:1.1: USB Mass Storage device detected [ 850.812875] scsi host4: usb-storage 3-2:1.1 [ 851.844406] scsi 4:0:0:0: CD-ROM Linux File-CD Gadget 0318 PQ: 0 ANSI: 2 [ 851.846412] sr 4:0:0:0: [sr1] scsi-1 drive [ 851.846747] sr 4:0:0:0: Attached scsi CD-ROM sr1 [ 851.846892] sr 4:0:0:0: Attached scsi generic sg2 type 5 Looks like this is a different bug?
Perhaps someone shall forward this to the upstream libmtp? Looks like the 126 files limit is related to some hard coded constants in the driver, and can be an clean if not easy fix.
(In reply to Feng Yu from comment #17) > Perhaps someone shall forward this to the upstream libmtp? > > Looks like the 126 files limit is related to some hard coded constants in > the driver, and can be an clean if not easy fix. (btw, it's 123 file limit, not 126) I have contacted libmtp mailing list: https://sourceforge.net/p/libmtp/mailman/message/36314380/ I am trying to help someway, but my experience is poor.
(still affects current upstream libmtp-1.1.15)
upstream bug: https://sourceforge.net/p/libmtp/bugs/1808/
libmtp-1.1.16-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-bb02c4e8d6
libmtp-1.1.16-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-bb02c4e8d6
libmtp-1.1.16-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
it looks like, problem still persist for Fedora 29 libmtp-1.1.16-1.fc29.x86_64 4.19.6-300.fc29.x86_64. cat /etc/fuse.conf mount_max = 20000 user_allow_other