Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
Hi I had a similar issue. Turns out that Gnome's gvfs was locking the mtp device. Since I run KDE, I've removed gvfs-backends package and rebooted. I now can run mtp-detect without issue. HTH
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
Thanks. I also got this error on a new computer, running NixOs 20.03, and on a completely different phone, a Samsung A 40: [nix-shell:~]$ 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 124 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK. I also tried "android-file-transfer", and when I kill the process that is using the device, it does work. Can I help somehow? Cheers, Léo
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
Hi, I am really annoyed by this issue! It seems to be present in other distrib at least in Fedora but I am not able to reproduce... I have no problem with my android phones. Le ven. 19 juin 2020 à 11:51, Tobias Bora a écrit : > > I can confirm the bug also with libmtp9 1.1.17 and a Samsung Galaxy A3 > (2015, A300FU). Is there at least meanwhile a solution independant of > libmtp and a bit faster than installing a FTP server on my phone? You can try to use "android-file-transfer" (available in Debian repo), it should work because it doesn't use libmtp. Best, Dylan
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
I can confirm the bug also with libmtp9 1.1.17 and a Samsung Galaxy A3 (2015, A300FU). Is there at least meanwhile a solution independant of libmtp and a bit faster than installing a FTP server on my phone? $ sudo apt-cache policy libmtp9 libmtp9: Installé : 1.1.17-3 Candidat : 1.1.17-3 Table de version : *** 1.1.17-3 500 500 http://ftp.fr.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status $ 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 2, dev 8 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK.
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
On Thu, 5 Sep 2019 21:49:41 +0200 Eric Van Buggenhaut wrote: On Sun, 4 Aug 2019 18:59:34 +0300 Vincas Dargis wrote: > On Thu, 11 Apr 2019 09:20:01 +0200 Erwan David wrote: > > Same problem with a Huawei P9 Lite (2017) > > My problems are fixed now with libmtp 1.1.16 on Sid. Does it work now for you too? > > I'm experiencing the same problem with libmtp 1.1.16 on Buster: $ mtp-detect libmtp version: 1.1.16 Listing raw device(s) Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB). Found 1 device(s): Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 38 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK. Getting identical problems using libmtp 1.1.16 on Fedora with Huawei Honor 5 ( which is called Ascend P8 according to ProdID ) mtp-detect libmtp version: 1.1.16 Listing raw device(s) Device 0 (VID=12d1 and PID=1082) is a Huawei Ascend P8. Found 1 device(s): Huawei: Ascend P8 (12d1:1082) @ bus 2, 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.
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
On Sun, 4 Aug 2019 18:59:34 +0300 Vincas Dargis wrote: > On Thu, 11 Apr 2019 09:20:01 +0200 Erwan David wrote: > > Same problem with a Huawei P9 Lite (2017) > > My problems are fixed now with libmtp 1.1.16 on Sid. Does it work now for you too? > > I'm experiencing the same problem with libmtp 1.1.16 on Buster: $ mtp-detect libmtp version: 1.1.16 Listing raw device(s) Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB). Found 1 device(s): Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 38 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK.
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
On Thu, 11 Apr 2019 09:20:01 +0200 Erwan David wrote: Same problem with a Huawei P9 Lite (2017) My problems are fixed now with libmtp 1.1.16 on Sid. Does it work now for you too?
Bug#921559: MTP broken for number of phones with "LIBMTP PANIC: Unable to initialize device"
Package: libmtp9 Version: 1.1.16-2 Followup-For: Bug #921559 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Same problem with a Huawei P9 Lite (2017) I see the problem with jmtpfs or mtp-tools so definitely the bug is in libmtp9 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmtp9 depends on: ii libc6 2.28-8 ii libgcrypt201.8.4-5 ii libmtp-common 1.1.16-2 ii libusb-1.0-0 2:1.0.22-2 Versions of packages libmtp9 recommends: ii libmtp-runtime 1.1.16-2 ii udev241-3 libmtp9 suggests no packages. -- no debconf information
Bug#921559:
Control: severity -1 important Hi, I tried to reproduce this problem with an up-to-date (2019-04-01) live Buster. And I was not able to reproduce this problem with all my Android devices (Nexus 5, Nexus 7, Galaxy S3, Galaxy J5 2018 and Galaxy Tab A 2018). So, I reduce the severity of this bug for the moment. Best, Dylan
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
Control: forwarded -1 https://sourceforge.net/p/libmtp/bugs/1818/ Looks like there are problems with more phones (forwarded to bug about Moto G regression).
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
Control: found -1 1.1.16-1 Control: severity -1 serious I've downgraded to 1.1.13-1.1 and my phone is accessible again. Upgrading version introduces problem again. Naively bumping severity in hope to be fixed for Buster.
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
Control: reassign -1 libmtp9 Looks more like a problem in libmtp9 (or maybe the kernel). Reassigning to libmtp9. I don't see it being reassigned, trying again.
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
On Sun, 17 Mar 2019 10:53:57 +0200 Vincas Dargis wrote: > I just tested on GNOME Sid, also cannot access smartphone via MTP: > > Mar 17 10:52:41 debian-sid-gnome gvfsd[1241]: error returned by > libusb_claim_interface() = -6LIBMTP > PANIC: Unable to initialize device > Mar 17 10:52:42 debian-sid-gnome gvfsd[1241]: Device 0 (VID=2a47 and > PID=2008) is a bq Krillin (MTP). > Looks more like a problem in libmtp9 (or maybe the kernel). Reassigning to libmtp9. If you are convinced this actually a bug in udev, please re-assign back providing some context why you think this is a udev bug. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
I just tested on GNOME Sid, also cannot access smartphone via MTP: Mar 17 10:52:41 debian-sid-gnome gvfsd[1241]: error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Mar 17 10:52:42 debian-sid-gnome gvfsd[1241]: Device 0 (VID=2a47 and PID=2008) is a bq Krillin (MTP).
Bug#921559: kio-extras: MTP browsing stopped working (after recent udev upgrade?) with "The file or folder udi=/org/kde... does not exist."
Package: kio-extras
Version: 4:18.08.3-1
Severity: normal
Dear Maintainer,
A was using Dolphin for browsing files in Android-based phone for quite
some time, and while I did have some occasional flanky problems (similar to
#920153), it seems I can no longer browse *at all* with different error:
```
The file or folder
udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2
does not exist.
```
This is what syslog prints when I connect phone:
```
Feb 6 21:20:56 vinco kernel: [ 4241.131018] usb 2-2: new high-speed USB
device number 23 using xhci_hcd
Feb 6 21:20:56 vinco kernel: [ 4241.279954] usb 2-2: New USB device
found, idVendor=2a47, idProduct=2008, bcdDevice= 2.16
Feb 6 21:20:56 vinco kernel: [ 4241.279961] usb 2-2: New USB device
strings: Mfr=2, Product=3, SerialNumber=4
Feb 6 21:20:56 vinco kernel: [ 4241.279964] usb 2-2: Product:
Aquaris_E5_HD
Feb 6 21:20:56 vinco kernel: [ 4241.279968] usb 2-2: Manufacturer: BQ
Feb 6 21:20:56 vinco kernel: [ 4241.279971] usb 2-2: SerialNumber:
UA001404
```
Snippet from `.xsession-errors` (sorry, some messages are in my native
lanugage):
```
QObject::connect: invalid null parameter
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to
initialize device
Object::disconnect: No such slot
Meta::MtpHandler::slotDeviceMatchSucceeded()
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "bind"
org.kde.plasmaquick: Applet "Pranešimai apie įrenginius" loaded after 0
msec
org.kde.plasmaquick: Increasing score for "Pranešimai apie įrenginius"
to 100
org.kde.plasmaquick: Applet "Sistemos dėklas" loaded after 0 msec
org.kde.plasmaquick: Applet "Sistemos dėklas" loaded after 1 msec
org.kde.plasmaquick: Increasing score for "Sistemos dėklas" to 100
file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/FullRepresentation.qml:163:25:
Unable to assign [undefined] to QString
kde.kio-mtp: fileSystemFreeSpace:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp: udi =
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2"
kde.kio-mtp: fileSystemFreeSpace:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp: udi =
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2"
kde.kio-mtp: New device attached with udi=
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2" .
Checking if PortableMediaPlayer...
kde.kio-mtp: SOLID: New Device with udi=
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2"
kde.kio-mtp: new device, getting raw devices
kde.kio-mtp: No Error, continuing
kde.kio-mtp: Found device matching the Solid description
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to
initialize device
kde.kio-mtp: fileSystemFreeSpace:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp: udi =
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2"
kde.kio-mtp: fileSystemFreeSpace:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp:
QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2")
kde.kio-mtp: udi =
"/org/kde/solid/udev/sys/devices/pci:00/:00:14.0/usb2/2-2"
UdevQt: unhandled device action "bind"
org.kde.plasmaquick: Applet "Pranešimai apie įrenginius" loaded after 0
msec
org.kde.plasmaquick: Increasing score for "Pranešimai apie įrenginius"
to 100
org.kde.plasmaquick: Applet "Sistemos dėklas" loaded after 0 msec
org.kde.plasmaquick: Applet "Sistemos dėklas" loaded after 0 msec
org.kde.plasmaquick: Increasing score for "Sistemos dėklas" to 100
file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/FullRepresentation.qml:163:25:
Unable to assign [undefined] to QString
file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/FullRepresentation.qml:163:25:
Unable to assign [undefined] to QString
file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/FullRepresentation.qml:163:25:
Unable to assign [undefined] to QString
