if i enable the compositing manager in metacity i don't get any errors, warnings
or messages, all i get is a white screen. In this "white" desktop the mouse
pointer is the only thing working ok. Not however that it is not crashing if i
disable i can move the windows around and if i disable the compositing manager
using gconftool-2 everything is back to normal.
I'm using DRM, Mesa and the lastest version of the ati drivers from CVS also,
this is with benjamin's memory patches applied.
Created attachment 4721 [details]
screenshot showing how the desktop looks like.
My guess is that the version of metacity you're using creates a direct rendering gl context, this have
been fixed in metacity cvs. Try starting metacity after setting LIBGL_ALWAYS_INDIRECT=1 and see if
that helps. Otherwise, give CVS head a try, but know that this code is still very much in development
and things may break from day to day.
Right now, as of today everything is black expect for the mouse. It doesn't
change anything that LIBGL_ALWAYS_INDIRECT is set or not. The result is the same.
Could it be related to the fact that GL applications report missing visuals?,
more specifically they usually report the visual 0x4b as missing.
hi again, i just updated X to the 7.1 release, I keep seeing this problem,
nothing has changed. I have something to add that might be interesting though.
I'm using the jimmac cursor theme, this is, i'm not using the core pointer for
the mouse pointers. When i enable the compositor in metacity everything is
black, expect for the mouse pointer.
could you post your xorg config file. Also try disable ColorTiling.
Disable ColorTiling make no difference. Find the xorg.conf file attached
Created attachment 5719 [details]
my xorg.conf file
I am affected by this too, except for the screen being blue and not seeing the
I also actually have an error message from metacity:
Log level 16: No texture created - maybe Texture From Pixmap extension is not
I also filed this against metacity:
(In reply to comment #8)
> I am affected by this too, except for the screen being blue and not seeing the
> I also actually have an error message from metacity:
> Log level 16: No texture created - maybe Texture From Pixmap extension is not
> I also filed this against metacity:
Have you enabled AIGLX? I think you need to (I'm a fellow user though, I don't
know directly). Without AIGLX or XGL, you definitely won't have that extension,
Created attachment 6928 [details]
i see the white screen (as in the screenshot) with ubuntu's "spiftacity"
package, which seems to be the 2.13.89 version of metacity compiled w/
compositor enabled, compiled against libcm 0.0.16. I see a similar, but blue,
screen with a self compiled version of metacity 2.16.1 with cvs libcm. in both
cases, I don't see the message that pavel does, but I do see the message
described in bug 6689. attaching xorg.conf
I think you need to launch metacity from console to see that message i.e:
1. metacity --replace
2. click to enable compositor in gconf-editor; click the same spot blindly again
to get rid of the blue screen
I have the blue version of the problem with the nvidia drivers, metacityu-2.16.2
and a libcm snapshot from 20060827
Do you still experience this issue with newer soft ?
Please check the status of your issue.
on Jan 21, 2017 at 23:45:52.
(provided by the Example extension).