So after I check for updates with “Qubes Update” and there are no updates, in the end I get the message, that no qubes need to be restarted.
BUT after those qubes shutdown, which is what they always do after the looking for Updates procedure with “Qubes Update” is finished, the “Qube Manager” in the tray bar has those two green arrows building a circle beside the qubes that were checking for updates some seconds ago. An if I go over it with my mouse cursor, I get the following message displayed: “Qube must be restarted to reflect changes in template”. Almost the same if I open the “Qube Manager”, but there it’s just one grey arrow beside all the qubes in the “State” column that were checking for updates, but besides that I get almost the same message with “The qube must be restarted for recent changes in template to take effect”.
But that does not make any sense, because after finishing “Qubes Update” or rather looking for updates and with no updates found, “Qubes Update” told me that no qubes need to be restarted. So why is the “Qube Manager” telling me that the qubes need to be restarted right after “Qubes Update” told me the opposite?
So is this an UI bug or what is this about?
And like with my other bug report, this problem has been going on for a long time, I was just too lazy to report this.
I think the reason is the following: to update the template, the updater needs to start the template and, each time you start and shut down a template, dom0 will consider that every qube based on it might have to be restarted in order to reflect potential changes you made.
Since Microslop took over Github, you get shadow banned if you are using the Tor network like with the Tor Browser, meaning that you and you only can read your messages, but nobody else. So it would do nothing to put it on Github, because nobody besides me could read it.
And I remember reading something about Github, that they made it even worse. Can I even register an account using the Tor Browser now? I mean it wouldn’t do any good anyway, because like I said, you get shadow banned from the start and nobody can read your messages, but I’m just curious, because sometimes I read here and there something like “Microslop made Github even worse”…so who knows.
But again, since you get shadow banned from the start if you are using the Tor Browser, this forum is the only way for me to report a bug.
Thanks for following up! If you do try this, I hope it works and doesn’t turn out to be a further waste of your time. No argument from my corner that Microsoft sucks and Github sucks and that it would be great if there were a better home for community engagement with Qubes’ development.