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 571854 - Metacity composite don't work well with totem
Metacity composite don't work well with totem
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-02-15 16:53 UTC by s.malacarne
Modified: 2020-11-06 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description s.malacarne 2009-02-15 16:53:06 UTC 
Please describe the problem:
I activate metacity composite support and all work correctly (shadows and transparency). I use ubuntu 8.10 64 bit, ATI X800, free ati driver 6.9.

Problem happens when i use watch a video on totem (or a mp3 with visual effect). When i put a window above video shadow and transparency don't work correctly. Shadows are rendered like a black solid square and transparency just don't work (all black).

Steps to reproduce:
1. use metacity composite support
2. start a movie with totem
3. move a window over the movie 


Actual results:
shadows are solid black

Expected results:
shadows should look like a shadows, soft black with transparency

Does this happen every time?
yes

Other information:
flash video in a browser work perfectly, tv on Me TV has problem like totem
Comment 1 André Klapper 2020-11-06 20:05:08 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.