But I also had noticed a week prior that chrome was not showing, for example, the live chat popup button on amazon.com. with no extensions nothing. ah no they probably changed their chat to allow some non https connection or something I bet. and in the default disposable I use with firefox that is not the case. sorry fro the stream of consciousness.
Regardless, I'm still using firefox for right now cause the freezing in the suspect vms has not happened with firefox for some reason. Over the years I always go back and forth to whichever one is less abused for the current time being.
But I'm so paranoid right now I'm gonna wipe the entire system. Actually even keepassx vault froze on me... I hope its just a hardware failure, fedora is good about monitoring hdd though...but yikes.
anybody have any encouraging words for me? lol.
delete this thread please don't know why I posted it. Its obviously more then a google chrome and chromium issue. I don't think its hardware issue cause its program affected, or maybe its vm affected I didn't even try to open terminal when it happened, not that it matters at this point, also probably worth checking the memory chips at least.
Is it possible to run a memory checker from a usb stick? Anybody got a recommended program to use i haven't used one in years. maybe my bios has a checker.
you becoming my favorite poster man Ty for being part of Qubes.
yes I think I noticed this too. When I got the freeze instead of shutting down vm I launched the terminal from it. was going to kill process and then realized it was working again.
The machine this is happening on has 500gb ssd and 16gb ram, iommu on, intel gpu, intel 5 cpu.
Another machine doesn't have this issue, and it has no iommu, no ssd, and old amd cpu, older nvidia gpu. This machine also never got the missing kernel bug. And has had no restored backup vms.
Legacy boot on both.
In fact I wonder if the freezing is happening on those vms that were affected. Because it happened when updating my fedora-24 clone from the qubes-manager gui. When I went to hit enter to close the vm, window was frozen so I manually shut it down. This hasn't happened on any of the other templates, and in fact, this was the only template that had a missing kernel problem. Could it be related? Never had any freezing before the day of dom0 update.
none of my untrusted vms were affected with the dom0 update bug. I will start using chrome in them and see if it freezes.
And yes I can confirm what Reg Tiangha said... I opened a gnome-terminal when the update froze. And as soon as I did that you could see the y's pop on the screen I was hitting for yes to update. But then both terminals froze. So I simply just once again opened a second gnome-terminal and they everything unfroze immediately and updates kicked into action.
No idea what that means but hopefully thats a clue for a dev.
Ya I don't think this is related to the missing kernel issue, or at least that wasn't the direct cause it seems.