Running qubes are sometimes missing from Qubes widgets

permezel commented 1 year ago

How to file a helpful issue

Qubes OS release

4.1.2

Brief summary

The Qubes Domain widget is missing at least one of my running AppVM.

Steps to reproduce

Boot Qubes
start some AppVM
right-click on Qubes Domain Widget
Verify that all running AppVm are present in the list: bug if not

Expected behavior

I expect all running AppVM to be present in the list. This also affects the ability to assign USB devices to AppVM. The first time I noticed this I was trying to assign a YubiKey to a running AppVM and it was not present in the list.

Actual behavior

One or more AppVM are missing. In screenshot, the AppVM "beto" is missing, but it can be seen to be running from the Qubes Manager. It really is running.

I note that this was identified previously, and closed as a dup of another bug which was also closed as fixed back in 2022. This is a newly installed system (with old 4.1.2 system backup re-installed). Just ran qubes-dom0-update and nothing updated, so I am reasonably sure I have the fixes from 2022 applied.

Screenshot_2023-07-29_09-33-32

andrewdavidwong commented 1 year ago

I note that this was identified previously, and closed as a dup of another bug which was also closed as fixed back in 2022.

Sounds like a possible duplicate of #7362.

This is a newly installed system (with old 4.1.2 system backup re-installed). Just ran qubes-dom0-update and nothing updated, so I am reasonably sure I have the fixes from 2022 applied.

Even so, if this is the same bug, then we should reopen that issue.

But there still isn't enough information to tell whether it's the same bug, as far as I can tell.

Please read through #7362 and see whether that matches your situation. In particular, please specify whether this happens only when starting things concurrently or whether it also happens when the missing VM is the only thing recently started.

permezel commented 1 year ago

Edit: Went back to verify some assertions --- fixing up lies and misrepresentations.

I looked at #7326. It may match my situation, however I do not start Qubes Manager. I do not have any auto-start things.

[nimda@dom0 ~]$ find ~/.config/ | grep start
[nimda@dom0 ~]$

Just powered on my system. I have 12 qubes which do start automatically due to "start qube automatically on boot" being set. One VM started is missing from the list -- beto-email.

Screenshot_2023-07-31_11-07-47

permezel commented 1 year ago

I just remove the "start qube automatically on boot" setting on the sys-firewall-02-mgmt as I no longer use it. Rebooted. All qubes are in the list. Screenshot_2023-07-31_11-27-08

Unsure what this implies, but another data point.

permezel commented 1 year ago

Another data point. Just rebooted, with the same 11 AppVM as above, and admin-aws is missing. Screenshot_2023-08-01_17-57-33

marmarta commented 1 year ago

I think this means some events get lost. Theoretically, we do a complete refresh of the widget menu once connection to the event dispatcher is established, but this looks like it doesn't really work and some events are lost. Or it's a cache problem...

marmarta commented 1 year ago

Ok, found it. The (new) fix should work.