[12.04 only] Allow Mesa 9.0.x point releases to have unredirection enabled also on intel and nouveau

Bug Description

This only affects 12.04(.2) (precise). It's continuation of bug #1063690, so mostly the same SRU information applies:

[Impact]

Lower than optimal fullscreen applications performance, especially games, on intel and nouveau.

[Test Case]

Benchmark a game with for example phoronix-test-suite / pts/openarena-1.5.0 - the default settings after this bug fix should give equal performance to what previously required manually enabling the compiz unredirect fullscreen windows option.

[Regression Potential]

The feature has been tested for the last few months, and all known regressions have been fixed. The potential regressions lie in for example exiting a fullscreen application.
This setting is already the default in Ubuntu 12.10 - the stack that 12.04.2 is now identical to. It's also already default on 12.04.2 on radeon, fglrx and nvidia.

---

We currently have the following blacklist string regarding unredirection on 12.04: (nouveau|Intel).*Mesa (8.0|9.0). The '9.0' was added because an user had x-updates PPA enabled only, not the rest of the 12.04.2 (LTS-Q) stack, and on that unredirection of fullscreen windows didn't work.

We now have Mesa 9.0 point releases in precise, so the strings compared for blacklisting would differ now even from x-updates PPA. As an example:

up-to-date 12.04.2:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965GM
OpenGL version string: 2.1 Mesa 9.0.3
OpenGL shading language version string: 1.20

original 12.04 stack + x-updates:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965GM x86/MMX/SSE2
OpenGL version string: 2.1 Mesa 9.0
OpenGL shading language version string: 1.20

It'd be wanted that Mesa 9.0.x would not be blacklisted anymore on Intel and Nouveau, but original 9.0 (and 8.0*) could remain blacklisted.

Hello Timo, or anyone else affected,

Accepted compiz into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/compiz/1:0.9.7.12-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

No issues seen here (nouveau, nvidia [GeForce 8400M GS]

This bug was fixed in the package compiz - 1:0.9.7.12-0ubuntu2

---------------
compiz (1:0.9.7.12-0ubuntu2) precise; urgency=low

* debian/patches/fix_1095001.patch
- Cherry-pick a patch from upstream to fix CPU usage (LP: #1095001)
* debian/patches/blacklist_precise_mesa80_intel_nouveau.patch:
- Rename the blacklist patch, add verbose description and allow
fullscreen unredirection for also Intel and Nouveau users using
Mesa 9.0.x (Ubuntu 12.04.2 LTS or those who have opted in to LTS-Q
packages). (LP: #1167321)
-- Timo Jyrinki <email address hidden> 2013年4月11日 12:05:04 +0300

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Allow Mesa 9.0.x point releases, we found the screensaver couldn't show unlock interface when back from screen off.

Please view bug 1216781 for more information.