Bug 375257 - VirtualBox mini toolbar doesn't respond to mouse clicks
Summary: VirtualBox mini toolbar doesn't respond to mouse clicks
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-18 21:27 UTC by Mike E.
Modified: 2017-07-18 20:16 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike E. 2017-01-18 21:27:30 UTC
Hi,

I usually run VirtualBox guests in fullscreen mode and switch back in forth from the VirtualBox guest(s) to the host KDE (Plasma) desktop using the "Present Windows" action triggered by screen edges.  VirtualBox also offers a mini toolbar that can be located at the bottom or top of the screen when running a guest in fullscreen (or seamless) mode that is normally an auto-hide toolbar that has various functions available to interact with the virtual machine.  The toolbar does show as it's supposed to when the mouse is moved to the screen edge where the toolbar is, but then clicking on any of the menu items yields nothing.  The mouse pointer does change from the guest pointer to the host pointer when the toolbar is shown, indicating that the system knows it has switched to the host.

This issue never arose for me with KDE 4.x.

Using Kubuntu 16.04 with KDE 5.8.5 from the backports repository.

Thanks,

Mike E.
Comment 1 Martin Flöser 2017-01-19 05:25:45 UTC
Why do you think this is an issues in KWin?
Comment 2 Mike E. 2017-01-19 16:14:19 UTC
(In reply to Martin Gräßlin from comment #1)
> Why do you think this is an issues in KWin?

Since you are one of the primary developers of KWin and based on your question, I'm guessing you don't think it is a KWin issue.  So I'd like to ask you why not?  Can you give me a suggestion about what you think would be responsible for this issue so I can submit it to the correct developer(s) instead?
Comment 3 Martin Flöser 2017-01-19 18:12:09 UTC
Am 2017-01-19 17:14, schrieb Mike E.:
> COMMENT # 2 [2] ON BUG 375257 [3] FROM MIKE E.
> 
> (In reply to Martin Gräßlin from comment #1 [1])
>> Why do you think this is an issues in KWin?
> 
> Since you are one of the primary developers of KWin and based on your
> question,
> I'm guessing you don't think it is a KWin issue.

Correct.

>  So I'd like to ask you why
> not?  Can you give me a suggestion about what you think would be
> responsible
> for this issue so I can submit it to the correct developer(s) instead?

Because KWin doesn't handle input.

And no, I don't know where the issue might be.
Comment 4 David Edmundson 2017-01-22 21:32:25 UTC
Plasmashell does not handle input either.
Talk to virtualbox. Sorry.
Comment 5 Mike E. 2017-01-22 21:57:51 UTC
Sorry, I don't really know where to post this, but as I stated in the original post, the issue doesn't happen when running KDE 4.13.3 and the same version of VirtualBox (5.1.14).  I find it very hard to believe that this is a VirtualBox issue when only KDE 5.x is affected.  Any other ideas on where on the KDE side of things this should be posted?
Comment 6 Kai Uwe Broulik 2017-01-22 21:59:48 UTC
Did you try with a different window manager like openbox?
Comment 7 Mike E. 2017-01-22 22:05:48 UTC
No, other than KDE 4, I haven't tried anything else yet.  I guess I'm going to put that on my list of things to do.  Right now, those are the only two desktop environments that I have installed on actual hardware.  All the other DEs that I use, I use through a VirtualBox guest.  As soon as I have a chance to try something else, I'll report back with my findings.
Comment 8 Mike E. 2017-01-23 22:26:22 UTC
I installed both Gnome 3 and Enlightenment on Kubuntu (not virtualized) now.  The VirtualBox mini toolbar works perfectly on both Gnome 3 and Enlightenment (as well as KDE 4).  So, I'm back to my initial report that this issue is certainly tied directly to KDE 5.  I'm obviously no expert, but I still feel like it is a window management issue.  Any ideas other than KWin and Plasmashell that could be responsible for this issue?
Comment 9 Christoph Feck 2017-02-01 23:42:09 UTC
Do those toolbars reside in a separate window, which does not accept focus? It could be a revival of bug 283474.
Comment 10 Mike E. 2017-02-02 03:11:16 UTC
Well, I'm obviously not an expert so I can't say whether or not that particular issue is the same as this, but after reading your post and looking at that bug, I did a little more testing.

I found that if I set the window behavior focus policy to "Focus Under Mouse" or "Focus Strictly Under Mouse", when I move the mouse to the top edge of the screen, it raises the VirtualBox mini toolbar like it should and the mouse cursor changes to the host's cursor theme (again like it should, and like it always does with my usually setting of "Click To Focus").  Then if I click on one of the menu items, the guest's screen goes dim (Dim Inactive desktop effect is turned on for the host), the VirtualBox mini toolbar disappears, the mouse cursor theme changes back to the guest's theme (because the mouse is now over the guest's window), and lastly, but most curiously, the host's desktop panels are displayed.  The desktop wallpaper is not displayed, just the panels.  This lasts for as long as the time set by the "Delay focus by" setting, and then the VirtualBox guest (which the mouse is now over) regains focus and the window brightens.

So it does appear that this is related to the window focusing.  Hope this gives some more clues to help someone get to the bottom of it.

Thanks,

Mike E.
Comment 11 Christoph Feck 2017-02-09 01:55:03 UTC
Readding Martin to check comment #9 and comment #10.
Comment 12 Mike E. 2017-07-18 20:16:23 UTC
I just updated VirtualBox to version 5.1.24 r117012 (Qt5.6.1) and the mini toolbar is working like it should.  Kubuntu 16.04.2  plasmashell 5.8.7