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
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:
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
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
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
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
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?
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
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
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).
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.
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.
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
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
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:
15 matches
Mail list logo
