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

qvm-copy doesn't work #3614

Closed
dakka2 opened this Issue Feb 20, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@dakka2

dakka2 commented Feb 20, 2018

Qubes OS version:

R4.0

Affected TemplateVMs:

All

Steps to reproduce the behavior:

qvm-copy any file from any vm to any vm

Expected behavior:

file copies

Actual behavior:

Request Refused

General notes:

from qrexec log in dom0:
Traceback (most recent call last):
File /usr/bin/qrexec-policy, line 5, in
sys.exit(main())
File /usr/lib/python3.5/site-packages/qubespolicy/cli.py, line 128, in main
action.targets_for_ask, action.target or '', icons)
File /usr/lib/python3.5/site-packages/pydbus/proxy_method.py, line 75, in call
0, timeout_to_glib(timeout), None).unpack()
GLib.Error: g-io-error-quark: GDBus.Error:unknown.AssertionError: Input string was expected to be sanitized, but was not. (36)

Seems to be related to qubes-core-admin 4.0.23 / qubes-core-admin-linux 4.0.11 / qubes-core-agent-linux 4.0.22 but I don't know for sure. Packages in testing not unstable.

please delete #3613 it was created by mistake.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 20, 2018

Member

You need to restart qrexec-policy-agent in dom0:

killall qrexec-policy-agent
qrexec-policy-agent &

Or simply restart the system.

Member

marmarek commented Feb 20, 2018

You need to restart qrexec-policy-agent in dom0:

killall qrexec-policy-agent
qrexec-policy-agent &

Or simply restart the system.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 20, 2018

Member

Also, be sure to install updates in templates before that.

Member

marmarek commented Feb 20, 2018

Also, be sure to install updates in templates before that.

@dakka2

This comment has been minimized.

Show comment
Hide comment
@dakka2

dakka2 Feb 20, 2018

Just you you know it's still $default in qvm-copy/qvm-copy-to-vm in the templates. it worked after restarting policy agent anyway.

dakka2 commented Feb 20, 2018

Just you you know it's still $default in qvm-copy/qvm-copy-to-vm in the templates. it worked after restarting policy agent anyway.

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