Hi there, first topic here 
It’s been a week now that, when using Qubes Update, after the update is complete and I select to restart AppVMs, nothing happens and I have to restart them all manually – a problem when it’s about the service apps.
The only different thing I remember doing before it started happening was testing some unprivileged user possibilities with “echo 0 > /proc/sys/user/max_user_namespaces” (along with “user.max_user_namespaces = 0” in /etc/sysctl.d/ directory), which I soon changed back to default 1259 in /proc/sys/user/max_user_namespaces (and deleted the line in sysctl.d).
Any clue anyone? Thanks in advance!
2 Likes
Welcome, i can’t help you for that. All i could doing is to give my values 
for /proc/sys/user/max_user_namespaces i have 31257 and in /etc/sysctl.d/ directory, i just have one file (99-sysctl.conf) and all lines are commented.
It’s just what i could do to help you
3 Likes
I got the same behavior today, for the first time - the running qubes based on updated templates were not restarted!
Probably a bug in the (graphical) Qubes Updater 
As I use this restart feature very seldomly, so seldom that I don’t remember when I used it last time - I cannot determine when the bug was introduced.
(R4.2.4 up-to-date)
4 Likes
Thanks for the reply! That was just something I’ve read about CVE-2021-22555 to fix it for good, but as Qubes is basically a bunch of containers: it really screwed up the experience and I went back to default. All the lines in 99-sysctl.conf must indeed remain commented out, as I understood. Thanks again for confirming!
2 Likes
Hmmm… it shall be a bug, then. Hopefully patched on coming dom0 updates. I restart them almost every time as I rarelly shutdown the pc. Thanks for sharing, barto!
3 Likes
I came here to make this exact post! Thank you very much OP
2 Likes
i just do an update and yes, AppVms doesn’t restart…
2 Likes
I’m not alone in this world! LOL Thank you, Nika.
2 Likes
God shall hear out prayers… :~
2 Likes
“God is dead” (Nietzsche)
Only Devs and Mods remain… 
3 Likes
lmao, true that
1 Like
2 Likes
since last update the same issue
1 Like
Still happening today
Out of curiosity based on this discussion, do you have chromium installed in these templates?
Yes it seems that was depending on that, yesterday I uninstalled & purged Brave Browser (chromium based) from fed-41. Today I didn’t have this issue, as well not the request of update as every day before uninstalling it.
dnf remove Vivaldi, Google Earth.
No change. Can’t see anything else google-linked, but wtf do I know.
But, setting SELinux to 0 works for template update now.
This has been such a time-sink.
1 Like
Yesterday I updated dom0 and the issue is again here. It confirms that’s not correlated to chromium apps.
here is the solution reported.
2 Likes
same still happening over here as well
Today’s dom0 update fixed this for me.
2 Likes