virtualbox.org

---

[ModEdit; related ticket: #17783: NS_ERROR_ABORT on cue/bin CD image created with Isobuster]

---

I still had this problem in 5.2.12. After trying to import "broken" VM, UI becomes messed up even to the level of not showing version number in "about".

For me, it occured after trying to add "broken" cue sheet (.cue) as image file for cd-rom drive. Adding it to existing VM breaks UI immediately, but at this stage you can just quit without saving VM settings. That cue sheet is probably valid, but it doesn't work in Virtualbox.

Cue sheets support is a new feature in 5.2.

Workaround: remove entry for that broken .cue from .vbox file with text editor.

I split your post from the thread "VirtualBox completely messed up for user, works for root":

• That was a thread from 4 years ago. That's way over the statute of limitation, even for dead threads.
• You didn't even have the same problem! The title of the original thread and your situation had absolutely nothing to do with each other!

kolen wrote:UI becomes messed up even to the level of not showing version number in "about".

That doesn't quite make sense, you got to describe the situation a little bit more detailed, "messed up" is too vague.

kolen wrote:That cue sheet is probably valid, but it doesn't work in Virtualbox.

If you don't know for sure... if you start with "probably valid"... I could say "probably invalid". We have a 50-50 chance of being right...

If the .cue file is really valid, then VirtualBox should accept it. If the .cue file is not valid, then VirtualBox should gracefully reject it. In either case, we need more details. For example the .cue file would be a good start, to see whether it's valid or not.

Then, complete details about your host and your VirtualBox version. Please note, "the latest" is *not* a version, so isn't "Ubuntu", "Fedora", or "fully updated". We need versions, builds, revisions. For VirtualBox in particular, post the output of:

• VBoxManage -version