I've installed Virtual Box 6.1 from Discover (KDE app installer).
If I attempt to change vm default directory, I get a frozen dialog window.
It seems like a screenshot and I cannot select any element.
The only operation allowed is to close the dialog.
How can I solve?
Thanks
KDE Neon - Dialog change vm default directory don't work
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: KDE Neon - Dialog change vm default directory don't work
There are a few steps in the "change the default VM folder" process. Please post a screenshot of exactly where the process seizes up. Please use the forum's Attachments tab to post the picture.
Re: KDE Neon - Dialog change vm default directory don't work
The Dialog highlighted in red is frozen.
I can only close it with the upper right X.
I can only close it with the upper right X.
- Attachments
-
- VirtualBox - Change default dialog problem 2.png (109.94 KiB) Viewed 1454 times
Re: KDE Neon - Dialog change vm default directory don't work
Any suggestions about the cause of the problem and possible solutions?
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: KDE Neon - Dialog change vm default directory don't work
I can only present a general idea with a well constructed example:
VirtualBox and the host OS work together to populate the contents of the dialog, which include the visible and invisible parts of the displayed hierarchies. If for example there was a link to a network share that is currently unreachable or takes a long time to reach (e.g. DNS requests can take 30 seconds or even minutes), this population process could take a long time.
The basic idea is to question if the file system tree contains something unusual in the sense that not all users have it.
VirtualBox and the host OS work together to populate the contents of the dialog, which include the visible and invisible parts of the displayed hierarchies. If for example there was a link to a network share that is currently unreachable or takes a long time to reach (e.g. DNS requests can take 30 seconds or even minutes), this population process could take a long time.
The basic idea is to question if the file system tree contains something unusual in the sense that not all users have it.