error returned by libusb_claim_interface() = -6 LIBMTP PANIC: Unable to initialize device

Question

error returned by libusb_claim_interface() = -6 LIBMTP PANIC: Unable to initialize device

Opened this issue 5 years ago · 7 comments

sid@unstable:~$ jmtpfs /tmp/android
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
  what():  Can't open device
Aborted (core dumped)

sid@unstable:~$ jmtpfs -l
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Available devices (busLocation, devNum, productId, vendorId, product, vendor):
1, 14, 0x6860, 0x04e8, Galaxy models (MTP), Samsung

version: 0.5-2+b2
OS: Latest Debian unstable / sid
Device: Samsung Galaxy S10

Answer 1 · 2020-07-16T15:43:32.000Z

Same issue.

jmtpfs version: 0.5
FUSE library version: 2.9.9
fusermount version: 2.9.9
using FUSE kernel interface version 7.19

OS: GNU/Linux Ubuntu 20.04
Device: Xiaomi Mi A1

Answer 2 · 2020-09-01T18:37:08.000Z

Same issue here:

Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device

OS: Kubuntu 20.04
jmtpfs version: 0.5
FUSE library version: 2.9.9
fusermount version: 2.9.9
using FUSE kernel interface version 7.19

Answer 3 · 2020-09-02T12:36:29.000Z

The problem was when I try to open the phone with Dolphin before, so jmtpfs could not access it anymore. The GPhoto2 instance of the KIOslave driver is using it. This is a bug of the KIO module. See DigiKamBug.

For me the command sudo killall kiod5 solved the problem. On other os than Kubuntu, another service must be killed (e.g. gvfsd-mtp for ubuntu)

Answer 4 · 2020-12-19T18:35:18.000Z

Same issue for me.

EDIT : I is only necessary to say "yes" when authorization is asked from the phone and then only connect to dolphin.
No problem anymore.

Answer 5 · 2021-01-08T10:49:37.000Z

Same issue in GNOME or MATE or even without those. jmtpfs crashes if the device is mounted already by anything else (including itself):

$ mkdir /tmp/Samsung
$ jmtpfs /tmp/Samsung
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
$ mount |grep jmtp
jmtpfs on /tmp/Samsung type fuse.jmtpfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
$ jmtpfs 
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
  what():  Can't open device
Aborted (core dumped)
$ umount /tmp/Samsung
$ jmtpfs 
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
fuse: missing mountpoint parameter
$ jmtpfs --version
jmtpfs version: 0.5
FUSE library version: 2.9.9
fusermount version: 2.9.9
using FUSE kernel interface version 7.19

Answer 6 · 2023-12-16T18:52:42.000Z

I got the same error with the xiaomi redmi 8. It occured since i installed the konqueror with konq-plugins. Killing the process kiod5 doesn't help. So i uninstalled the konq-plugins and i was able to mount the filesystem via caja. OS is Debian 12

Answer 7 · 2024-07-18T19:52:45.000Z

With GNOME, you may encounter problems due to GVfs (GVfs is a userspace virtual filesystem implementation for GIO, a library available in GLib). Try the following command: ps aux | grep gvfs and then kill all processes using their PID.