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 upQubes 4.0 qvm-run should be asynchronous by default like in 3.2 #3231
Comments
andrewdavidwong
added
bug
C: core
labels
Oct 28, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 28, 2017
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
qubesuser commentedOct 27, 2017
Qubes OS version:
R4.0-rc2
Steps to reproduce the behavior:
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.