These VMs are running in my Ubuntu 2022.04 LTS Host OS (Lenovo Thinkpad T14S). On Thursday (01.09.22) I started experiencing similar problems as the one described by the OP with my VirtualBox 6.1.34 in all my guest OS (Windows, Ubuntu2016, Ubuntu 2018 and CentOS 8). There are already bug reports popping up that I would bet are related, like this for example: /msg486212.html Disabling compositing or even using a different window manager also had no effect, also disabling 3D acceleration of the VM did not help. It was not only Chrome that was crashing, it also affected Firefox (that one crashed even more often than Chrome), also other apps were crashing, for example Telegram, and even the entire Plasma shell has crashed once or twice already. I will leave it that way until I know the problem is solved and then install the meta package again. This will then also automatically uninstall the meta package linux-image-generic and this should prevent any further kernel upgrades, and this way I also don't have to mess with grub defaults and I can be sure it won't eventually automatically purge the last working kernel. This left me with the -46 kernel as the default boot option, which is still installed.įor some reason the -unsigned package keeps popping up unless you purge it in the same command alongside with the normal linux-image. I temporarily did the following: apt purge linix-image-5.15.0-47-generic linux-image-unsigned-5.15.0-47-generic Until I tried booting the host (not the guest) with the previous kernel version and all problems disappeared. I lost almost a day trying all kinds of things, trying to find a reliable pattern to reproduce it or browser-settings to prevent it. Yes, same here, except that I am using a Kubuntu guest on a Kubuntu host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |