Bug 1225601

Summary:	libmtp error: could not get object handles for some directories
Product:	[Fedora] Fedora	Reporter:	Roland Roberts <roland>
Component:	libmtp	Assignee:	Linus Walleij <triad>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	andrea.vai, gregab, jcoscia, triad, twaugh
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 19:35:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roland Roberts 2015-05-27 18:41:26 UTC

Description of problem:

About two weeks ago, I was able to keep my Samsung Note 10.1 2014 book collection up-to-date using Calibre. Today, I attempted to update it and found Calibre showed me having no books on the device, something I know to be false.

I attempted to browse the device using Nautilus and can see directories and contents, so far on everything I've tried *except* the Books directory. For that, after a long delay, I get an error:

This location could not be displayed.
Sorry, could not display all the contents of “Books”: libmtp error: could not get object handles.

I have used a directory browser on the device to read the directory contents without any issues.

Version-Release number of selected component (if applicable):

2035 roland> uname -a
Linux airy.rlent.pnet 3.19.7-200.fc21.x86_64 #1 SMP Thu May 7 22:00:21 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
2036 roland> lsusb
Bus 004 Device 005: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 004 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 004 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 004 Device 007: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 003 Device 004: ID 05e3:070e Genesys Logic, Inc. USB 2.0 Card Reader
Bus 003 Device 003: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
2037 roland> rpm -q libmtp
libmtp-1.1.8-1.fc21.x86_64

How reproducible:

Steps to Reproduce:
1. Plug in Samsung Note 10.1 2014 (P-605)
2. Open device in Nautlius
3. Try to open Books directory

Actual results:

Error dialog reading

This location could not be displayed.
Sorry, could not display all the contents of “Books”: libmtp error: could not get object handles.

Expected results:

Display of directory contents

Additional info:

Comment 1 Tim Waugh 2015-10-29 17:37:45 UTC

I see the same with F-22, libmtp-1.1.9-1.fc22.x86_64, with a Samsung Galaxy S5.

Comment 2 Grega Bremec 2016-07-05 12:39:56 UTC

Same here, but on RHEL Workstation 7.2 with:
 - libmtp-1.1.6-3.el7.x86_64
 - gvfs-mtp-1.22.4-6.el7.x86_64
 - gvfs-fuse-1.22.4-6.el7.x86_64
 - fuse-2.9.2-6.el7.x86_64
 - fuse-libs-2.9.2-6.el7.x86_64

Action:
 - I was able to browse and copy files using Nautilus as recently as two days ago
 - browsing the DCIM folder on my phone w/ 1404 files named yyyymmdd_HHMMSS.jpg (nothing out of the ordinary, I was able to do this with 10k+ files just fine)
 - no updates, no config changes
 - rebooted the phone, rebooted the laptop, reattempted the action

Symptom:
 - after some seconds of communication, the above libmtp error is reported

Expected result:
 - list of files in that directory

Notes:
 - no other directory exhibits this behaviour
 - the contents can be listed using the file manager on the phone

Comment 3 Fedora End Of Life 2016-07-19 19:35:19 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Grega Bremec 2016-07-19 19:38:09 UTC

Can someone reopen this under RHEL?

Comment 5 Andrea Vai 2016-12-06 08:20:26 UTC

Opened bug 1401826 against Fedora 24, because it's still present there.