Bug 213236 - emulators/virtualbox-ose: VirtualBox 5.1.x interferes with fbpanel, lxpanel, xfce4-panel
Summary: emulators/virtualbox-ose: VirtualBox 5.1.x interferes with fbpanel, lxpanel, ...
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-06 06:06 UTC by Will B
Modified: 2018-02-15 23:05 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (vbox)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will B 2016-10-06 06:06:38 UTC
After the recent update by FreeBSD maintainers to VirtualBox version 5.1.x, fbpanel, lxpanel, xfce4-panel and possibly others have problems with right-clicking their task manager buttons after a virtual machine is started from the VirtualBox Manager.

Previous versions of VirtualBox (4.x.x and 5.0.x) did not have this problem.

How to reproduce this issue:
- - - -
* Start VirtualBox Manager

* Double-click virtual machine to start it

* After virtual machine starts, right-click on the virtual machine's task manager button in fbpanel, lxpanel or xfce4-panel and the context menu does not pop up.  

* Normal click another task bar button, then right-clicking works temporarily

* Exit (all) virtual machine(s)

* Right-clicking of task manager buttons works again in fbpanel, lxpanel and xfce4-panel.
- - - -

This problem does not seem to happen when only the VirtualBox Manager is running.

VirtualBox version: 5.1.6 r110634 - (Qt5.6.1)

FreeBSD 10.3 - 64-bit

uname -a: FreeBSD will-freebsd 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
Comment 1 Will B 2016-10-06 06:23:29 UTC
Additional information:
I am running Fluxbox as my window manager, however I also tried this with xfce4-wm and the problem still exists.
Comment 2 Will B 2016-10-07 17:23:23 UTC
Filed a bug report upstream:

https://www.virtualbox.org/ticket/16046
Comment 3 Walter Schwarzenfeld 2018-01-14 03:17:42 UTC
We have version 5.2.4. Does the problem still exists or is  this is overcome by events.