Closed jaseg closed 5 years ago
This also seems to affect some other services, I managed to hang qvm-open-in-vm
with both file and URL arguments.
This is directly caused by #951 Indeed qrexec should handle it better. I can easily convert it into "request refused" error, and also remove source from target selection. Some more elaborate error reporting would require slightly bigger change than I'm comfortable with doing as stable update.
Automated announcement from builder-github
The package qubes-core-dom0-4.0.41-1.fc25
has been pushed to the r4.0
testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Automated announcement from builder-github
The package qubes-core-dom0-4.0.41-1.fc25
has been pushed to the r4.0
stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
Thank you for the fix!
Qubes OS version: 4.0
Affected component(s):
qvm-copy
Steps to reproduce the behavior:
Run
$ qvm-copy /var/empty
in domain $foo then select same domain $foo as target.Expected behavior:
Either of:
Actual behavior:
qvm-copy starts, but progress hangs at 0kB and nothing happens. When invoked from nautilus via the context menu, Nautilus hangs.
General notes:
Showing an error message in dom0 might be done by extending the qubes policy framework to include a differentiation between
$anyvm
and$anyvm
excluding the source vm. This might make sense to prevent user error in other cases.Related issues:
None that I could find.