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 upCan't shutdown VMs from Qubes widget #3739
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Duplicate of #3660 |
andrewdavidwong
marked this as
a duplicate of
#3660
Mar 25, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
andrewdavidwong
Mar 25, 2018
Member
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.
|
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you. |
andrewdavidwong
closed this
Mar 25, 2018
andrewdavidwong
added
the
duplicate
label
Mar 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
n1m1 commentedMar 24, 2018
Qubes OS version:
R4.0-rc5
Affected component(s):
Qubes widget
All templates and AppVM
Steps to reproduce the behavior:
In Qubes 4.0-rc5 (the problem was not present in 4.0-rc4) I am experiencing a weird issue with Qubes widget. Please, take a look to this picture.
When I open a VM (be it an AppVM or a ProxyVM) or a Template (be it Fedora, Debian or Whonix), a circle appears in the widget - I do not know what it means exactly - and it never stops. In the menu of the VMs affected by this problem, the "Shutdown" button is not present anymore (only the "Kill" one). In order to shutdown a VM or a Template i need to run
qvm-shutdown nameoftheVMin Dom0.
If I click on "Console log", "Qrexec log" or "GUI Daemon Log" nothing happens.
This issue appears randomly: as mentioned above, it affects AppVM and ProxyVM, independently from the template they are based on. Sometimes a VM is not affected by this problem, but after a reboot it is.
No idea how to debug this problem, nor which logs I should look at.