VirtualBox breaking Unity's Compiz Scale Plugin

[shockwave]

My setup: Ubuntu 16.04 host, Win8 64bit guest.

On the host when I enable the Compiz Scale plugin in CompizConfig Settings Manager and give it a window binding (say the top of the screen initiates the plugin) everything works except when Virtualbox is the active window. When Virtualbox is the active window it "steals" the mouse movement when moving to the top of the screen and leaves the desktop in a bad state. The scale plugin is now broken (it no longer triggers) until I manually switch to a different active application then re-initiate the scale plugin via the mouse at the top of the screen. After that it works fine again until I try to trigger it with VirtualBox being the active window. If, however, I press the host key (right ctrl in my case) before I move the cursor to the top of the screen it initiates the Scale plugin as expected.

On previous versions of VirtualBox this all worked. Not exactly sure what version this started happening in unfortunately.

This is quite hard to explain, but it is 100% reproducible on my machine. I've tried everything from clearing all gnome settings, clearing all compiz settings, etc.

[socratis]

On previous versions of VirtualBox this all worked. Not exactly sure what version this started happening in unfortunately.

This sounds like a case for the bugtracker. But please, if you want this resolved try to make the developer's lives easier. Go with full details, i.e. last known version was x.y.z, versions of your system, gnome and the whole nine yards as they say in my village.

[socratis]

Boy, am I glad when advice is well followed. Or not (ticket 15935).

[shockwave]

Ubuntu 16.04 should cover what you asked. I don't have anything special set up. Short of dumping dpkg output so you have every version of everything on my system I'm not sure what else should be put there, considering an up to date 16.04 system will have the same versions as I do.

I put the version of VirtualBox in the proper field, the proper Host/Guest OS and versions, etc. As I put in my original post, I am not sure what version was the last known working. It has been doing it for a while and I can't recall when it started.

[socratis]

I am not sure what version was the last known working. It has been doing it for a while and I can't recall when it started.

That's what I was talking about. Instead of you doing some research yourself, like going back a version or two, now you have a developer trying to replicate and hunt down your specific bug. What about the rest of the bugs that need to be fixed in the meantime?

Trust me, a well documented bug report has way more chances of getting looked at. Imagine if you file a bug report that says "Crash. Help me". Do you think that they're seriously going to take a look at it? I know the example is extreme, but if the bug report was "Crash with 5.1.6 on X.Y, but not on Y.Z" that would be much better. Makes sense, no?

[shockwave]

I am a software developer myself, I understand the want for as much information as possible.

However I also understand that me spending hours trying to replicate this (and it would take hours...I have to downgrade not just the packages on the host but the guest OS extensions over and over and over) when the developer can figure it out without that information (often that happens) is more beneficial overall.

If the developer looks at it and requires extra information no problem I will go ahead and do that.