Daniel P. Berrangé <berra...@redhat.com> writes: >> I can't find usb-mtp sending a "I/O error" on an error condition >> for the objectinfo phase. It might be libmtp or even the command itself >> failing for some reason. For incomplete transfer, I just checked, it's >> spitting out the error message correctly as INCOMPLETE_FILE_TRANSFER. >> >> With libmtp version 1.13 on a FC24 guest, here's the output: >> >> $ mtp-sendfile test.txt test.img >> libmtp version: 1.1.13 >> >> Device 0 (VID=46f4 and PID=0004) is UNKNOWN in libmtp v1.1.13. >> Please report this VID/PID and the device model to the libmtp development >> team >> ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, >> trying again after resetting USB interface >> LIBMTP libusb: Attempt to reset device >> Sending test.txt to test.img >> type: txt, 44 >> Sending file... >> Progress: 322 of 322 (100%) >> New file ID: 7 >> >> What guest is this ? I can try to reproduce. > > This was Fedora 26, so technically it is end of life, but then so > is your F24 guest :-) > > Should really check with a modern guest like Fedora 29 or rawhide. > I had a F28 guest and here, mtp-sendfile appears to succeed but no file is written However, nautilus works fine, it doesn't appear like an issue with libmtp or Qemu.
> Regards, > Daniel
