VirtualBox Manager for 5.2 nonfunctional
Posted: 20. Oct 2017, 05:12
Hello all,
Earlier this evening I installed VirtualBox 5.2 on my Fedora 26 machine using the x86_64 rpm package from the Downloads page. I had to uninstall my previous version of VirtualBox, 5.1-30, to complete the installation. The Expansion Pack installed without complaint. However, after opening the VirtualBox Manager I found that trying to open the Settings window would fail and the Manager would lock up and accept no input. The lockup occurred as soon as I clicked the Settings button - the Settings window did not even begin to appear. I got the same result trying to open the Settings window using the Machine menu. Eventually I would have to have Linux terminate the Manager. I tried restarting Fedora's Gnome desktop, rebooting Linux and trying to uninstall and reinstall 5.2. Nothing helped. As I describe below, I couldn't even uninstall the 5.2rpm package. For what it's worth, my Windows 10 VM appeared to run just fine and the 5.2 Guest Additions for Windows also installed with no difficulty. I need to adjust the window size of the VM when I display it on my laptop screen, so the problem with the Manager is a show-stopper.
Perhaps even more strange, when I tried to uninstall 5.2 with the rpm tool, rpm claimed that VirtualBox 5.2 was not installed! I need a functioning VBox system immediately, so I then installed 5.1-30 without having had 5.2 removed, again using the rpm package from the 5.1 Downloads page. That installed without complaint - no file conflicts to resolve like I experienced when I tried to install 5.2 before uninstalling my earlier version. The Manager works as expected under 5.1-30. The Settings windows pops open with no difficulty. My Windows 10 VM runs well under 5.1-30, but the 5.2 version of Guest Additions is still installed and the .iso for the 5.1-30 version is gone; only the 5.2 version of the .iso appears. I guess I'll have to remove the 5.2 .iso by hand and reinstall 5.1-30.
Has anyone else experienced lockups trying to open the Settings window on 5.2 running on a Fedora or other Linux host? Any insights appreciated!
Darron
Earlier this evening I installed VirtualBox 5.2 on my Fedora 26 machine using the x86_64 rpm package from the Downloads page. I had to uninstall my previous version of VirtualBox, 5.1-30, to complete the installation. The Expansion Pack installed without complaint. However, after opening the VirtualBox Manager I found that trying to open the Settings window would fail and the Manager would lock up and accept no input. The lockup occurred as soon as I clicked the Settings button - the Settings window did not even begin to appear. I got the same result trying to open the Settings window using the Machine menu. Eventually I would have to have Linux terminate the Manager. I tried restarting Fedora's Gnome desktop, rebooting Linux and trying to uninstall and reinstall 5.2. Nothing helped. As I describe below, I couldn't even uninstall the 5.2rpm package. For what it's worth, my Windows 10 VM appeared to run just fine and the 5.2 Guest Additions for Windows also installed with no difficulty. I need to adjust the window size of the VM when I display it on my laptop screen, so the problem with the Manager is a show-stopper.
Perhaps even more strange, when I tried to uninstall 5.2 with the rpm tool, rpm claimed that VirtualBox 5.2 was not installed! I need a functioning VBox system immediately, so I then installed 5.1-30 without having had 5.2 removed, again using the rpm package from the 5.1 Downloads page. That installed without complaint - no file conflicts to resolve like I experienced when I tried to install 5.2 before uninstalling my earlier version. The Manager works as expected under 5.1-30. The Settings windows pops open with no difficulty. My Windows 10 VM runs well under 5.1-30, but the 5.2 version of Guest Additions is still installed and the .iso for the 5.1-30 version is gone; only the 5.2 version of the .iso appears. I guess I'll have to remove the 5.2 .iso by hand and reinstall 5.1-30.
Has anyone else experienced lockups trying to open the Settings window on 5.2 running on a Fedora or other Linux host? Any insights appreciated!
Darron