Bug 5999 - problems with r300 and metacity compositing manager
problems with r300 and metacity compositing manager
Status: NEW
Product: DRI
Classification: Unclassified
Component: General
XOrg git
x86 (IA32) Linux (All)
: high major
Assigned To: Default DRI bug account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-22 23:04 UTC by Diego
Modified: 2013-03-15 14:26 UTC (History)
5 users (show)

See Also:


Attachments
screenshot showing how the desktop looks like. (12.39 KB, image/png)
2006-02-22 23:05 UTC, Diego
no flags Details
my xorg.conf file (3.14 KB, text/plain)
2006-05-23 17:59 UTC, Diego
no flags Details
xorg.conf (4.83 KB, text/plain)
2006-09-12 16:02 UTC, thejoe
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego 2006-02-22 23:04:32 UTC
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.
Comment 1 Diego 2006-02-22 23:05:20 UTC
Created attachment 4721 [details]
screenshot showing how the desktop looks like.
Comment 2 Kristian Høgsberg 2006-03-07 14:56:52 UTC
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.
Comment 3 Diego 2006-04-29 17:56:59 UTC
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.
Comment 4 Diego 2006-05-23 10:57:43 UTC
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.
Comment 5 Jerome Glisse 2006-05-23 17:08:53 UTC
could you post your xorg config file. Also try disable ColorTiling.
Comment 6 Diego 2006-05-23 17:58:31 UTC
Disable ColorTiling make no difference. Find the xorg.conf file attached
Comment 7 Diego 2006-05-23 17:59:25 UTC
Created attachment 5719 [details]
my xorg.conf file
Comment 8 Pavel Rojtberg 2006-08-23 07:10:53 UTC
I am affected by this too, except for the screen being blue and not seeing the
pointer.
I also actually have an error message from metacity:
Log level 16: No texture created - maybe Texture From Pixmap extension is not
present?

I also filed this against metacity:
http://bugzilla.gnome.org/show_bug.cgi?id=352520
Comment 9 Simon 2006-08-26 20:41:34 UTC
(In reply to comment #8)
> I am affected by this too, except for the screen being blue and not seeing the
> pointer.
> I also actually have an error message from metacity:
> Log level 16: No texture created - maybe Texture From Pixmap extension is not
> present?
> 
> I also filed this against metacity:
> http://bugzilla.gnome.org/show_bug.cgi?id=352520

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,
either.
Comment 10 thejoe 2006-09-12 16:02:44 UTC
Created attachment 6928 [details]
xorg.conf

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
Comment 11 Pavel Rojtberg 2006-09-15 11:20:18 UTC
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
Comment 12 Olivier Crête 2006-09-26 21:43:57 UTC
I have the blue version of the problem with the nvidia drivers, metacityu-2.16.2
and a libcm snapshot from 20060827 
Comment 13 chemtech 2013-03-15 14:26:50 UTC
Diego 
Do you still experience this issue with newer soft ?
Please check the status of your issue.