MTP error when connecting phone

[ghost]

 * Nemo version (nemo --version)
 4.8.4
 * Is issue with desktop or windowed nemo?
 desktop
 * Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
 Mint 20.1
 * Graphics hardware *and* driver used
 unknown
 * 32 or 64 bit
 64

After upgrading from Linux Mint 20 to 20.1 (Cinnamon) I cannot mount my phone, or maybe I can mount it but can't look at it.

Phone is Google Pixel 3 running Android 11.

Steps to reproduce

• Connect phone to computer via USB C cable

• In USB Preferences on phone, select File transfer / Android Auto

• Upon connecting cable, Pixel 3 appears under Devices in Nemo, but error message appears. I have seen two different messages on different attempts:

Unable to open a folder for Pixel 3 No such interface "org.gtk.vfs.Mount" on object at path /org/gtk/vfs/mount/1

and

Could not display "mtp://Google_Pixel_3_8A9X0NLW2/". Error: The name:1.744 was not provided by any .service files Please select another viewer and try again.

Attempting to navigate to Pixel 3 in Nemo repeats the error message.

Expected behaviour

• Before upgrade, Pixel 3 would appear under Devices in Nemo upon connecting cable, and after selecting File transfer a window would appear showing files on the phone.

Other information

I asked about this on the Linux Mint forums and antikythera noted possible connection with https://github.com/linuxmint/nemo/issues/2632 and recommended opening a new issue here.

[ghost]

Closing this issue as I can no longer reproduce the problem.

[Hordeking]

This issue might be with gvfs. I think it should be reopened until we know if the bug is with Nemo or at a lower level. I have no way of getting verbose information from Nemo to narrow it down much.

I am able to mount my android phone via mtp and browse files, but when I attempt to access them, nemo gets stuck. I also opened in a terminal and attempted to copy files out using rsync -vP. rsync simply hung until I had to kill it with -s9. No error, no progress bar, nothing.

In the meantime, until we know that the issue is with GVFS and not Nemo, I'm requesting this issue be reopened.

[akred]

Hello, I agree, I have exactly the same issue

[ParticleMon]

Do reopen. Same issue but with a OnePlus and a different cause. The MTP error includes the name ":1.8596"

This started sometime after flashing a custom ROM, changing settings, and installing apps. No such issue with previous ROMs on the same device, and PTP still works.

This program, a suggested workaround, works: https://github.com/whoozle/android-file-transfer-linux

Mint 20.2 Cinnamon 5.0.7 nemo 5.0.5

[MohamedTarekq]

I have exactly the same issue

[sakralbar]

Same issue with mint 20.3, Nemo and android 11 phone.

[adb-luna]

Same issue with 21.1 and Android 13 phone. Update: After that original post, I ran scrcpy to show my phone's screen on my PC, and then the mtp error did not occur in Nemo. Very strange.

[Area5142]

Same issue with LM 21.1 Cinnamon and Android phone (version 9). Everything worked fine in LM 19.3 Cinnamon and earlier on the same HW before reinstalling

[jdancouga]

I am seeing the same issue when connecting my Garmin fitness watch on LM 21.1 Cinnamon.

[LinuxOnTheDesktop]

@holmesrichards

Please re-open this issue. For, several people report that they still have the problem and I too see the error message that is in question.

[BarbzYHOOL]

me too but only on nemo, not on nautilus

[ZebulonGlitch]

Me three. It's been a bug ever since I put mint 21 on this laptop (i use a Fairphone 5 (android) but it was the same problem with my old android phone a few months ago. Been suffering with it well over a year - quite brutal.

In Nemo on my rig: MTP file transfer via USB to a phone will work ~33% of the time on a fresh boot if you're extremely careful with the sequence you connect and allow USB file transfer. But it's 100% guaranteed on my rig that Nemo will lose its mind eventually and give errors if you try anything ambitious like disconnect and reconnect the phone. It sometimes bombs out mid transfer on a large group of files. Reboot fixes it until you again get ambitious.

Update: BarbzYHOOL above is an inspired genius!!! I just installed nautilus and indeed that app is able to transfer files to and from my phone perfectly!! Epic lifesaver! This is definitely a Nemo only issue. Inspired by this I went and used double commander and it also has no problems with accessing the phone. I feel so dumb thinking this was some deeper GVFS issue when in the end it was merely a local NEMO glitch....

important work around note to anyone else with this issue: Use a different file manager until Nemo is fixed! :-)

(I do love Nemo, it's a slick tool. Hope it's fixed soon :)

[Jeremy7701]

Have to say that 2 Samsung phones work 100% (get a spurious message when nemo mounts them).

[LinuxOnTheDesktop]

@Jeremy7701

I presume that your testing was somewhat 'ambitious' (to quote @ZebulonGlitch).

Either way, Nemo struggles to transfer data reliably to at least some phones, whereas, it seems (see the comment by BarbzYHOOL), Nautilus does not. So, perhaps the problem can be identified by seeing where relevant code within Nemo differs from the code that Nautilus has.

Also, we could do without those 'spurious message[s]', no? (Still, I seem to recall, vaguely, that the message might owe to something upstream.)

[Jeremy7701]

Sure - but the spurious dialog boxes, requiring me to click a mouse once or twice are not a big deal.

[LinuxOnTheDesktop]

the spurious dialog boxes, requiring me to click a mouse once or twice are not a big deal.

Not a big deal, no, except that (1) the boxes contributes to an unpolished feel, (2) if one plugs in one's phone often, then a few clicks become many clicks. Anyhow, those boxes ought to be the subject of a separate bug report.

[BarbzYHOOL]

thank you Zebulon, I like being viewed by others exactly how I view myself

Yeah, if it's only one single function or file that is related to that thing, then comparing with Nautilus would be fairly simple but it requires to know how to develop linux apps and have the tools for

[gessel]

My system too - Samsung phone, worked fine under mint 20.0, updated to 20.3 and got: Could not display "mtp://SAMSUNG_SAMSUNG_Android_26f..../" Error: the name :1.5... was not provided by any .service files Please select another viewer and try again.

Good advice in that error:

sudo apt install nautilus

Loads just fine, seems faster moving pictures/video from phone to desktop, so that's workable. Too bad about Nemo, I prefer not to have two file managers installed.

[NickSto]

Just attesting that I've been having this issue often for years. It often goes away after a bit, but the last several days it's been constant. I just tried opening it in Nautilus and it worked fine. But I hate Nautilus and I really want to stick with Nemo!

FYI I'm running Ubuntu 20.04 and connecting to a Google Pixel 7.