VirtualBox

Opened 8 years ago

Last modified 22 months ago

#15649 new defect

Can no longer switch screens using mini toolbar

Reported by: s23ayers Owned by:
Component: other Version: VirtualBox 5.1.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

I just upgraded to v5.1 and can no longer switch screens using the mini-toolbar command View | Virtual Screen 1 | Use Host Screen X. I am running the VM in full screen mode. When I choose "Use Host Screen 2" nothing happens. No errors.

I can switch out of full screen mode, I can drag the VM to my second monitor and reenter full screen mode. But moving the VM to another monitor via. the mini toolbar menu no longer works for me.

Windows 8.1 host with multiple monitors

Windows 7 VM, with a single monitor

Attachments (2)

VBox.log (79.6 KB ) - added by s23ayers 8 years ago.
Logs-Tesseract.zip (41.4 KB ) - added by Tesseract 8 years ago.

Download all attachments as: .zip

Change History (18)

by s23ayers, 8 years ago

Attachment: VBox.log added

comment:1 by John JJ, 8 years ago

I found that this problem (as well as others) went away if I disabled 3D acceleration.

https://www.virtualbox.org/ticket/15603

comment:2 by Tesseract, 8 years ago

I have the same problem. My host is Windows 7 Ultimate SP1, 64-bit, with two monitors. My guest is Windows 7 Ultimate SP1, 64-bit, with one virtual monitor, but I can reproduce the problem with no guest OS, ie just an empty virtual disk and the virtual bootloader (and one virtual monitor).

I do not have 3D acceleration enabled on any VM.

While in full-screen mode, if I select the other host screen from the mini toolbar nothing happens (the VM does not move the selected screen), but if I switch off full-screen then switch it back on, the VM appears on the selected host screen.

Attached Logs-Tesseract.zip has the logs for a session with an empty virtual disk and just the virtual boot loader, in which I:

  • Start VM, full-screen on monitor 1
  • Select "Use Host Screen 2" (and nothing happens, the VM does not move to the other monitor)
  • Disable full screen
  • Enable full screen (now the VM is on monitor 2)
  • Power off the VM

This bug did not exist in VirtualBox 5.0.24

An extra piece of information that might be relevant... With VirtualBox 5.0.x (and every version since 4.3.20) my host screen numbers were reversed, as described in https://www.virtualbox.org/ticket/13749, but with 5.1.0 that problem seems to have been fixed - ie Virtual Box's host screen numbers match the monitor numbers as shown by Windows.

by Tesseract, 8 years ago

Attachment: Logs-Tesseract.zip added

comment:3 by John JJ, 8 years ago

s23ayers,

I do have that same issue without 3D enabled and didn't notice it before.

With 3D enabled the option is ignored completely. Cycling full screen has no affect.

I also noticed that the root menu always reads "Virtual Screen 1", which just may be hard coded, but then it shouldn't have the "1" in the menu entry.

comment:4 by AlD, 8 years ago

Is there any information on this issue?

I have the same problem. I have recently updated from 5.0.14 to 5.1.8.

My host is Windows 7 Pro SP1 64-bit. The issues exists with or without 3D acceleration.

Interestingly, in contrast to Tesseract's comments above, my screen number is now reversed w/r/t the screen number on the Windows host. In 5.0.14 and earlier they were not reversed.

comment:5 by FstTesla, 8 years ago

I have the same problem. It appeared with version 5.1.0.

Disabling full screen and re-enabling it, the changes I have made using the toolbar are applied correctly.

comment:6 by Zeppe, 7 years ago

This impacts me as well. Still present in the latest test build (as of today): 5.1.11-112223

comment:7 by s23ayers, 7 years ago

Just a note to say the bug still exists in 5.1.14

in reply to:  description comment:8 by Hans Vledder, 7 years ago

As well as in 5.1.16 ...

Windows 10 Pro host Any guest

comment:9 by Hans Vledder, 7 years ago

I just noticed that support for 5.0 is running out. However, I decided not to upgrade to 5.1 until this issue is fixed. Nor will my team.

in reply to:  9 comment:10 by Socratis, 7 years ago

Replying to Hans Vledder:

I just noticed that support for 5.0 is running out.

May I ask where did you see that? AFAIK, the 5.0.x series is still getting fixes and updates. In fact the latest 5.0.x version (5.0.36) was released on 2017-03-16, just one day after the latest 5.1.x version (5.1.18).

Maybe by support you mean that you have a support contract?

comment:11 by Hans Vledder, 7 years ago

Hi socratis,

Please have a look here. The red line at the top of the page: https://www.virtualbox.org/wiki/Download_Old_Builds_5_0

Regards, Hans

comment:12 by Socratis, 7 years ago

@Hans Vledder
Ah, OK, didn't notice that. Thanks for the information. I wonder what that really means in terms of the majority of users which don't have "support".

To answer my own question, most probably it means that if a bug is fixed it's not going to be back-ported (actively/aggressively) to older versions or tested extensively, except maybe if it's trivial or security related. Unless you do have "support" in a form of a "support contract".

comment:13 by Frank Mehnert, 7 years ago

To answer this question: VBox 5.0.x will run out of support soon. That means that there will be no security updates and also no trivial updates once the EOL is reached. Neither for normal users nor for paying customers.

VirtualBox 5.0.x and 5.1.x are both part of the major VirtualBox 5.x release so technically speaking the upgrade from 5.0.x to 5.1.x is a minor update.

comment:14 by Hans Vledder, 7 years ago

This issue is still keeping me from upgrading to 5.1 or 5.2. Anyone any idea when it will be fixed?

in reply to:  14 comment:15 by Socratis, 7 years ago

Replying to Hans Vledder:

Anyone any idea when it will be fixed?

I don't think that you're going to get a promise for a future date fix, here or anywhere else where developers are involved. Those things are never, ever promised. The following, original workaround doesn't work for you?

From the original report:

I can switch out of full screen mode, I can drag the VM to my second monitor and reenter full screen mode.

comment:16 by mgrzegor, 22 months ago

I have been having the same issue (with a Windows 10 host and a Linux guest, but as noted in comment:2 it occurs even without any guest OS) since version 5.1.8. I reported my reproduction steps in #16547, which appears to be a duplicate. (Also, I use the pop-up menu instead of the mini-toolbar.)

The workaround mentioned in comment:2 works for me, too (as does switching to the scaled mode then back to the full-screen mode), but the bug is definitely annoying as I switch the VM between my two monitors quite often.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use