Bug 577473 - compiz erratic with updating the entire screen in fedora 13 alpha
Summary: compiz erratic with updating the entire screen in fedora 13 alpha
Keywords:
Status: CLOSED DUPLICATE of bug 573366
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-27 10:02 UTC by Gautam Ghare
Modified: 2010-03-27 12:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-27 12:04:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gautam Ghare 2010-03-27 10:02:27 UTC
Description of problem:

When desktop effects are enabled in Fedora 13 alpha (gnome 2.29.92); parts of the screen do not get updated on the display when they should. This is particularly observed when playing gnome-games (robots, freecell, ...) or even browsing the web; when firefox has to display a lot of tables. The screen shows an old image until you have moused over the modified region and the mouse cursor redraw causes the displayed image to be updated; or the minimizing the window and restoring it refreshes the application display.

Version-Release number of selected component (if applicable): 0.8.4-6.fc13


How reproducible:
Always

Steps to Reproduce:
1. Enable desktop effects
2. Play a game of robots, or freecell solitare
3.
  
Actual results:
Image updates made by the application are not sometimes not rendered until another reason for the update occurs. For example movement of the mouse cursor over the image region; or minimizing the application and restoring it.

Expected results:
Image updates should be rendered to the screen



Additional info:

Comment 1 Adel Gadllah 2010-03-27 12:04:45 UTC
This is a mesa bug.

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

Comment 2 Adel Gadllah 2010-03-27 12:05:26 UTC
Err .. wrong bug.

Set duplicate to the correct bug.


Note You need to log in before you can comment on or make changes to this bug.