In metacity-2.14.3, the compositor compile-time option is disabled in the ebuild stating stability concerns. Now that xorg 7.1 and AIGLX have hit ~arch, unstable GNOME users should have the option of using metacity's built-in compositor. The metacity ebuild should be changed to have a 'composite' USE flag which enables the built-in compositor, possibly along with an ewarn about any stability problems that may occur.
I agree, lots of work as been going on this in the 2.13 branch, and a lot more is being done in the 2.15. So I guess we could help gnome upstream making this feature available for more testers (~arch for the moment).
The current development on the compositor is done in the unstable branch, not in 2.14 + there is no official release of the libcm dep. Adding a compositor flag to 2.14 would just mean exposing old bugs (e.g. RH uses a large compositor patch for metacity 2.14), so that is not much of an argument to me.
hum sorry, I should have misread version number then. So this bug should be closed as later, isn't it ?
we'll make this available later on since its still 'unstable'.
I took the libcm-0.1.1-package of the xeffects-overlay and used it together with metacity-2.20.1 (from official portage-tree) with enabled compositor. It compiles fine and also works though I have the same problems as with compiz. Though it seems more fluent and stable than compiz. I get always this when I try to play videos with mplayer over xv: "X11 error: BadAlloc (insufficient resources for operation) ??,?% 0 0" Perhaps it's realy what it says, that some resources are insufficient because it's a simple Intel(R) 945GM 20061017 x86/MMX/SSE2 (in my MacBook).
Created attachment 137089 [details] extended metacity-2.20.1.ebuild
