Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz |
Invalid
|
Undecided
|
Unassigned | ||
Nux |
Fix Released
|
Medium
|
Simon Arlott | ||
Trusty |
Triaged
|
Medium
|
Unassigned | ||
Unity |
Invalid
|
Undecided
|
Unassigned | ||
nux (Ubuntu) |
Fix Released
|
Medium
|
Simon Arlott | ||
Bug Description
(Using the Terminal window as an example)
1. Open a Terminal window
2. Maximise a window fully so that its title bar and menu share the top Unity panel
3. Click the "View" menu (the menu opens)
4. Click the "Search" menu (the "View" menu closes)
5. Click anywhere on the title bar
6. The window restores to non-maximised size
It shouldn't do this, only a double-click should restore the window.
Alternative ways to trigger it:
3. Click the "Terminal" menu
4. Click the "Reset" option
5. Click anywhere on the title bar
3. Click the "Terminal" menu
4. Click inside the main area of the application
5. Click anywhere on the title bar
It looks like something is going wrong with the double-click detection when a menu is opened and then closed.
Version: Ubuntu 14.04.1
unity 7.2.2+14.
xorg 1:7.7+1ubuntu8
Related branches
- Christopher Townsend (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 34 lines (+3/-3)2 files modifiedNuxGraphics/GraphicsDisplayX11.cpp (+2/-2)
NuxGraphics/GraphicsDisplayX11.h (+1/-1)
Changed in compiz: | |
status: | New → Invalid |
Changed in unity: | |
status: | New → Invalid |
Changed in nux: | |
status: | Confirmed → In Progress |
Changed in nux (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in nux: | |
importance: | Undecided → Medium |
milestone: | none → 4.0.7 |
assignee: | nobody → Simon Arlott (sa.me.uk) |
Changed in nux (Ubuntu): | |
assignee: | nobody → Simon Arlott (sa.me.uk) |
Changed in nux: | |
status: | In Progress → Fix Committed |
Changed in nux: | |
status: | Fix Committed → Fix Released |
This only happens after the system has been running for a while, so either a long running service stops behaving correctly or a software upgrade causes it to stop working correctly. I logged in as a Guest Session and the problem still occurred, but it doesn't happen immediately after a reboot.