Seamless/Fullscreen weirdness

[IMoffensive]

Running Virtualbox 4.3.18 (latest release) on OS X (10.10) With a guest OS running, I frequently hit command-L (unintentionally: that's the same key stroke that puts the cursor in the address bar on all Mac web browsers) which then puts my guest OS in "seamless mode." Now my virtual machine is running a full desktop but the overall window no longer has any borders or titlebar. Hitting command-L again has no effect and I cannot seem to get back to normal operation. I am also unable to go to fullscreen mode either. I've tried toggling seamless mode from the VirtualBox menu but it doesn't seem to make any difference either. The only way out of this predicament is to shut down the guest OS and then start the VM back up. Am I missing something here? How do I get my VM unstuck?

[loukingjr]

I'm running 4.3.18 in OSX 10.10. When I hit 'Host'+L (left cmd+L) it switches my guest to seamless mode which it's supposed to. if I hit it again it switches back to windowed mode. Make sure Auto-Resize guest is checked.

Which guest are you running? Please attach the latest compressed vbox.log file.

[IMoffensive]

I'm running 4.3.18 in OSX 10.10. When I hit 'Host'+L (left cmd+L) it switches my guest to seamless mode which it's supposed to. if I hit it again it switches back to windowed mode. Make sure Auto-Resize guest is checked.

Which guest are you running? Please attach the latest compressed vbox.log file.

It doesn't switch back for me. After posting this, I found a workaround - removing the shortcut from the input settings. At least that prevents me from accidentally switching into seamless mode.

Using Ubuntu as the guest OS in this case. I am curious as to why it doesn't work properly. I've attached a gzipped copy of the log file. The error seems to occur around 17:42:24.

[loukingjr]

I thought about your problem. There seems to be a few people who have had random issues with VirtualBox since updating to OSX 10.10. What fixed one person's problem was to reinstall VirtualBox. So what I would try is use the VirtualBox_Unintall.tool to uninstall VB and reinstall it. It can't hurt anything and it might fix your problem.