"libmtp error: Could not send object info" when copying content to root MTP folder

[Richard Huddie]

ENVIRONMENT:
Ubuntu device: ubuntu-rtm/14.09-proposed build 40
Desktop: Ubuntu 14.10

SUMMARY:
"libmtp error: Could not send object info" when copying content to root MTP folder

STEPS:
1) Connect Ubuntu MTP device over USB
2) Attempt to copy some content to the root of the MTP folder

EXPECTED RESULT:
The copy operation should succeed. (This is the Android behaviour).

ACTUAL RESULT:
An error message is presented on desktop: "libmtp error: Could not send object info"

[Michael Frey (mfrey)]

Our behavior is different. We do not allow files in the root . Files can only live in the folders listed in the mtp share.

[Duane Moody (duane-moody)]

Michael, I'm intrigued by your comment because Android File Transfer for OS X is capable of moving files to the root of an MTP folder, and its backend is libmtp.

Also, applications like calibre are designed to keep manifests at the root of whichever storage they're connected to. Unless the documentation for libmtp explicitly forbids file write access at the root (and the error thrown is more specific about this), developers will assume they have access.

Can you walk me through this decision?

[Martin Spacek (mspacek)]

I get this "Could not send object info" error from libmtp on seemingly random files while copying a large number of files to a subfolder of "Internal storage" on my Moto X running CyanogenMod 11 2014-11-28 (ghost), using Thunar in Xubuntu 14.04. On second glance, I think this is due to the full pathnames of some of the files on the destination exceeding 255 characters in length. Could use a more informative message. Does MTP provide more descriptive error codes?

[Dmytro (sequentiality)]

I have the same issue @ Xubuntu 14.04.1 64-bit.

I can't copy file to LG-P705 (connected via MTP), copying hangs and after I get "libmtp error: Could not send object".
But I can create folders.

Also sometimes Xubuntu file manager hanfs when device is connected via MTP.

Version of libmtp is 1.1.6-20-g1b9f164-1ubuntu2.

[tasadar_f (tasadarf)]

 I have the same problem.

I can't copy a big file to my smartphone Xiaomi mi2s. The transfer start but stop after 1 or 2 or 3 minutes.

Ubuntu 14.10 32bits

Version of libmtp 1.1.6-20-g1b9f164-1ubuntu5

[snurfle (snurfle)]

I'm removing ubuntu 14.04.2 64-bit from a Lenovo W530, and wanted to put a few things on my phone (samsung galaxy s4, JB) before I wiped it... and nothing will copy, it just repeatedly gives this error.

Ah well, I'm deleting ubuntu so I guess I really don't need a reply, but at least there is one more data point for someone who may be working on this problem.

[Felipe Castillo (fcastillo.ec)]

I see this problem when trying to copy files under folders to my Android phone. I see the same error and then I see that the first folder was created but nothing else was copied. If I only send files (no folders at all) I don't see the error anymore. So I manually have to create all my folders and then copy the files to each of the folders. This is very annoying.
I hope this description helps anybody to fix the problem. I'm using a Nexus 5 with Ubuntu 14.04 64bit

[Paulo Oliveira (poliveira-u)]

I got this error too, in Ubuntu 15.04 64-bit while copying a folder with a colon in the name.
Removed the colon, solved the problem!
Hope it helps someone

[NoBugs! (luke32j)]

It's actually happening when you copy to non-root-directory, unless Samsung Android/Phone/Music/ is considered root folder.

Keeps freezing or just does nothing - maybe it's caused by dashes or _ in the folder or file name? Going too slow or just crashing, when connected to Android 5.1.1 device. Maybe it's just that version?

[devoncatt (chelle)]

Same exact problem. The weird part is that before I had to reinstall Ubuntu 16.04 it worked fine in transfers to the SD card. I did a factory reset on my S7. But the exact same problem is happening with a Nexus 7 that also previously worked. Android 6.01 with patches.

[devoncatt (chelle)]

I enabled developer mode as suggested elsewhere. I get the feeling it is a Samsung issue because I have the same problem if I boot Windows 10 instead of Ubuntu 16.04 64 bit. Samsung S7 says transfer files to PC (not from PC

[Sampath Gopathi (g-sampath004)]

Same Issue.
I have been using MotoG 3rd Generation.
It was working fine.
All of sudden unable libmtp error unable to send objects comes up.
and System Hangs occationally due to this.

[Bib (bybeu)]

Same here, copying ~3GB with nemo from 14.04.5 to Samsung Android 5.1.1 /extSdCard/Musique/Musique Vrac/
After the error, or even without error show, system becomes unresponsive until I unplug the phone. Then I replug/remount everythings seems OK, but when I browse to the subfolder on the sdcard, nemo can't show it poping "unable to display folder content, Sorry, unable to show the whole content of "Musique Vrac". libmtp error : couldn't get object handles"

[erwan KRUG (erwank)]

Hi everybody,

has any answer been found or is this just a matter of root permissions on androids ?

I have the same issue: "libmtp error: Could not send object info"

keep me up-dated ! :)
erwan.

[James Bowery (jabowery)]

The title of this bug report is either inaccurate or it isn't the same bug as some of us are experiencing:

Large file copy always fails to non-root directory on Android.

[inchidi (inchidi-r)]

helo if you are experiencing this `libmtp error`, you cant write to sd card from your ubuntu, please try `format your SD Card from your Android` and try write to your sd card again.

[Teddy525 (boring525)]

It also occurs in Ubuntu 16.04.3 and it happened to me before I discovered the sd card was full.
It gave no warning that the sd card was full and instead gave the libmtp error.

[Kristoffer Grundström (umeaman)]

This also exists in 20.10.

[Bill Hayden (hayden-haydentech)]

This happens for me on 20.04 LTS when the file being copied has a colon (:) in its name. The error doesn't pop up until the very end of the file copy process, and in the end, the file is not copied to the destination.