lp:~vanvugt/compiz-core/fix-930412
- Get this branch:
- bzr branch lp:~vanvugt/compiz-core/fix-930412
Branch merges
- Sam Spilsbury: Approve
-
Diff: 211 lines (+51/-54)4 files modifiedsrc/action.cpp (+3/-0)
src/privatescreen.h (+0/-2)
src/screen.cpp (+36/-50)
xslt/bcop.xslt (+12/-2)
Related bugs
Bug #930412: [regression] no core keybindings work any more | High | Fix Released |
Related blueprints
Branch information
Recent revisions
- 2997. By Daniel van Vugt
-
Fixed: Core keybindings like Alt+F4 not being registered due to bad
construct/init ordering (LP: #930412) - 2996. By Sam Spilsbury
-
Fixes LP #930071
There's a race condition in gtk-window-
decorator that would cause some windows to be updated before the decoration was fully realized Merge lp:~smspillaz/compiz-core/compiz-core.fix_930071 into lp:compiz-core
- 2994. By Alan Griffiths
-
Fix for https:/
/bugs.launchpad .net/compiz- plugins- extra/+ bug/929449 and failing tests in package build - 2993. By Daniel van Vugt
-
Revert the compiz.pc part of the fix for LP: #928044 because it caused some
packages like libcompizconfig to link to compiz_core when they shouldn't.
(LP: #929443)And besides, the CMake portion of the fix for LP: #928044 seems enough.
- 2990. By Sam Spilsbury
-
Be a little smarter about updating decorations (LP: #928173)
Merged -r2983..2985 from lp:~smspillaz/compiz-core/compiz-core.decor_928173
- 2989. By Daniel van Vugt
-
Fix build failure due to combining these two commits together:
2987: lp:~alan-griffiths/compiz-core/test-PrivateScreen-updatePlugins
2988: lp:~vanvugt/compiz-core/fix-928655Of course, they worked independently, but not together.
- 2988. By Daniel van Vugt
-
Revert revision 2938:
lp:~smspillaz/compiz-core/compiz-core.fix-880707-test-v3
in order to avoid a critical regression it causes (LP: #928655).Unfortunately the regression was not just a logical bug, but a design bug.
The imposition of user-controlled frame rate throttling completely broke the
existing automatic frame rate throttling and detection. This was a design bug
because it attempted to separate waiting for Vsync from buffer swapping.
Doing so makes the detection of unthrottled rendering impossible. So the
paintscheduler would just switch to non-vsync mode and get stuck there
(LP: #928655).Instead use the original algorithm from revision 2916:
lp:~vanvugt/compiz-core/fix-880707.2
which is stable and has many months of community testing already.Merged from lp:~vanvugt/compiz-core/fix-928655
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:compiz-core