Scale mode broken since 4.2.4

[RickCHodgin]

Scale mode worked correctly in 4.2.2, is broken in 4.2.4 and 4.2.6.

Windows 7 Professional 64-bit SP1 host. Windows 7 Professional 32-bit SP1 guest.

Uninstalling and reverting back to 4.2.2 corrects the issue.

Host machine details: HP Pavilion dm4 Notebook PC Intel Core i5-2450, 2.50 GHz 6.00GB RAM

In 4.2.4 screen updates do not occur in scale mode (screen is black). In 4.2.6, screen updates occur occasionally and sporadically, and can be forced if you re-scale the window by slightly resizing it.

Bottom line: unusable in scale mode since 4.2.4.

[Alex]

Could you attach VBox.log from this guest please? I can't reproduce scale mode problem here.

[Mihai Hanor]

It could be a duplicate of #11341

[RickCHodgin]

from \users\rick\.VirtualBox\vboxsvc.log

[RickCHodgin]

After upgrading to 4.2.6, then back to 4.2.2, the scaling issues remain. I had updated the guest additions in the guest, and then uninstalled them and re-installed 4.2.2 guest additions. Still no go. I do not have scaling issue in Linux versions. Just since 4.2.4 and later on Win7 AMD64, and now 4.2.2 after upgrading to 4.2.6, and then down-grading to 4.2.2.

[Simón]

Same problem with same VirtualBox versions:
Hosts: Ubuntu 12.04 64 bits (Gnome-shell 3.4.1) and Ubuntu 12.10 64 bits (Gnome-shell 3.6.2).
Guests: Windows XP and Windows 7 32 bits.

Screenshots with Windows 7 Home Premium:

[Dsen]

Could you please check if the "2D video acceleration" or "3D acceleration" feature is enabled for the guest?

[RickCHodgin]

Yes, 2D and 3D acceleration were on. Turning them off seems to have fixed the problem. BTW, how did they turn on? I have not changed their settings. Will look for this in the future.

[Dsen]

Have no idea how each of these features could be auto-enabled. At least GUI should not do that automatically. BTW, which exactly of these two features provokes the scale-mode issue (I assume 3D one)?

[RickCHodgin]

Yes, I turned 2D back on and it worked correctly. I turned 3D on by itself and it was broken. Turning 2D and 3D and it is broken. I have now observed this behavior also dates back to at least 4.2.2.

[misha]

Most likely your problem is caused by that the Scale Mode does not work for 3D content.
It is not a regression, it has always been like this.
Most likely the reason you did not see this issue for older VBox versions is because 3D did not work properly for you with those versions and thus guest 3D desktop failed to activate for you.
The resent VBox versions have lots 3D improvements which I expect make guest 3D desktop (Aero) work in your guest thus making scaled mode not working for you.

Could you confirm/disclaim my above assumption? I.e. :

1. Using the recent VBox version that has Scale mode issues with 3D enabled, start the guest with 3D enabled and check whether you have Aero theme active in a guest when the Scale Mode does not work for you -> the Aero theme should be active.
2. Using the 4.2.2 VBox version that does NOT have Scale mode issues with 3D enabled, start the guest with 3D enabled and check whether you have Aero theme active in a guest when the Scale Mode does not work for you -> the Aero theme should NOT be active.

We are planning to make the Scale Mode work for 3D as well in the future, so if my guess is confirmed, I propose to change the summary of this bug report and use this report for tracking Scale Mode for 3D issues.

[RickCHodgin]

For my guests, I am running Windows Server 2003, Windows 2000, and a few versions of Linux (so no Aero mode). Also, I did find out that 4.2.2 is also affected. It wasn't affected previously (I think) because the checkbox for 3D acceleration wasn't set. After upgrading to 4.2.6, then back to 4.2.2, it kept the checked setting 4.2.6 introduced. Un-checking in 4.2.2, 4.2.4, 4.2.6 and now 4.2.8 all work correctly.

[misha]

Please provide ​VM log files for the case scale mode working (i.e. 3D disabled) and not (3D enabled) using the latest VBox 4.2.8 Release.

[RickCHodgin]

From Toshiba Satellite AMD 4-core laptop running 4.2.12

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.