Right, it used to check to see if you had a resolution higher than 2048
and fall back to metacity if that was the case. Now it checks if you
have a resolution higher than or equal to 2048 and falls back to
metacity. The fix in bug 428769 wasn't a fix for your issue, it was the
cause of your issue.
Then why does the changelog say that they changed the greater than to
greater than *or equal to*. Mine is equal, and I should be seeing the
results of the change.
- improve the maxTextureSize check to test for >= instead of
just > (thanks to bryceh) LP: #428769
However as noted in comme
@Travis: I'm confused, I'm not using 15, I'm using 15.*1*, which is the
most recent version available in lucid-proposed.
And I do have a working system. The MTS for my card is 2048x2048, and I
am at 2048x768, just at the limit. And according to some developers at
the Compiz IRC channel, this is a
You're not doing anything wrong and it isn't a bug in our wrapper. It is
a deliberate decision to block compiz from running in such a situation
due to bug 428769
--
Compiz incorrectly determines MTS
https://bugs.launchpad.net/bugs/597103
You received this bug notification because you are a member
Actually 1:0.8.4-0ubuntu15 is what is causing this problem for you, it
isn't a fix for this problem. It's a fix for the opposite problem: bug
428769
Since the choice is between you having a working system with compiz and
the other bug reporter having a broken system this bug is Won't Fix.
** Chan
