VirtualBox

Ticket #17168 (new defect)

Opened 2 years ago

Last modified 3 months ago

VB display frame and content are no longer bound in High Sierra (osx 10.13)

Reported by: jimoe Owned by:
Component: GUI Version: VirtualBox 5.1.28
Keywords: high sierra, display, gui Cc:
Guest type: all Host type: Mac OS X

Description

OSX High Sierrra 10.13 Windows 8.1 Guest (and others)

After upgrading to High Sierra, the display frame and display content are no longer bound together. When I drag using the title bar, only the frame moves exposing a black window behind the guest's content which has remained in place.

It is possible to re-sync the two either by minimizing/restoring the window, or the Display icon -> "Adjust Window Size" option.

Attachments

virtualbox-log.txt Download (95.0 KB) - added by pzrq 23 months ago.
VirtualBox Log File
Screen Shot 2017-12-29 at 11.13.38 pm.jpg Download (298.0 KB) - added by pzrq 23 months ago.
Example screenshot of results after clicking and dragging

Change History

comment:1 Changed 2 years ago by socratis

Or another workaround it to Hide/Show the VM window. Or you can disable 3D acceleration. Known issue since the early 10.13 betas.

comment:2 Changed 2 years ago by jimoe

Thank you. Disabling 3D acceleration has made Vbox useful again.

comment:3 Changed 2 years ago by ncj

This issue is present in VB 5.2.2, on macOS 10.13.1. Given the symptoms and resolution techniques, it may be related to https://www.virtualbox.org/ticket/17180.

comment:4 Changed 2 years ago by socratis

@ncj
No it's not. #17180 is a completely different problem. Not to confuse the two.

comment:5 Changed 2 years ago by socratis

Just for completion, here are all the possible workarounds:

  • Minimize/Restore the VM window.
  • Hide/Show the VM window.
  • Menu Display » Adjust window size (HostKey+A).
  • Disable 3D acceleration.

Changed 23 months ago by pzrq

VirtualBox Log File

Changed 23 months ago by pzrq

Example screenshot of results after clicking and dragging

comment:6 Changed 19 months ago by jhawksley

I have disabled 3D acceleration on this and it does work. Could we get some attention on this - maybe it's a simple fix? (hope springs eternal). Many thanks!

comment:7 Changed 19 months ago by socratis

Thanks @jhawksley, but this workaround was already listed seven months ago! It could help if you read the whole ticket, and the comments too...

As to why it's not "fixed", 1) it's not a simple fix (how do you know, did you find the source of the problem?) and 2) there are way more important things to address than a cosmetic issue with four known workarounds...

comment:8 Changed 19 months ago by jhawksley

@socratis Thank you for your response, which was ... very enlightening :-)

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

comment:9 Changed 18 months ago by socratis

Can an admin please change the "Host type:" to "OSX" from "Other"? I was trying to find all open OSX bugs and (not) strangely this one didn't come up. TIA...

comment:10 Changed 18 months ago by janitor

  • Host type changed from other to Mac OS X

comment:11 follow-up: ↓ 12 Changed 15 months ago by adaugherity

Still an issue on 5.2.18.

As previously mentioned, it only happens when 3D is enabled and the guest is using 3D, and it affects all guest OSes (definitely Windows and Linux at least). The window frame and content do not detach until the desktop or login screen is displayed (presumably the VirtualBox guest 3D drivers activate at this point); the BIOS/EFI boot screen, OS boot loader, and Linux text consoles are unaffected. If I disable 3D support in a Linux guest (inside the guest -- 3D acceleration remains enabled in the VM settings), the problem never occurs (but performance suffers, obviously).

Interesting detail: While in this "detached" state, launching Mission Control (Ctrl+UpArrow or F3) shows two separate windows for the VM: one titled VirtualBox VM showing the VM's desktop; the other VM name [running] with the window frame and black screen. While in this state, if you move either to another desktop, switching to that desktop will kick you right back to Desktop 1.

After minimizing and restoring the VM window, they are combined into one window with the VM's name, and you can move it between desktops as normal.

comment:12 in reply to: ↑ 11 Changed 14 months ago by Neptune BSC LLC

Replying to adaugherity:

Still an issue on MacOS Mojave

Last edited 14 months ago by janitor (previous) (diff)

comment:13 Changed 14 months ago by socratis

@Neptune BSC LLC
Please do not quote the whole previous 3 paragraphs, just to say "still an issue". Do not hit the "Reply" button, just put your comment in the form and hit the "Submit changes" below the form. It makes it really difficult to see your comment like that...

comment:14 Changed 13 months ago by Neptune BSC LLC

The issue also appears on MacOS Mojave.

comment:15 Changed 7 months ago by dkardell

This is still an issue with the latest. Please fix. Thanks! (The work around of mimimizing and then restoring the window appears to work - so it just happens when you launch and don't do that).

Last edited 7 months ago by dkardell (previous) (diff)

comment:16 Changed 3 months ago by notit

Still an issue with VirtualBox 6.0.10 r132072 on macOS Mojave 10.14.5

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use