Opened 8 years ago
Last modified 8 years ago
#15813 new defect
Windows Guest crashes when opening keyboard settings on Mac Host
Reported by: | brianthesmith | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 5.1.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description
Host: Mac OS X 10.11.6 - MacBook Pro (Retina, 15-inch, Late 2013) Guest: Windows 7 64-bit VirtualBox version: 5.1.4 r110228 (Qt5.5.1)
When opening the Keyboard --> Keyboard Settings menu item the Guest immediately crashes. I have observed this in 5.1.2, 5.1.3 as well. I am new VirtualBox user so I can't confirm this wasn't also present in older versions.
I have attached a snippet of the VirtualBox Log from Guest Startup to crash when opening the menu item. It doesn't look terribly helpful.
Attachments (2)
Change History (8)
by , 8 years ago
Attachment: | VirtualBoxCrashLog.log added |
---|
comment:1 by , 8 years ago
Error 404: File not found.
You didn't attach the log. But that may turn out to be a good thing, because the whole VBox.log is needed, after you completely shut down the VM (or it crashes). Zip it before attaching it.
comment:2 by , 8 years ago
The same behavior is present when booting my CentOS 6.5 guest. Does not seem to be tied to the guest at all.
comment:3 by , 8 years ago
Oh, now I get it. Input -> Keyboard -> Keyboard preferences, as in VirtualBox VM preferences. Then the VBox.log I'm afraid is not of too much use. I distinctly remember a recent issue where a Mac user had a similar problem when they were launching the preferences of the program. I'll try to find it along with the solution (hopefully). Please check if you have a crash in the General VirtualBox preferences as well.
In the meantime, would you mind posting the "~/Library/VirtualBox/VirtualBox.xml" file, where "~" is your user home directory? That's where all the keyboard settings are stored and something there might not be right.
comment:4 by , 8 years ago
Found it! It is #15617 and the root cause is Karabiner, which has a beta that addresses the issue. Is the same thing happening in your case?
VirtualBox Log file