Menu
▾
▴
#1818 Moto G regrerssion: -6LIBMTP PANIC: Unable to initialize device
After upgrade to Fedora 29 with libmtp 1.1.16 (from Fedora 27 with 1.1.14) it's no longer possible to transfer files from Moto G 1st Gen using gvfs:
gvfsd[1822]: error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
gvfsd[1822]: Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
(...)
gvfsd[1822]: LIBMTP PANIC: could not inspect object property descriptions!
mtp-detect returns:
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
Found 1 device(s):
Motorola: Moto G (ID2) (22b8:2e82) @ bus 2, dev 5
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
On Fedora 27 with libmtp 1.1.14 it worked without any problem.
Discussion
Anonymous
When downgraded to libmtp 1.1.14 also on Fedora 29 it works as well.
Last edit: Marcin Zajaczkowski 2018-12-15
Same problem with idVendor=2a47, idProduct=2008 (Aquaris_E5_HD) (and some older Huawei Android phone I don't have Id's now) on Debian after 1.1.13->1.1.16 upgrade. Downgrading to 1.1.13 fixes issue.
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921559
This is bad output:
This is OK output:
This is bad mtp-detect output with 1.1.6 for Huawei Y330-U01 with Android 4.2.2:
And this is OK output with 1.1.3:
Hi,
I have the same problem with my Samsung Galaxy A3, Debian and the MATE desktop.
Regards.
$ sudo mtp-detect
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
similar problem with 1.1.16; 1.1.13 works.
No idea what the new version could change there ...
Perhaps gvfs conflicts ? Is the device working in Nautilus File Manager?
Intrestingly, it works now with latest Debian Sid.
I get the same problem with an Oukitel C5 (chinese cheap brand), but sometimes it works. Don'tknw what changes to make it work, but I did have a half connected USB plug once and itjust wont wrk now (even though it's now properly connected).
Phone rebooted still doesn't work.
It;s like libmtp or the USB hub gets itself into a broken state and won't reset out of it.
This is the Oukitel C6
Also for the Oukitel (obvious bogus serial number) :)
Oukitel lshw output
on my laptop (Oukitel)
Oukitel: can confirm downgrading to libmtp9 (1.1.13-1) works
Fixed for me on libmtp 1.1.16 by adding my user to the uucp group per https://wiki.archlinux.org/index.php/Media_Transfer_Protocol#libmtp
LXDE Spin Fedora 31 with manually compiled and installed 1.1.17. PCManFM will mount this but it's not usable. When I also plug in my phone I get that error and Calibre will not connect. When I unmount it Calibre connects and I can store, retrieve and delete books. mtp-detect also works when prior to that it will not.
LXDE Spin Fedora 31 with manually compiled and installed 1.1.17. PCManFM will mount this but it's not usable. When I also plug in my phone I get that error and Calibre will not connect and mtp-detect squalls that error.
When I unmount it Calibre connects and I can use all features OR I can run mtp-detect. It appears I can only have one thing connected at a time.
I thought I was logged in, the anonymous posting can go away.
LXDE Spin Fedora 31 with manually compiled and installed 1.1.17. PCManFM will mount this but it's not usable. When I also plug in my phone I get that error and Calibre will not connect and mtp-detect squalls that error.
When I unmount it Calibre connects and I can use all features OR I can run mtp-detect. It appears I can only have one thing connected at a time.
I thought I was logged in, the anonymous posting can go away.
In my case: Debian Buster with XFCE and the stock libmtp 1.1.16-2, Nokia 3.2 with Android 10. Couldn't seem to make MTP-based tools work. I found out that it's appropriate to tell the support for MTP in Thunar to disconnect from the phone, while trying mtp-detect et al - but still "Get storage information failed".
Solution: it took quite a bit of focused sniffing around to find out, that indeed THE PHONE LIKELY DOES NOT MAKE ANY DATA AVAILABLE. All my adult life I keep rejecting fondleslabs, so I merely know Android exists. I've been aware of the historical choice in telephone config, what protocol suite should be used to present data to the PC on the USB cable. I've been aware that the old-skool USB Mass Storage mode is out - and as a Linux-based storage admin, I know exactly why. I kept stumbling over howto guides that were out of date for Android 10. Because in Android 10, apparently "there's no such thing anymore". Or is there? Oh yes there is! You're just not expected to configure this as a mere mortal. The default USB properties were configured for "no transfer" - period. My own son kept telling me "just send the photoes by e-mail, silly old man". Naah... who's silly here. Heh you need to search for hints about easter eggs to get to the choice "PTP" or "file transfer". Along the way, you have to enter developer mode for christ sake... Either PTP or "file transfer" works in Debian 10 XFCE with mtp 1.1.16-2 out of the box! The old PTP will only show you the photoes, won't work with MTP-tools (namely mtp-detect). The "file transfer" option will show you pretty much the whole directory tree in the phone.
Hell... now I just need to calm down a bit. Gotta keep an eye on my blood pressure.
In the default setting (no transfer), the phone did respond to mtp-detect, but did not divulge any useful data... maybe it's trying some auto-detection/decision/heuristic, what to switch on? Maybe there's a more modern PnP explicit way that the libmtp does not know yet? Whatever...
Someone with a login, please report this to this debian bug report .