I have a template based on Debian-10 called
d10-social. In this template, I have some social apps installed, like Slack, Element, Zoom. Then I have AppVMs using this template, like
My most recent backup is from March 27. At that time, I had no problems with any of my template or app VMs.
On March 28, I updated all VMs using the Qubes update manager. Now, when I try to open any app from an AppVM using the
d10-social template, no windows/GUI features will launch. For example, even just trying to open
gnome-terminal, it will not open. The Qube Manager shows the
work-social AppVM is running, but trying to open any apps on there does nothing. Please see this reply which elaborates on the issue, where I discovered that no terminal commands (e.g.,
whoami) will execute on AppVMs based on this updated termplate.
Perhaps the services are starting but I don’t actually see any windows. For what it’s worth, I also cannot access these apps from the
d10-social template VM itself after updating.
d10-social template VM to the backup I created on March 27 is a work-around - I can then open and use apps once again. But after an update of the template VM and restart, all AppVMs based on that template become useless.
I have other VMs based on Debian-10, like a
d10-dev VM that I use for development. This continues to work fine after the most recent updates. This leads me to believe that something unique to the
d10-social template VM is causing issues with Qubes.
How do I resolve this? What additional info can I provide to help triage? Is this an issue introduced by some Debian package maintainers? Or more likely an issue that can be resolved with Qubes?