regression / unable to interact with window-titlebar (window decoration) after minimizing/unminimizing gnome-terminal
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Compiz |
Fix Released
|
High
|
Daniel van Vugt | |||
Compiz Core | Status tracked in 0.9.7 | |||||
0.9.7 |
Fix Released
|
High
|
Daniel van Vugt | |||
Arch Linux |
New
|
Undecided
|
Unassigned | |||
compiz (Ubuntu) |
Fix Released
|
High
|
Unassigned | |||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
Title bar buttons (close, minimize, maximize) become unresponsive to clicks. This has been observed mainly with Terminal windows, and only by a limited number of people.
[Development Fix]
Fix committed to lp:compiz-core r3096 (compiz 0.9.7 and 0.9.7 series). "Make sure window frames actually get destroyed when they should, to guarantee they get recreated on unminimize."
[Stable Fix]
As above.
[Test Case]
1. open gnome-terminal
2. minimize gnome-terminal
3. un-minimize gnome-terminal
4. try to interact with window title-bar; ie: close/minimize/
[Regression Potential]
Low. It's been tested by developers for the past week. One-liner.
ORIGINAL DESCRIPTION:
the title says it all, but here is how to reproduce;
1. open gnome-terminal
2. minimize gnome-terminal
3. un-minimize gnome-terminal
4. try to interact with window title-bar; ie: close/minimize/
So far (and quite oddly) gnome-terminal is the only app i have found that isn't working properly.
however, that being said on my machine is happens 100% of the time. I can however, move the window by using it's gtk menubar.
Related branches
- Sam Spilsbury: Disapprove
- Daniel van Vugt: Needs Fixing
- Alan Griffiths: Needs Fixing
-
Diff: 69 lines (+14/-10)1 file modifiedplugins/decor/src/decor.cpp (+14/-10)
- Sam Spilsbury: Approve
-
Diff: 19 lines (+1/-3)1 file modifiedsrc/window.cpp (+1/-3)
- Sam Spilsbury: Approve
- Alan Griffiths: Abstain
- Daniel van Vugt: Pending requested
-
Diff: 12 lines (+1/-2)1 file modifiedplugins/decor/src/decor.cpp (+1/-2)
Changed in compiz-core: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in compiz-core: | |
milestone: | none → 0.9.7.8 |
description: | updated |
Changed in compiz (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → precise-updates |
Changed in compiz: | |
milestone: | none → 0.9.8.0 |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → Daniel van Vugt (vanvugt) |
no longer affects: | compiz-core/0.9.8 |
Changed in compiz-core: | |
milestone: | 0.9.8.0 → none |
status: | Fix Committed → Fix Released |
Changed in compiz: | |
status: | Fix Committed → Fix Released |
I forgot to mention,
this bug has appeared today (April 14th), in the last few hours.
I built compiz once and noticed the problem. but waited before filing a bug report in case i had just pulled from bzr at a bad time. i waited about 2 hours before building again, and the bug is still there.
cheerz