VirtualBox

Ticket #19593 (new defect)

Opened 3 months ago

Last modified 5 weeks ago

VM window movement broken with Linux-Mate distros and Auto capture keyboard enabled

Reported by: mrvstudio Owned by:
Component: guest additions/x11/graphics Version: VirtualBox 6.1.8
Keywords: mate auto capture keyboard window Cc:
Guest type: Windows Host type: Linux

Description

Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8

Data: ubuntu 20.04 LTS Virtualbox Versión 6.1.8 r137981 (Qt5.12.8) VirtualBox_Extension_Pack-6.1.8 Tested in Desktop Mate kernel 5.4.0-29-generic OpenGL version string: 4.6 Mesa 20.2.0-devel

Change History

comment:1 Changed 3 months ago by mrvstudio

according to the changelog 6.1.8: Guest Additions: Fixed resizing and multi monitor handling for X11 guests. (6.1.0 regression; bug #19496), but the problem is not fixed yet

echo $XDG_SESSION_TYPE

x11

uname -a

Linux mrv 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -crid

Distributor ID: Ubuntu

Description: Ubuntu 20.04 LTS

Release: 20.04

Codename: focal

Desktop: Mate - Metacity (Marco) -

dpkg -l | grep virtualbox

ii virtualbox-6.1 6.1.8-137981~Ubuntu~eoan amd64 Oracle VM VirtualBox

lsmod | grep vbox

vboxnetadp 28672 0

vboxnetflt 28672 0

vboxdrv 487424 2 vboxnetadp,vboxnetflt

vboxmanage --version

6.1.8r137981

sudo modprobe -v vboxdrv

empty

dmesg | tail

vboxdrv: 0000000000000000 VMMR0.r0

vboxdrv: 0000000000000000 VBoxDDR0.r0

vboxdrv: 0000000000000000 VBoxEhciR0.r0

VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)

3D: The problem always happens. It doesn't matter if 3D acceleration is selected or not, and it happens in all modes (VBoxSVGA, VMSVGA, VboxVGA)

Hardware:

Resolution: 1366x768

CPU: Intel i5-6200U (4) @ 2.800GHz

GPU: Intel Skylake GT2 HD Graphics

Memory: 31977MiB

Last edited 3 months ago by mrvstudio (previous) (diff)

comment:2 follow-up: ↓ 7 Changed 3 months ago by fbatschu

Is your Ubuntu guest running Xwayland by any chance instead of Xor? I cannot reproduce this on my own Ubuntu 20.04 guests.

comment:3 Changed 3 months ago by fbatschu

also, the ticket claims host: Linux, guest: Windows but it seems that you are describing a Linux guest problem? Which is it now?

comment:4 Changed 3 months ago by openminded

Same Issue here!

VirtualBox 6.1.8

Host: Ubuntu 20.04

Guest: Windows 10

Graphics Controller: VBoxSVGA

The issue can be fixed by selecting Graphics Controller "VBoxVGA". Shutdown Windows properly by the operating systems shutdown procedure. However, VBoxVGA has some drawbacks (e.g. missing 3D acceleration).

comment:5 Changed 3 months ago by fbatschu

There must be more to it, I am running similar config without problems:

Host: Ubuntu 20.04
Guest: Windows 10 Version 1909 OS Build 18363.836
Virtualbox 6.1.8
Graphics Controller: VBoxSVGA _without_ 3D Accel.

and screen resizing of the Windows guest works.

So what Windows versions have you been running where problems happened and was 3D acceleration turned on or off?

comment:6 in reply to: ↑ description ; follow-up: ↓ 9 Changed 3 months ago by fbatschu

Replying to mrvstudio:

Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8


I guess I know what problem you run into, it's specific to Mate distros. please try to disable the following feature:

File->Preferences->Input->[ ] Auto capture keyboard

Once turned off, you should be able to move the guest window around with the mouse again, pls check this.

comment:7 in reply to: ↑ 2 ; follow-up: ↓ 8 Changed 3 months ago by mrvstudio

Replying to fbatschu:

Is your Ubuntu guest running Xwayland by any chance instead of Xor? I cannot reproduce this on my own Ubuntu 20.04 guests.

