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 300852 - Refresh problem in Totem
Refresh problem in Totem
Status: RESOLVED DUPLICATE of bug 168510
Product: totem
Classification: Core
Component: general
1.0.x
Other All
: Normal minor
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-04-16 10:43 UTC by Joaquin Cuenca Abela
Modified: 2005-04-16 17:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Screenshot showing the totem refresh problem (51.45 KB, image/png)
2005-04-16 10:44 UTC, Joaquin Cuenca Abela 		Details

Description Joaquin Cuenca Abela 2005-04-16 10:43:48 UTC 
Please describe the problem:
When you play a music file, if you have the visualizations desactivated, the 
main area in totem (that I guess should remain black) don't refresh correctly 
(or at all in some cases).

Steps to reproduce:
1. Desactive the "Show visual effects when an audio file is played" in 
Preferences -> Display
2. Play a music file
3. Open any totem menu


Actual results:
The content of the menu remains visible in totem

Expected results:
The main content of totem would remain black

Does this happen every time?
Yes

Other information:
Comment 1 Joaquin Cuenca Abela 2005-04-16 10:44:23 UTC 
Created attachment 45321 [details]
Screenshot showing the totem refresh problem
Comment 2 Ronald Bultje 2005-04-16 11:50:40 UTC 
probably a dup of 155350.
Comment 3 Bastien Nocera 2005-04-16 12:47:33 UTC 
Joaquin, is this with the xine-lib (bug #168510) or the GStreamer backend (bug
#155350)?
Comment 4 Joaquin Cuenca Abela 2005-04-16 13:47:07 UTC 
It's using xine-lib. It looks indeed like #168510.
Comment 5 Bastien Nocera 2005-04-16 17:45:35 UTC 
I'll be closing it as a duplicate, thanks.

*** This bug has been marked as a duplicate of 168510 ***