Bug 1187842 - "Operation unsupported" when copying files from "Recent" to MTP endpoint within Nautilus
Summary: "Operation unsupported" when copying files from "Recent" to MTP endpoint with...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 23
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Ondrej Holy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-31 01:16 UTC by smitna
Modified: 2016-12-20 13:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-20 13:11:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
mtp-detect output (32.82 KB, text/plain)
2015-02-06 04:52 UTC, smitna
no flags Details

Description smitna 2015-01-31 01:16:34 UTC
Description of problem:
See summary.

Version-Release number of selected component (if applicable):
gvfs-1.22.3-1.fc21.x86_64
gvfs-mtp-1.22.3-1.fc21.x86_64
nautilus-3.14.2-1.fc21.x86_64

Steps to Reproduce:
1.  open Nautilus / GNOME files
2.  show sidebar, and select "Recent"
3.  copy any(?) file within "Recent" to a device attached via MTP.  In my case, it was an Android phone (MTP enabled; PTP disabled)

Actual results:
"Operation unsupported" message.

Expected results:
Copy should proceed as normal; no obvious reason why this should fail systematically.

Additional info:
Source of file copy, e.g. the virtual "Recent" location, appears to be the cause.  To further support this, I repeated "Steps to Reproduce" but between steps 2 & 3, I invoked "Open Item Location" from file context menu.  From this "original" location, same copy operation proceeds without error.

Comment 1 Ondrej Holy 2015-02-02 08:40:37 UTC
Hey! It seems like duplicate of the bug 1184728. Android extensions aren't provided probably and therefore transfer works between local filesystem (file://) and the device only (not between two gvfs locations, recent:// and mtp://).

I know that recent files can be also local files, but gvfs doesn't know it. Maybe Nautilus could call copy operation with target-uri (e.g. file://...) and not with uri (recent://...) for recent files...

Can you install "libmtp-examples" package and provide output of "mtp-detect" command (with the connected device), please?

Comment 2 smitna 2015-02-06 04:52:08 UTC
Created attachment 988675 [details]
mtp-detect output

Sorry about the potential duplicate.  I have attached requested output (stderr and stdout combined).

Comment 3 Ondrej Holy 2015-02-09 12:17:42 UTC
(In reply to sdcgear from comment #2)
> Created attachment 988675 [details]
> mtp-detect output
> 
> Sorry about the potential duplicate. 

No problem, thanks for your bug report and for the log! The log confirms my idea from the Comment 1 why it doesn't work. However I don't mark the bug as duplicate for now, because it could be probably fixed also in different way...

Comment 4 Robert de Rooy 2015-10-04 20:15:45 UTC
Due to this bug report, I found out why I could not copy files from an SMB share in nautilus to an USB MTP device.

Solution was to first tranfer the files locally and then to the MTP device to prevent a copy between two GVFS devices.

gvfs-1.26.0-1.fc23.x86_64
gvfs-mtp-1.26.0-1.fc23.x86_64
gvfs-smb-1.26.0-1.fc23.x86_64
nautilus-3.18.0-1.fc23.x86_64

Bumped the bug report to F23 as it is still a current issue.

Comment 5 Fedora End Of Life 2016-11-24 11:24:39 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 13:11:42 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.