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

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

Linus Walleij — Fri, 30 Dec 2022 00:03:12 -0000

Same issue with Samsung A53 (VID=04e8 and PID=6860) on Ubuntu 20.04 and libmtp 1.1.17

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

Marcus Meissner — Mon, 08 Feb 2021 04:52:51 -0000

In Plasma it appears only onr aoolication can have exclusive control of mtp, If Dolphin claims the mount than Cantata or Gwenview for instance, cannot connect. If Cantata has mtp access then the Dolphin file manager will not connect. Unfortunately there is no gui unmount for mtp in plasma. Closing out programs which use mtp and rebooting will allow the user to open the required program for mtp access.

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

Marcus Meissner — Mon, 31 Aug 2020 11:11:05 -0000

error 6 means device already in use by another tool, likely gvfs.
so it actually already mounted by gnome nautilus

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

Marcus Meissner — Tue, 18 Aug 2020 09:25:48 -0000

The same error on ubuntu 20.04 and Samsung Galaxy S10

me@mypc:~$ sudo mtp-detect
libmtp version: 1.1.17

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 12
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.

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

Linus Walleij — Sun, 09 Aug 2020 15:36:27 -0000

The same error on ubuntu 20.04 and Samsung Galaxy A51

root:# mtp-detect
libmtp version: 1.1.17

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 19
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.

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

Linus Walleij — Thu, 16 Jul 2020 15:49:58 -0000

Same issue on current latest Ubuntu (20.04)

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

Marcus Meissner — Sat, 25 Jan 2020 12:09:07 -0000

Fails as root on the latest Fedora.

[root@localhost libexec]# 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 3
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.

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

Marcus Meissner — Sat, 25 Jan 2020 11:17:03 -0000

status: open --> pending
assigned_to: Marcus Meissner

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

Marcus Meissner — Sat, 25 Jan 2020 11:16:42 -0000

probably is permission rela ted. can you test if it works as root , if it does the permissions need to be adjusted. (pending on your distribution)

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

Marcus Meissner — Sat, 25 Jan 2020 08:21:36 -0000

I get the same error with a Samsung A50 (same PID)