seamless mode fails in Version 5.2.1 r119176 (Qt5.6.1) -> fixed after 5.2.6

[matthewls]

Though 5.2.0 works perfectly, and 5.2.1 works fine using standard windows and in full screen mode, the seamless mode causes both windows and linux guests to disappear. I can retrieve them using the hotkey+l, but the video is hidden or distorted in seamless mode.

Host: AMD Fx370 32GB RAM, NVidia GeForce GTX 960/PCIe/SSE2 driver 387.22, Linux mint 18.2, kernel 4.13.15, KDE Plasma 5.11.3, QT 5.9.1.

Guests: windows7-x64; Linux mint 18.1 x64, KDE 5.10.90, QT 5.7.1, kernel 4.11.3

I've attached the log file in case it's helpful

[matthewls]

vbox.log

[matthewls]

Ubuntu updates provided virtualbox-5.2_5.2.2-119230~Ubuntu~xenial_amd64.deb which has the same problem as described above, so I had to downgrade to 5.2.0 to get seamless windows to work.

[matthewls]

Official release Version 5.2.2 r119230 (Qt5.6.1) with EP 5.2.2r119230 same problem--invisible seamless windows.

[thoms]

Seeing same behavior with 5.2.2 seamless on CentOS 6 hosts with Windows 7 & 10 guests.

[matthewls]

Test build (devo snap) 119268 has no visible VM windows in any mode (full, windowed,seamless).

[matthewls]

Test build Version 5.2.3 r119337 (Qt5.6.1) has the same issue. Same as ticket 17337

[matthewls]

more graphics weirdness in 5.2.3. Enabling 3d graphics for a mint 18.3 VM shows a blank cinnamon desktop in normal mode, and hidden applications and menubars in KDE. Switching to seamless mode reveals the previously hidden windows, but interacting with them is hit or miss--e.g. typing into a terminal may or may not show those keystrokes. switching back and forth between seamless and normal mode can run programs in the console . They're some off-target pointers in there somewhere. Again, VB 5.2.0 works perfectly in all regards--except in kernel 4.14.x. So the choice is using an end-of-life or older longterm kernel with fully functional VB, or using the latest kernel with broken seamless mode in VB.

[matthewls]

so i'm back to 4.13.15 and vb 5.2.0

[matthewls]

Same invisible windows using test build Version 5.2.3 r119552

[matthewls]

And in VirtualBox Version 5.2.3 r119552 .

[matthewls]

And VirtualBox-5.2.3-119608-Linux_amd64.run

[matthewls]

And VirtualBox-5.2.3-119620 -Linux_amd64.run

[Socratis]

Hey matthewls, there are a couple of test builds that you haven't commented on! How come?

Seriously now? Are you going to be commenting on every test build that pops out? This has the potential to end up as what's known as a large monologue... :D

[matthewls]

i'm just giving feedback on one 5.2.2+ show stopper (for me). i'm looking forward to sending the "hooray, it works!" monolog ;-)

[matthewls]

same with 5.2.4. BUT! VB5.2.0 works with linux kernel 4.14.7, so back to updated kernel.

[Michael Thayer]

I assume that you are installing the Guest Additions (the ones provided with VirtualBox) each time you upgrade. Would you be able to test VirtualBox 5.2.4 with older Additions[1] and /or older VirtualBox versions with current Additions to compare?

[1] ​https://download.virtualbox.org/virtualbox

[matthewls]

yes, each time. now I'm running 5.2.0 r118431 (Qt5.6.1) w/ ExtPk 5.2.4r119785. I'll try the latest test build (119921 with the current EPack and see how it goes.

[matthewls]

5.2.5 r119921 (Qt5.6.1) with ExtPk 5.2.4r119785 has the same problem. 5.2.5 r119921 (Qt5.6.1) with ExtPk 5.2.5 and guest additions 119806, same problem. 5.2.4 119785 (Qt5.6.1) with ExtPk 5.2.4r119785 and guest additions 119806, same problem.

*5.2.0-118431 (Qt5.6.1) with ExtPk 5.2.0r118431 and guest additions 5.2.5r119806 works* *5.2.0-118431 (Qt5.6.1) with ExtPk 5.2.0r118431 and guest additions 5.2.0r118431 works*

despite starting guest giving error, 'run /sbin/vboxconfig' which gave " vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why."

[yaap]

Same problem on Debian Stretch with backport kernel 4.13.13 using KDE / X and Intel integrated GPU (i5-5200U). With official release 5.2.4 in seamless mode the Windows guest taskbar is weird, a bit translucent, mouse doesn't show up in Windows taskbar and displaying the Windows menu is corrupted. Win7 windows content are black. Problem occured with both old guest extensions 5.1.30 and new guest extensions 5.2.4.

Reverting to vbox 5.1.30 fixed the issue. This with the old extensions 5.2.4 still in place. So it doesn't seem related to the guest extensions.

I tried to disable 2D and 3D hardware acceleration when the issue occured: no effect.

[matthewls]

All versions after 5.2.0 including 5.2.x test build 120181 have the same issue. 5.1 all worked, 5.2.0 worked, nothing since.

[Michael Thayer]

If anyone seeing this is able to build VirtualBox it would be greatly appreciated if you could bisect this.

[Dsen]

I think we had reproduced that thing. Will fix it to next maintenance release.

[matthewls]

Many thanks. 5.2.6 has same issue, I'm glad the fix is coming.

[rc]

I'm facing the same issue when I upgraded from 5.1.x to 5.2.6 and I'm adding a comment to get updates on changes.

[Paul Allen]

Ditto, upgraded to 5.2.6. Linux mint 18.1 host with Windows 10 VM, unable to activate any window in VM in seamless mode. Full screen works. Adding to get updates.

[matthewls]

FIXED! In Version 5.2.7 r120579 (Qt5.6.1) Thank you VB engineers.

[Michael Thayer]

Thank you for letting us know.

[Socratis]

Replying to matthewls:

i'm looking forward to sending the "hooray, it works!" monolog ;-)

Hooray, it works! :D

[matthewls]

Hooray, it works! Version 5.2.7 r120678 (Qt5.6.1)

[Walter Lapchynski]

I cannot, sadly, say this fixes Windows 10, which still suffers from the problems described in #15092.

[Socratis]

@wxl
You do not necessarily have to wake up every ticket in the bugtracker and every thread in the forums that mentions the word "seamless" to draw more attention to #15092. If there's an issue with #15902, a comment in #15902 should suffice.

The OP's problem here was fixed, as reported by none other than the OP. Ticket can be closed and we only have to worry about open tickets. And there are plenty to deal with... ;)

[Walter Lapchynski]

Replying to socratis:

You do not necessarily have to wake up every ticket in the bugtracker and every thread in the forums that mentions the word "seamless"

My friend, you mentioned this ticket— that had nothing clearly to do with Windows 10— on a forum post about Windows 10. You also mentioned this in #15092. So I could shoot this back at you, just replacing "seamless" with "Windows 10" ;)

In all reality, I was drawn to this all by your mention in #17337 that what appeared to be a global fix for seamless issues. As a result, today I made four posts:

• confirmed #17337 is fixed by #17304 (a response to a question you asked)
• confirmed #15092 is NOT fixed by #17304 (once on each ticket)
• reiterated the latter on the forum

If those three tickets and that one forum post is all you have to deal with with regards to seamless, I guess you should count yourself lucky.