I see this problem when I am running Calibre and connect a Kindle Fire.
The Fire shows up as a mounted device in Nautilus, but has nothing on it
(which is wrong). Errors from both dmesg and Calibre imply that the
problem may be related to libusb_claim_interface()
dmesg shows:
[149203.958526] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[149204.107572] usb 1-1: New USB device found, idVendor=1949, idProduct=00f1
[149204.107582] usb 1-1: New USB device strings: Mfr=2, Product=3,
SerialNumber=4
[149204.107589] usb 1-1: Product: Fire
[149204.107595] usb 1-1: Manufacturer: Amazon
[149204.107601] usb 1-1: SerialNumber: 00DA080750350787
[149205.439654] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim
interface 0 before use
[149205.567133] usb 1-1: reset high-speed USB device number 6 using xhci_hcd
[149205.715936] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim
interface 0 before use
[149205.716428] usb 1-1: usbfs: process 19851 (events) did not claim interface
0 before use
[149205.716462] usb 1-1: usbfs: process 19851 (events) did not claim interface
0 before use
[149205.716643] usb 1-1: usbfs: process 19851 (events) did not claim interface
0 before use
[149205.717093] usb 1-1: usbfs: process 19822 (DeviceManager) did not claim
interface 0 before use
Calibre output:
Device 0 (VID=1949 and PID=00f1) is UNKNOWN in libmtp v1.1.13.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on
second attempt
Error while trying to open MTPDevice(busnum=1, devnum=5, vendor_id=6473,
product_id=241, bcd=65535, serial=u'00DA080750350787', manufacturer=u'Amazon',
product=u'Fire') (Driver: <calibre.devices.mtp.driver.MTP_DEVICE object at
0x7fa71054b090>)
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/device.py", line 295, in detect_device
dev.open(cd, self.current_library_uuid)
File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 126, in open
BASE.open(self, device, library_uuid)
File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 26, in synchronizer
return func(self, *args, **kwargs)
File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 220, in open
connected_device, as_unicode(e)))
OpenFailed: Failed to open MTPDevice(busnum=1, devnum=5, vendor_id=6473,
product_id=241, bcd=65535, serial=u'00DA080750350787', manufacturer=u'Amazon',
product=u'Fire'): Error: Unable to open MTP device with busnum=1 and devnum=5,
tried 1 such devices
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1792085
Title:
MTP not working/very slow on Bionic
Status in libmtp:
New
Status in gvfs package in Ubuntu:
Incomplete
Bug description:
Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
18.04.
I have used MTP on 16.04 without problems, but on 18.04 it does not
work. When I connect my Android devices (Samsung A5 and Samsung J3)
and I try to list directories with many files (e.g. /DCIM/Camera) the
window hangs until I disconnect the device. Same issue if I try to
post the command "ls /var/run/1000/gvfs/<MTP-FOLDER>".
I have installed Ubuntu 18.04 on two different machines - an older HP
laptop and a recent DELL laptop - and the issue is present on the all
of them.
I suspect a defect on the "libmtp". I tried many alternative solutions
suggested by the net (e.g. jmtpfs and so on) but anyone worked.
That's all!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-fuse 1.36.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 12 06:20:07 2018
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp