After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 151918 - Find out what is going on with Metacity's frame visuals.
Find out what is going on with Metacity's frame visuals.
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: Søren's compositor
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity compositor maintainers
Metacity compositor maintainers
Depends on:
Blocks:
 
 
Reported: 2004-09-05 17:50 UTC by bugzilla
Modified: 2008-01-21 21:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8

Attachments
weird borders (403.64 KB, image/png)
2004-09-05 17:51 UTC, bugzilla 		Details

Description bugzilla 2004-09-05 17:50:26 UTC 
-have metacity 2.8.4 running
-run xcompmgr (with any options)
-watch the window borders gone transparent
Comment 1 bugzilla 2004-09-05 17:51:34 UTC 
Created attachment 31305 [details]
weird borders
Comment 2 Havoc Pennington 2004-09-05 23:34:51 UTC 
with all themes or just this one?
Comment 3 bugzilla 2004-09-06 08:18:52 UTC 
with any theme

was running fine with 2.8.1, just appeared after installing 2.8.4
Comment 4 bugzilla 2004-09-11 12:11:46 UTC 
found the problem:
you have to run metacity with XLIB_SKIP_ARGB_VISUALS=1 environment variable.
Comment 5 Havoc Pennington 2004-09-11 16:40:54 UTC 
That's a workaround, certainly not a fix ;-)
Comment 6 bugzilla 2004-09-11 19:10:16 UTC 
this variable also affects other gnome apps like gnome-theme-manager (no
preview) and epiphany (crashes on toolbar setup)
Comment 7 Christoph Richter 2004-09-30 11:40:58 UTC 
I've seen that behaviour in 2.8.5 and current cvs, too. However, if you compile
metacity with --disable-render, the problem disappears. Still just a workaround,
I know...
Comment 8 Soren Sandmann Pedersen 2006-04-25 18:11:37 UTC 
The real issue here is probably just that metacity is still somewhat confused about what visual it picks for the frame windows. It's not a compositor problem as such, but we might as well leave it here since anything having to do with ARGB visuals will probably have to be dealt with by me.
Comment 9 Elijah Newren 2006-05-03 23:01:07 UTC 
Well, if it's an ARGB visual problem with the frame, it may be related to bug 150465.
Comment 10 Thomas Thurman 2008-01-20 18:59:53 UTC 
Søren's compositor is not in trunk any more. -> OBSOLETE
Comment 11 Soren Sandmann Pedersen 2008-01-21 21:59:43 UTC 
Well, the issue of ARGB frame visuals is not going away. But it may not be worthwhile keeping the bug open.