VirtualBox

Opened 6 years ago

Last modified 5 years ago

#17168 new defect

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

Reported by: James Moe 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 (2)

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

Download all attachments as: .zip

Change History (18)

comment:1 by Socratis, 6 years ago

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 by James Moe, 6 years ago

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

comment:3 by ncj, 6 years ago

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 by Socratis, 6 years ago

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

comment:5 by Socratis, 6 years ago

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.

by pzrq, 6 years ago

Attachment: virtualbox-log.txt added

VirtualBox Log File

by pzrq, 6 years ago

Example screenshot of results after clicking and dragging

comment:6 by jhawksley, 6 years ago

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 by Socratis, 6 years ago

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 by jhawksley, 6 years ago

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

Last edited 6 years ago by jhawksley (previous) (diff)

comment:9 by Socratis, 6 years ago

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 by janitor, 6 years ago

Host type: otherMac OS X

comment:11 by Andrew Daugherity, 6 years ago

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.

in reply to:  11 comment:12 by Neptune BSC LLC, 5 years ago

Replying to adaugherity: stiil an issue on MacOS Mojave

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.

Version 0, edited 5 years ago by Neptune BSC LLC (next)

comment:13 by Socratis, 5 years ago

@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 by Neptune BSC LLC, 5 years ago

The issue also appears on MacOS Mojave.

comment:15 by dkardell, 5 years ago

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 5 years ago by dkardell (previous) (diff)

comment:16 by notit, 5 years ago

Still an issue with VirtualBox 6.0.10 r132072 on macOS Mojave 10.14.5

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use