virtualbox.org

I was using VirtualBox 5.1.16 (113841) and the problem was still there.
Reverted to 5.1.8 and problem was revolved.

I haven't seen a ticket from the bugtracker, so I hope you guys like 5.1.8, because without a ticket, almost nothing gets fixed...
Please post your comments in #16246 - In seamless mode, mouse events do not reach host windows visible behind the VM.

socratis wrote:I haven't seen a ticket from the bugtracker, so I hope you guys like 5.1.8, because without a ticket, almost nothing gets fixed...

Sorry if I may didn't understand...
Isn't this a ticket for this bug ? https://www.virtualbox.org/ticket/16246
(I think you posted the link here)

Thanks

z3rodivide wrote:I think you posted the link here

Not only I posted the link, I even commented there!!! That's it, I'm officially losing it...
Sorry about that, too many windows open and not enough caffeine...
Post edited to reflect... reality

Hi, just tested with VirtualBox 5.1.22, I confirm the issue is still present.
I 'm wondering if this mode is little commonly adopted by users ?

From the usage patterns and the number of complaints, I'd say yes. Personally I want to keep my VMs as separate as they can possibly be. No read-write shared folders, no access from the guest to the host (only from the host to the guest).

Something like "separation of church and state" as opposed to a "theocratic state"

5.1.26 issue is still present
Considering it's a regression of an old feature it's quite strange that still can't be fixed

Considering that the amount of time available to the developers is finite and limited, it's no strange at all that it hasn't been addressed yet. You could compare the source code trees between 5.1.8 and 5.1.10 and at least see where the failure happened. I'm not saying to fix it, simply to identify it. If you don't take matters in your own hands, don't expect the developers to run and fix things that are not that widely used. You have your own priorities, they have theirs. They don't necessarily match...

5.1.28 solved the issue !!!
Thank's everybody !!

Just installed 5.2.0 on High Sierra and it appears the issue has returned.

I am running 5.1.30 under High Sierra and also have problems, although I have never seen it work well in my case, with dual monitors.

OSX - 10.11.6

Confirming that BOTH 5.1.30 and 5.2 seem to have this bug re-introduced. I attempted both
and finally back-leveled to 5.1.28. Guest OS tried - RHEL 7.4 and RHEL 6.9