VirtualBox

Opened 7 years ago

Last modified 19 months ago

#16547 new defect

Full screen mode only displays on 1 screen

Reported by: Jaques Owned by:
Component: GUI/multiview Version: VirtualBox 5.1.16
Keywords: full screen, use wrong host screen Cc:
Guest type: Windows Host type: Windows

Description

I've just upgraded to 5.1.16 hoping this problem will be resolved. When running my guest in full screen, it only displays on one of my screens (Screen 2). Does not matter if I select a different screen under View -> Virtual screen 1 -> Host host screen 1/2

If I plug screen 2 out, then it works, but the moment I plug it in, it goes back to screen 2

Change History (14)

comment:1 by Jaques, 7 years ago

I used 5.0.32, and that worked, and I did use 5.1.8 I think, but rolled back because of the critical error that occurred when using ALT-TAB in the guest, and that is why I hesitated to upgrade to 5.1. I've upgraded to 5.1.14 on 27/2/2017 and that is where the problem started

comment:2 by mgrzegor, 7 years ago

Same (I think) problem here — selecting a different screen does nothing. (Almost always, that is; I tend to move a full-screen VM between screens several times a day, so I must have done so a couple of thousand times now since I upgraded to 5.1, and it worked, randomly, less than 10 times without having to use the below mentioned workaround.)

The bug has been present since at least 5.1.8. It never occurred in the 5.0.x line.

Reproduction steps:

  • Prerequisite: Windows 10 64-bit with 2 displays connected.
    • In case it makes a difference, on my PC the two displays are connected to different adapters.
  • Create a new virtual machine of type Ubuntu 64-bit. Leave all options set to default.
  • Start the virtual machine. Cancel the installation CD prompt. (The virtual machine’s BIOS will display an error message because the virtual HD is empty at this point.)
  • Switch to full screen mode.
  • On the menu bar, select View -> Virtual screen 1 -> Use host screen 2 (or 1 if 2 was selected originally).

Workaround: after the last step, leave full screen mode (e.g. switch to scaled mode), then switch back to full screen mode.

Last edited 19 months ago by mgrzegor (previous) (diff)

comment:3 by mgrzegor, 6 years ago

The bug still occurs as of 5.2.2. (The above mentioned workaround still works, too.)

comment:4 by mgrzegor, 6 years ago

Bug still present as of 5.2.6.

comment:5 by mgrzegor, 6 years ago

Bug still present as of 5.2.8.

comment:6 by mgrzegor, 6 years ago

Bug still present as of 5.2.12.

comment:7 by mgrzegor, 6 years ago

Bug still present as of 5.2.14.

comment:8 by mgrzegor, 6 years ago

Bug still present as of 5.2.18.

comment:9 by mgrzegor, 5 years ago

Bug still present as of 5.2.20.

comment:10 by mgrzegor, 4 years ago

Bug still present as of 6.0.14.

comment:11 by mgrzegor, 4 years ago

Bug still present as of 6.0.16.

comment:12 by mgrzegor, 4 years ago

Bug still present as of 6.1.14.

comment:13 by mgrzegor, 3 years ago

Bug still present as of 6.1.22.

comment:14 by mgrzegor, 19 months ago

Bug still present as of 6.1.36.

#15649 appears to be the same issue.

Last edited 19 months ago by mgrzegor (previous) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use