Haven’t been around in ages–hope everyone’s doing well. Hope anyone from Ukraine is safe and sound.
I have this problem (maybe not exactly this), but it’s been something that’s been around for ages. On my Intel 10th Gen laptops the issue has been around since around 2020. I never bothered reporting it since I figured something like this would be fixed by release, but it hasn’t.
Basically, fiddling with qube settings, shutting down VMs, etc. can lead to the manager window just vanishing. I don’t know exactly what triggers it, but it’s something along the lines of ‘interacting with qubes’.
While I’m here: Everybody’s probably busy with more pressing concerns, but I just want to say that since R4.1 has been released with major changes to qrexec, it would be beneficial to the project if documentation referencing changes to no-longer-existent qrexec policies be updated before newcomers get extremely confused and discouraged by having to deal with outdated documentation on top of having to learn a new mode of computing. E.g. The pages for configuring sudo prompt and Yubikey. @adw
Also, @tasket just wanted to say that your github.com/tasket/qubes-scripts works fine, but github.com/tasket/qubes-vm-hardening doesn’t seem fully compatible with R4.1 (configure-sudo-prompt is flat incompatible due to the qrexec changes mentioned earlier). Booting certain Debian-11-minimal templates on a fresh Qubes installation with vm-boot-protect enabled can sometimes trigger its defenses leading to a terminal error message and a dom0 notification that something was written to dom0 (I don’t fully remember the details). Maybe this is an issue on my end.
P.S. has anyone figured out how to make minimal templates display sudo prompts yet? And are suspend and hibernate still not supposed to work on newer machines?