Button1 Actions are triggered regardless of whether or not they are actually active
Bug #1053280 reported by
Sam Spilsbury
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz |
Fix Released
|
High
|
Sam Spilsbury | ||
compiz (Ubuntu) |
Fix Released
|
High
|
Sam Spilsbury |
Bug Description
Currently CompScreen:
Related branches
lp:~compiz-team/compiz/compiz.fix_1053280
- jenkins (community): Approve (continuous-integration)
- Daniel van Vugt: Approve
- Sam Spilsbury: Pending requested
-
Diff: 1133 lines (+843/-75)11 files modifiedinclude/core/abiversion.h (+1/-1)
include/core/action.h (+14/-1)
include/core/option.h (+4/-3)
src/action.cpp (+15/-0)
src/event.cpp (+149/-62)
src/eventmanagement.h (+80/-0)
src/option.cpp (+16/-4)
src/option/tests/option.cpp (+31/-0)
src/privateaction.h (+23/-1)
src/privatescreen/tests/test-privatescreen.cpp (+507/-1)
src/screen.cpp (+3/-2)
Superseded
for merging
into
lp:compiz/0.9.8
- Daniel van Vugt: Needs Resubmitting
- jenkins (community): Approve (continuous-integration)
- Sam Spilsbury: Needs Resubmitting
-
Diff: 1115 lines (+859/-69)10 files modifiedinclude/core/action.h (+12/-1)
include/core/option.h (+4/-2)
src/action.cpp (+24/-0)
src/event.cpp (+149/-62)
src/eventmanagement.h (+80/-0)
src/option.cpp (+18/-0)
src/option/tests/option.cpp (+31/-0)
src/privateaction.h (+25/-1)
src/privatescreen/tests/test-privatescreen.cpp (+513/-1)
src/screen.cpp (+3/-2)
Changed in compiz: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Sam Spilsbury (smspillaz) |
milestone: | none → 0.9.8.4 |
Changed in compiz: | |
status: | Confirmed → In Progress |
Changed in compiz: | |
milestone: | 0.9.8.4 → 0.9.9.0 |
Changed in compiz: | |
status: | In Progress → Fix Committed |
Changed in compiz (Ubuntu): | |
assignee: | nobody → Sam Spilsbury (smspillaz) |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in compiz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This sounds similar to a problem I noticed a while back with spurious triggers. But I don't remember how to reproduce it. Got a manual test case?