New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't qvm-copy-to-vm files mounted as gvfs/mtp (qfile-agent: Operation not supported) #1726

Closed
taradiddles opened this Issue Feb 7, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@taradiddles

summary: trying to copy files from a gvfs/mtp mountpoint to a vm with qvm-copy-to-vm throws a "qfile-agent [...] Operation not supported" error.

environment: 3.1rc2 ; sys-usb vm.

steps to reproduce:
1- plug in a usb mtp device (in my case a samsung tablet)
2- open nautilus in sys-usb, click on the "android" device to mount the device. It's now mounted in /run/user/1000/gvfs/mtp:host=[...]/Tablet
3a - in nautilus, browse to some folder on the tablet, select and copy to vm (for instance "untrusted")
3b- or, in a terminal, qvm-copy-to-vm untrusted some_folder_on_that_tablet
4- if the folder is large, it takes a bit of time then there's the usual "do you allow domain sys-usb to execute[...]", click yes, it takes a bit of time again, and I get the following error:

"qfile-agent: Fatal error: open DCIM/Camera/20110603_060631.jpg (error type: Operation not supported)"

maybe it's specific only to MTP devices, or to gvfs or even fuse as a whole. Let me know if I you need more tests (eg. I could enable networking in sys-usb and try a ssh gvfs mount).

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 7, 2016

(forgot to add that copy between the private fs and the device is working. So the workaround is to copy files from the mtp device to sys-usb's rw/..., then qvm-copy-to-vm from there.)

(forgot to add that copy between the private fs and the device is working. So the workaround is to copy files from the mtp device to sys-usb's rw/..., then qvm-copy-to-vm from there.)

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 7, 2016

Member

Interesting. Even more interesting that a simple cp on such files also fails, with the same message. So it looks to be specific to mpt/gvfs, not exactly qvm-copy-to-vm only.
When copying the file using Nautilus, it makes some D-Bus calls to gvfs daemon to do that.

Member

marmarek commented Feb 7, 2016

Interesting. Even more interesting that a simple cp on such files also fails, with the same message. So it looks to be specific to mpt/gvfs, not exactly qvm-copy-to-vm only.
When copying the file using Nautilus, it makes some D-Bus calls to gvfs daemon to do that.

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 7, 2016

Sorry, I should have tested that. I used nautilus to do the mount magic but couldn't imagine that copying files would be different than regular cp.
When time permits I'll try to test that behavior on a f23 standalone install.

Sorry, I should have tested that. I used nautilus to do the mount magic but couldn't imagine that copying files would be different than regular cp.
When time permits I'll try to test that behavior on a f23 standalone install.

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 7, 2016

So - tested with stock f23, and same weird behavior there. Closing, not a Qubes issue.

So - tested with stock f23, and same weird behavior there. Closing, not a Qubes issue.

@taradiddles taradiddles closed this Feb 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment