As it turns out, the "proper" behaviour is actually what we're seeing in VNC/NX. Since the menu itself has been implemented as a seperate process to the panel applet, a single-click on the applet is interpreted as the mouse button being released *outside* of the menu, which results in the menu closing unless you move the mouse pointer down inside the menu before releasing.
The "desirable" behaviour we're seeing at the local console is only possible thanks to a number of GDK event filters which have been implemented by Canonical, possibly to try and work around this problem. Further, it seems that the X11 core event code has been removed at some point and replaced with XInput2 code, which neither VNC nor NX currently support (see service/panel-service.c:event_filter()). So it seems that the main issue here is the lack of support for X11 core events in the 2D panel. It's worth noting that without this support, no major remote desktop implementation will exhibit the desired behaviour on Ubuntu, and since there are no easy workarounds, this really needs to be fixed in Unity 2D in order to support remote access properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/866046 Title: unity-2d-panel fails to react to single mouse click in virtual session (VNC/NX) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/866046/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
