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 401432 - Menu aren't erased within visualization area
Menu aren't erased within visualization area
Status: RESOLVED DUPLICATE of bug 168510
Product: totem
Classification: Core
Component: Movie player
2.16.x
Other All
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-01-27 19:27 UTC by DimkaS
Modified: 2007-01-28 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
screenshot (32.45 KB, image/jpeg)
2007-01-27 19:53 UTC, DimkaS
Details

Description DimkaS 2007-01-27 19:27:56 UTC
Please describe the problem:
Menu aren't erased within visualization area when visualization/movie does not fill this area copmletly.
Also, popping up progress bar and 'leave fullscreen' button are not erased completly - some parts left on black area, which is not covered with movie/visualization

Steps to reproduce:
1. Start playing some movie or audio track
2. resize window to have some black space above visualization area
3. open and close some top menus. The will not be erased correctly


for fullscreen
1. Start playing wide movie
2. switch to fullscreen
3. move mouse to see popping up controls
4. Wait for controls to disappear. Some parts of them will stay...



Actual results:


Expected results:


Does this happen every time?
yes, but only when there is some black space

Other information:
Note: i'm using russian localization
i've a screenshot.

Sorry for bad english ;)
Comment 1 DimkaS 2007-01-27 19:53:51 UTC
Created attachment 81330 [details]
screenshot
Comment 2 DimkaS 2007-01-27 19:57:58 UTC
xine-lib version 1.1.2 and GNOME
Comment 3 Bastien Nocera 2007-01-28 13:05:53 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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