Is there any icon in the VB tray indicating that mouse is captured by VB? For example, using Xephyr, if you press Ctrl+Shift, mouse is grab by Xephyr, and you're not allowed to move the mouse outside the Xephyr's window. I believe to remember that VB guest additions allow to move the mouse from guest to host without hitting the host key (the special key which disable the keyboard grabbing).. Maybe you have to disable this feature (if it exists).
Kind, Alexis Le jeu. 3 sept. 2015 à 20:26, Marc Petit-Huguenin <[email protected]> a écrit : > On 09/03/2015 11:54 AM, Greg Meyer wrote: > > This is interesting. I've had similar problems with VMs other similar > > software before. I'm not sure what the solution would be, unfortunately, > > but I would be interested to hear if you find one. > > > > My best guess would be this: VirtualBox grabs the mouse when you're in > the > > VM and releases it when you press the host key. > > According to the icon indicator at the bottom of VB, the keyboard is still > captured by VB, although the VB window is moving. That's why I suspect > that the problem is AWM somehow intercepting the event, although it should > not. > > > Is there any chance that > > your host key has been mapped to mod4? > > No, it is a different key (Alt during my tests). > > > > > Best, > > Thanks. > > > > > > > Greg Meyer > > > > gmmeyer.com > > > > @GMMeyer <https://twitter.com/@GMMeyer> > > > > 862 684 9101 > > > > [email protected] > > > > On Thu, Sep 3, 2015 at 12:02 PM, Marc Petit-Huguenin < > > [email protected]> wrote: > > > >> I am using a guest Linux instance with Awesome in Virtualbox. This > >> Virtualbox guest is itself running in a Linux host that is also using > >> Awesome. > >> > >> The Mod4 key works fine with key sequences in the guest - i..e. when > >> pressing Mod4+Enter, it opens a new terminal in the guest, not in the > >> host. This is when using Mod4+Mouse that things start to break: When I > try > >> to move a Window in the Guest, it is the VirtualBox window that moves. > >> > >> So my questions are: > >> > >> - Is there a possibility to fix this by configuration? > >> > >> - If not, where should I look to fix that? Would it be in the Awesome > >> running on the host, the Awesome running on the guest, VirtualBox or X?. > >> > >> Thanks. > >> > >> > >> > >> -- > >> To unsubscribe, send mail to [email protected]. > >> > > > > > > -- > To unsubscribe, send mail to [email protected]. >
