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 upqvm-copy-to-vm unexpressive error message if argument are inverted #3086
Comments
andrewdavidwong
added
bug
C: core
labels
Sep 9, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Sep 9, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cartman4
Mar 15, 2018
I cant copy or move any files to other VMs since the last update (tried current-testing which seams to be RC-5 now and a the dom0-current repo of RC-4) i only get Request refused message when trying from terminal or nothing happens if i try it using the GUI
cartman4
commented
Mar 15, 2018
|
I cant copy or move any files to other VMs since the last update (tried current-testing which seams to be RC-5 now and a the dom0-current repo of RC-4) i only get |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Mar 15, 2018
Member
|
On Thu, Mar 15, 2018 at 10:35:05AM -0700, cartman4 wrote:
I cant copy or move any files to other VMs since the last update (tried current-testing which seams to be RC-5 now and a the dom0-current repo of RC-4) i only get `Request refused` message when trying from terminal or nothing happens if i try it using the GUI
Have a look at the policy file in /etc/qubes-rpc/policy and make sure
that the qube you are using is covered there.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 15, 2018
Member
@cartman4 Are you sure you have installed updates in both dom0 and template? There should be qubes-core-dom0 4.0.24 (dom0) and qubes-core-agent 4.0.24 (template). And restarted VMs?
In some cases (depending on previous version) system restart might be required.
BTW This is different than original issue. I believe original issue is resolved by introducing qvm-copy/qvm-move tools, which do not have VM name argument at all.
|
@cartman4 Are you sure you have installed updates in both dom0 and template? There should be qubes-core-dom0 4.0.24 (dom0) and qubes-core-agent 4.0.24 (template). And restarted VMs? BTW This is different than original issue. I believe original issue is resolved by introducing |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cartman4
commented
Mar 15, 2018
|
thanks marmarek. missed updating templates to same version. |
Mayeu commentedSep 8, 2017
Qubes OS version (e.g.,
R3.2):R4-rc1
Affected TemplateVMs (e.g.,
fedora-23, if applicable):Not sure if applicable, but all my test happened in AppVM using fedora-25
Expected behavior:
When running
qvm-copy-to-vmwith the wrong argument, eg.qvm-copy-to-vm $file $toVMinstead ofqvm-copy-to-vm $toVM $file, the tool should error out saying something like:Actual behavior:
The only error showned is:
The result is that you end-up digging into your policy to understand why on earth you can't send something from this VM when the policy clearly state
$any $any ask:)Steps to reproduce the behavior:
qvm-copy-to-vm