-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Ubuntu VM fails to start applications on first attempt #8205
Comments
I observed a similar behavior with jammy on Qubes R4.1, and also for debian bookworm on R4.1. Might have the same cause???? |
Very likely. |
Tested fix QubesOS/qubes-core-agent-linux#426 on R4.2 on:
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
I can confirm that this issue is also present on R4.1 with Debian bookworm, and that QubesOS/qubes-core-agent-linux@41e6458 fixes it. However it seems like that patch was only applied to the R4.2 branch. Can it also be applied to R4.1? |
Closes QubesOS/qubes-issues#8205 (cherry picked from commit 41e6458)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
How to file a helpful issue
Qubes OS release
R4.2
Brief summary
When starting an application in a Ubuntu jammy VM that wasn't running already, the VM is started, but the application is not. Starting an application in already running VM works fine.
Steps to reproduce
qvm-run VMNAME gnome-terminal
Expected behavior
VM starts and gnome-terminal opens up.
Actual behavior
VM starts, but no application is started.
qvm-run
hangs. It seems to hang on thequbes.WaitForSession
call.On the process tree, under
qubes.WaitForSession
I see:The text was updated successfully, but these errors were encountered: