Bug 683850 - Macroblock changing luminosity in gnome3
Summary: Macroblock changing luminosity in gnome3
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 13:56 UTC by Fabien Archambault
Modified: 2011-03-13 22:17 UTC (History)
4 users (show)

Fixed In Version: xorg-x11-drv-nouveau-0.0.16-23.20110303git92db2bc.fc15.x86_64
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-13 22:17:36 UTC
Type: ---


Attachments (Terms of Use)

Description Fabien Archambault 2011-03-10 13:56:33 UTC
Description of problem: In Fedora 15 alpha (all updates from today done except gdm which is buggy), when I change the luminosity, before seeing the correct picture of the luminosity being modified many macroblocks are displayed.


Steps to Reproduce:
1. Load gnome and wait a little until everything is loaded
2. In the laptop change the luminosity
3. See macroblocks then the luminosity changer indications
  
Actual results: no macroblocks.


Additional info:
I tried to see if it was due to a delay in the response but I waited I would say 1 minute after loading and on the first try it happens.
Then when loaded once it is harder to get it back. I am able to see it again, very briefly, with this:
* Change luminosity
* Change sound
* Change luminosity and sometimes the macroblocks are again here.

I will try to do a screenshot but it is very sudden...
The graphic card is in the smolt profile: http://www.smolts.org/client/show/pub_97a51b9b-9c31-4027-b192-acdfa7376036

Comment 1 Fabien Archambault 2011-03-11 08:44:06 UTC
Solved with the update of today : xorg-x11-drv-nouveau-0.0.16-23.20110303git92db2bc.fc15.x86_64

Comment 2 Ben Skeggs 2011-03-13 22:17:36 UTC
Thanks for letting us know.


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