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

Qubes 4.0 qvm-run should be asynchronous by default like in 3.2 #3231

Open
qubesuser opened this Issue Oct 27, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@qubesuser

Qubes OS version:

R4.0-rc2

Steps to reproduce the behavior:

  1. Use qvm-run to start something

Expected behavior:

qvm-run exits immediately (unless --pass-io is specified)

Actual behavior:

qvm-run waits for the program to terminate

General notes:

Qubes 3.2 behaved like this (unless I'm crazy), and I think compatibility should be kept.

A --wait flag should be introduced to wait for the program instead of making it the default.

Also there should ideally be --startup-notification flag that waits for startup notification and relays it to dom0 so the desktop GUI hourglass cursor works properly.

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