Bug 12450 - Gwd rendering errors with metacity_theme_opacity = 1, maximized, use_metacity_theme
Summary: Gwd rendering errors with metacity_theme_opacity = 1, maximized, use_metacity...
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: App/compiz (show other bugs)
Version: unspecified
Hardware: All All
: medium major
Assignee: David Reveman
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-16 18:45 UTC by Andrea Cimitan
Modified: 2009-02-15 03:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Oops wrong screen (111.21 KB, image/png)
2007-09-16 18:45 UTC, Andrea Cimitan
no flags Details
Screenshot of the problem (135.56 KB, image/png)
2007-09-16 18:55 UTC, Andrea Cimitan
no flags Details

Description Andrea Cimitan 2007-09-16 18:45:11 UTC
I got this bugs for _months_... And I'm not alone.
The metacity titlebar gets corruption on maximized state AND use_metacity_theme.

The strange thing is that today I've set the metacity_theme_opacity in /apps/gwd (gconf) to 0.9 and the curruptions disappears to nearly 98% (I've just an hint of cottuption on the top-left... but not completely corrupted as in the screenshot).
So it seems a problem in the metacity rendering part, which is completely visible (80% of corruption) when using opacity = 1 for active and inactive windows.

Other guys... (probably all of us have this problem as I don't know anyone without it)
http://forum.compiz-fusion.org/showthread.php?t=3831
Comment 1 Andrea Cimitan 2007-09-16 18:45:53 UTC
Created attachment 11594 [details]
Oops wrong screen
Comment 2 Andrea Cimitan 2007-09-16 18:55:00 UTC
Comment on attachment 11594 [details]
Oops wrong screen

sorry mistake in upload
Comment 3 Andrea Cimitan 2007-09-16 18:55:33 UTC
Created attachment 11595 [details]
Screenshot of the problem
Comment 4 Andrea Cimitan 2007-10-22 11:21:56 UTC
this is the piece of code that causes the bug:
NOTICE: REMOVING 8 OF THESE LINES FIXED THE PROBLEM, SO IT'S LIKE GWD CAN'T HANDLE TOO TINT OPERATIONS OR LIKE IT HAS SOME LEAKS

<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="1" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="1" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="1" y="2" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-2" y="2" width="1" height="1"/>
	
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="3" y="2" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-4" y="2" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="3" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="3" width="1" height="1"/>
	
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="3" y="height-3" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-4" y="height-3" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="height-4" width="1" height="1"/>
<tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="height-4" width="1" height="1"/>
Comment 5 Brandon Wright 2007-10-23 04:47:02 UTC
(In reply to comment #4)
> this is the piece of code that causes the bug:
> NOTICE: REMOVING 8 OF THESE LINES FIXED THE PROBLEM, SO IT'S LIKE GWD CAN'T
> HANDLE TOO TINT OPERATIONS OR LIKE IT HAS SOME LEAKS
> 
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="1" width="1"
> height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="1"
> width="1" height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="1" y="2" width="1"
> height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-2" y="2"
> width="1" height="1"/>
> 
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="3" y="2" width="1"
> height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-4" y="2"
> width="1" height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="3" width="1"
> height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="3"
> width="1" height="1"/>
> 
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="3" y="height-3"
> width="1" height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-4" y="height-3"
> width="1" height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="2" y="height-4"
> width="1" height="1"/>
> <tint color="shade/gtk:bg[SELECTED]/0.6" alpha="0.2" x="width-3" y="height-4"
> width="1" height="1"/>
> 
This makes me wonder whether this is similar to another gwd bug--

Does adding the --sync parameter to gtk-window-decorator fix the problem?
Comment 6 Andrea Cimitan 2007-10-23 05:38:30 UTC
yes this fixes.
but why we should add the synchronisation? Maybe the --sync could slowdown the performance on low systems.
I guess it's better to fix the leak
Comment 7 Andrea Cimitan 2007-10-23 07:07:59 UTC
the titlebar is rendered better but now buttons sometimes are not updated and appear slways in *pressed* state. (using --sync)
:|
Comment 8 Danny Baumann 2009-02-15 03:59:33 UTC
This was an issue with older versions of the Nvidia drivers, which is fixed in the 180.xx series.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.