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

Use qubes.StartApp service by default for qvm-run when no --pass-io specified #3043

Closed
rootkovska opened this Issue Aug 23, 2017 · 1 comment

Comments

Projects
None yet
3 participants
@rootkovska
Member

rootkovska commented Aug 23, 2017

As discussed in #3012. While this is strictly not a bug, not fixing this for 4.0 release we can be sure to receive many bug reports for qvm-run not working by default, especially for DispVMs.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 25, 2017

Member

Note that the argument to qubes.StartApp is not a command name, but application name, as in /usr/share/applications. While for xterm or firefox it is the same, for others may not be: for example Nautilus is org.gnome.Nautilus.
This is done to allow "staring application in a VM", without giving arbitrary command execution.
#3012 require different solution, but lets discuss is there. Not in (this) duplicate.

Member

marmarek commented Aug 25, 2017

Note that the argument to qubes.StartApp is not a command name, but application name, as in /usr/share/applications. While for xterm or firefox it is the same, for others may not be: for example Nautilus is org.gnome.Nautilus.
This is done to allow "staring application in a VM", without giving arbitrary command execution.
#3012 require different solution, but lets discuss is there. Not in (this) duplicate.

@marmarek marmarek closed this Aug 25, 2017

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