VirtualBox

Ticket #6727 (reopened defect)

Opened 4 months ago

Last modified 2 months ago

Host Window Manager (GNOME + Metacity) window shortcuts interfering with guest -> fixed in SVN

Reported by: crimsonflame123 Assigned to:
Priority: major Component: other
Version: VirtualBox 3.2.0 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

Configuration: Host - Fedora 12 Guest - WinXP VB - 3.2

When I switch to fullscreen/seamless mode in the guest, then I suppose the correct behavior should be that all the normal keyboard input should be directed to the guest (except 'Right Ctrl' - the host key). In my Window Manager on Fedora 12 (Gnome Metacity), I have plenty of keyboard shortcuts etc. configured for ease. However, these shortcuts should _not_ work when the guest is in full screen mode. Unfortunately they do.

Even Alt+F4 inside a fullscreen guest brings up the "Close VirtualBox" dialog instead of closing the intended app inside the guest. Surprisingly, on enabling compiz, everything works fine. This is a regression since VB 3.1.8 because it worked there.

I do not have a dual monitor setup.

More discussions on this during the BETA feedback process @ http://forums.virtualbox.org/viewtopic.php?f=15&t=30874&sid=3310ef2ed76465abbc47bb7cdcc39695

Attachments

VBox.log (46.2 kB) - added by crimsonflame123 on 2010-05-20 05:23:52.
VirtualBox Log File

Change History

2010-05-20 05:23:52 changed by crimsonflame123

  • attachment VBox.log added.

VirtualBox Log File

2010-05-31 00:59:10 changed by crimsonflame123

Its really a bummer using VB 3.2 in Full Screen mode with this bug. Cant even use Alt+F4 to close windows in my Guests. No workarounds from dev?

2010-05-31 10:31:52 changed by poetzsch

  • summary changed from Host Window Manager (GNOME + Metacity) window shortcuts interfering with guest to Host Window Manager (GNOME + Metacity) window shortcuts interfering with guest -> fixed in SVN.

This is fixed in SVN and the fix will be included in the next minor release.

2010-05-31 11:16:40 changed by crimsonflame123

Heartening. Thank you so much. I'll wait for the next beta.

2010-06-02 21:00:11 changed by frank

  • status changed from new to closed.
  • resolution set to fixed.

2010-06-03 22:16:45 changed by pavel

crimsonflame123, do you observe this fixed in 3.2.2?

Or is this still relevant due to similar #6769?..

2010-06-08 15:48:30 changed by frank

Please re-check the updated 3.2.4 build. A fix which might at least restore the old behavior made it into this release. Make sure that you install the latest build (3.2.4-62467).

2010-06-22 20:36:23 changed by Mori

  • status changed from closed to reopened.
  • resolution deleted.

I can understand the original reporter, because now I have his problem, only the other way around: it breaks my host shortcuts.

My setup: Two monitors, sawfish as the window manager. There's a Windows guest in fullscreen on Workspace two. No keyboard shortcut conflicts between Windows and sawfish.

Before the last update I could access Windows naturally and integrated into my environment. All I had to know was "Windows is on workspace 2".

Now, before switching to any other workspace i have to check

  • which workspace is active? Is it workspace 2?
    • If no: switch the workspace. Mission accomplished.
    • If yes, is there another window on the second monitor that has the focus?
      • If no: switch the workspace. Mission accomplished.
      • If yes, type host key, then switch workspace

(This could of course be shortened to "look if VirtualBox has the focus", but in reality that doesn't make it easier. Switching workspaces never was something I had to think about before!)

If I make an error, which happens regularly since 1 week, I either open the Windows help or a context menu (Host-key is the menu key). Needless to say, it drives me nuts.

This totally ruined my work flow. I realize that most people have conflicting shortcuts between the host and the guest, but even for them an exception for workspaces would be beneficial. I hope it was OK to reopen this bug for this.

2010-06-26 08:58:39 changed by frank

VBox 3.2.6 contains another workaround. How is the state of affairs now?

2010-06-27 21:33:13 changed by Mori

My problem seems to be that this bug is fixed, not that it isn't. Sorry, I guess I should have opened a new bug for this after all.

If I understand my problem correctly, I could only use my WM shortcuts because of a (this) bug in VBox. Now that this bug is fixed, I can't use my WM to manage the VBox window anymore.

3.2.6_OSE r63112, GNU/Linux, sawfish


Contact – Privacy policy