Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
crvigh opened this issue Jan 11, 2020 · 6 comments

Comments

@crvigh
Copy link

crvigh commented Jan 11, 2020

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

@Minabsapi
Copy link

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

@maeseee
Copy link

maeseee commented Sep 1, 2020

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

@maeseee
Copy link

maeseee commented Sep 2, 2020

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)

@OlivierV78
Copy link

OlivierV78 commented Dec 19, 2020

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.

@rathann
Copy link

rathann commented Jan 8, 2021

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

@seriousramius
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants