I checked to see if I had any restore points for Virtual Box. I had two restore points for Oracle Virtual Box. I did a system restore back to the latest previous version. I have one more older restore point for Oracle Virtual Box which would restore me back to the version I have before Version 6.1.32; but so far my Ubuntu system now seems stable.
VirtualBox Graphical User Interface Version 6.1.32 r149290 (Qt5.6.2) Copyright © 2022 Oracle Corporation and/or its affiliates. All rights reserved. My terminal screen inside Ubuntu-20.04.2.0 says the following: jmsigler2@JMSigler2-VirtualBox:~$ lsmod | grep vboxguest vboxguest 368640 6 vboxsf jmsigler2@JMSigler2-VirtualBox:~$ /usr/sbin/VBoxService --version 6.1.34r150636 jmsigler2@JMSigler2-VirtualBox:~$ lsb_release -r Release: 20.04 jmsigler2@JMSigler2-VirtualBox:~$ VBoxClient --version 6.1.34r150636 jmsigler2@JMSigler2-VirtualBox:~$ gcc --version gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. So, at this point, a have a newer version of VirtualBox Guest Additions inside Ubuntu-20.04.2.0 even though I am running VirtualBox Graphical User Interface Version 6.1.32. I may try to resync/reload the VirtualBox Guest Additions in Ubuntu to match the VirtualBox Graphical User Interface, Version 6.1.32 r149290 (Qt5.6.2). I have not decided whether to do that or not. I have loaded VirtualBox Guest Additions a number of times now to know that the it unloads the old version and then loads the new version in Ubuntu. Right now, all seems stable, regardless. I think I will leave it alone for now, and seem what happens. For now, the unstable error messages for VirtualBox 6.1.34r150636 are gone. --------------------------------- My System - DELL Latitude E6420 --------------------------------- OS Name Microsoft Windows 10 Pro Version 10.0.18362 Build 18362 OS Manufacturer Microsoft Corporation System Manufacturer Dell Inc. System Model Latitude E6420 System Type x64-based PC Processor Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2801 Mhz, 2 Core(s), 4 Logical Processor(s) BIOS Version/Date Dell Inc. A24, 5/12/2017 SMBIOS Version 2.6 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer Dell Inc. BaseBoard Product 032T9K BaseBoard Version A02 Platform Role Mobile Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.18362.1171" Time Zone Central Daylight Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.9 GB Available Physical Memory 8.11 GB Total Virtual Memory 31.9 GB Available Virtual Memory 17.9 GB Page File Space 16.0 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Running Virtualization-based security Required Security Properties Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection Virtualization-based security Services Configured Virtualization-based security Services Running Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable A hypervisor has been detected. Features required for Hyper-V will not be displayed. Note: I have had some issues with Windows 10 Professional upgrades to Version = "10.0.19xxx. One issue is over the new Bluetooth driver Microsoft provides. When I listen to sounds I get crackling sounds with Bluetooth headphones. When I updated VirtualBox to Version 6.1.34 r150636 (Qt5.6.2), I think the software prompted me to update my Bluetooth device driver. Windows 10 | Bluetooth and other device settings is showing that I am using "BCM920702 Bluetooth 4.0", the older stable driver. On the other hand, Windows 10 | Device Manager is reporting that I have "Broadcom BCM20702 Bluetooth 4.0 USB Device", which had shown to be unstable for me. My Bluetooth is functioning okay right now. So, the new driver could loaded and fixed, and there is then a reporting problem in the "Bluetooth & other devices" settings; or the new driver is not loaded but reporting in Device Manager as such. This still looks like a Microsoft bug. I found a way to update the registry to block any major Microsoft Updates. I had to recover to the last major update a number of times. If you do not used the registry to block updates, the UI has a path only to delay major or minor updates which did not work for me. Maybe, after some time, I will try to update again to a newer major release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873922 Title: 20.04 not compatible with virtualbox-guest-x11: Fails changing display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1873922/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