X11, PC Ubuntu 20.04, VM Windows

Last edited 3 months ago by mrvstudio (previous) (diff)

comment:8 in reply to: ↑ 7 Changed 3 months ago by fbatschu

Replying to mrvstudio:

Replying to fbatschu:

Is your Ubuntu guest running Xwayland by any chance instead of Xor? I cannot reproduce this on my own Ubuntu 20.04 guests.

Please read the information provided which is quite detailed well (hardware and software). There it says very clearly that I am working on x11 and that the PC is Ubuntu 20.04 and the VM is Windows.


Please read the information provided in #19496 which is quite detailed . There it says very clearly that this is a problem with Linux _guests_ not with Linux _hosts_. You report a problem on a Linux _host_ for a Windows _guest_ wrongly citing #19496 in the quite detailed information you provided.

comment:9 in reply to: ↑ 6 ; follow-up: ↓ 10 Changed 3 months ago by mrvstudio

Replying to fbatschu:

Replying to mrvstudio:

Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8


I guess I know what problem you run into, it's specific to Mate distros. please try to disable the following feature:

File->Preferences->Input->[ ] Auto capture keyboard

Once turned off, you should be able to move the guest window around with the mouse again, pls check this.

@fbatshu. Sorry for my comments and Thanks a lot. It Works!.... But it's still a BUG

Last edited 3 months ago by mrvstudio (previous) (diff)

comment:10 in reply to: ↑ 9 Changed 3 months ago by fbatschu

Replying to mrvstudio:

Replying to fbatschu:

Replying to mrvstudio:

Issue: The guest window doesn't resize and doesn't move. It is embedded in the upper left corner of the desktop. This problem was also found in version 6.1.6 (ticket 19496) and was not fix in version 6.1.8


I guess I know what problem you run into, it's specific to Mate distros. please try to disable the following feature:

File->Preferences->Input->[ ] Auto capture keyboard

Once turned off, you should be able to move the guest window around with the mouse again, pls check this.

Thanks a lot fbatshu. Works!.... But it's still a BUG


Yes, I know I should have filed a bug on this already describing the problem and the workaround, we only found out about this bug which is very specific to Mate distributions 2 weeks ago.

comment:11 Changed 3 months ago by fbatschu

  • Summary changed from Virtualbox 6.1.8 guest screen resize broken to VM window movement broken with Linux-Mate distros and Auto capture keyboard enabled

comment:12 Changed 3 months ago by fbatschu

  • Keywords mate auto capture keyboard window added

comment:13 Changed 5 weeks ago by HarryM

I have encountered a very similar problem, though only once. I have not been able to reproduce it. The only difference is that I am running XFCE 4.12 on my host desktop, not Mate. After trying to manipulate the guest window a few times, the entire host desktop became unresponsive.

I was able to "correct" this by opening up a console on the host and calling vboxmanage to shut the VM down. Then I was able to re-start the guest and all has been well since then.

I do have auto capture keyboard enabled, but that was because I had been having problems with VMs not responding to keyboard input and I *thought* perhaps this might help. What would happen is that, intermittently, a guest would not respond to keyboard input (but mouse worked fine in guest) and I would have to switch from full screen mode to windowed mode and then back to full screen so that I could input keys again in the guest. I may not fully understand the meaning of this option, but I thought it worth a try.

My host is Devuan Ascii (2.1) on Vbox 6.1.10 (all guests have updated GAs), though I had the same keyboard problem in 6.0 (I don't recall this in 5.x however). I run about 6 or so guests on an 8-core AMD FX cpu. Most VMs only get 1 vcpu allocated to them.

If you feel this is a different issue, please feel free to move this comment to a different ticket. But please do not cancel it altogether. This *might* be related to the current issue; the symptoms are very similar even if the cause slightly different. Either way, this is a Vbox problem and deserves proper treatment. BTW, I discovered this ticket only by googling for a kernel message which has appeared several times in the past day or so on the host. (The message was "VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)"). I am happy to supply additional information.

Last edited 5 weeks ago by HarryM (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use