Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqfile-agent fatal error no such file #4058
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
donob4n
Jul 7, 2018
This is not a bug, qvm-copy is different in Qubes 4 (assuming in Qubes 3.2 was not modified).
You should do: 'qvm-copy a' , then you will get a dialog in dom0 asking the target VM. This way the source AppVM does not know the name of the destination VM.
donob4n
commented
Jul 7, 2018
|
This is not a bug, qvm-copy is different in Qubes 4 (assuming in Qubes 3.2 was not modified). You should do: 'qvm-copy a' , then you will get a dialog in dom0 asking the target VM. This way the source AppVM does not know the name of the destination VM. |
andrewdavidwong
added
enhancement
C: core
UX
labels
Jul 8, 2018
andrewdavidwong
added this to the Release 4.1 milestone
Jul 8, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Filing this as a UX enhancement to improve the error message. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
pietrushnic
Jul 9, 2018
Help of qvm-copy say:
usage: /usr/bin/qvm-copy-to-vm [--without-progress] dest_vmname file [file]+
This looks confusing to users.
pietrushnic
commented
Jul 9, 2018
|
Help of
This looks confusing to users. |
pietrushnic commentedJul 7, 2018
•
edited
Edited 1 time
-
pietrushnic
edited Jul 7, 2018 (most recent)
-
pietrushnic
created Jul 7, 2018
Qubes OS version:
R4.0
Affected component(s):
qvm-copy between all VMs
Steps to reproduce the behavior:
Expected behavior:
File should be copied to vault VM.
Actual behavior:
qfile-agent throws error:
General notes:
The only thing I was able to narrow is that below version works:
Debugging
qvm-copy-to-vmshow:I'm not sure if input params to
qfile-agentchanged or I messed up something. I'm not confident 100%, but this probably happen after template update.Related issues: