Bug 809052

Created attachment 574477 [details]
corrupted windows displaying

This problem is not only with firefox and fallback mode. 
In my VM it's happening always. I attached image showing Nautilus + Firefox - both are corrupted.

Panels are OK, login screen too.

I tagged this bug as blocker F17Beta.

(I tried LXDE also and there is everything ok with displaying)

I can reproduce by running F17 Beta RC2 i686 Live in VM. The desktop wallpaper is distorted and so is every application I run. The only thing that is not distorted is Gnome Shell UI. In fallback mode everything works ok (David's screenshot also indicates he was running gnome-shell, not fallback mode).

I see this problem only with vnc+cirrus, I don't see it with spice+qxl.

Re-assigning to gnome-shell.

Or, more probably, this could be a problem in llvmpipe or mesa (since cirrus has only 9MB RAM and there were some changes regarding this in llvmpipe/mesa lately).

Looks very much like it's a mesa issue somehow. Ajax?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

It is very interesting that all applications I tried are blurred, but gnome-terminal runs just fine.

The rendering is broken with following packages:
mesa-dri-drivers-8.0.1-9.fc17
llvm-libs-3.0-8.fc17 or llvm-libs-3.0-10.fc17

I'm experimenting with previous composes, I have a feeling this is a very recent regression.

Voila, it works with F17 Beta RC1 live:

mesa-dri-drivers-8.0.1-2.fc17
llvm-libs-3.0-8.fc17

Definitely a regression in mesa.

(In reply to comment #5)
> It is very interesting that all applications I tried are blurred, but
> gnome-terminal runs just fine.

Presumably the difference is that gnome-terminal uses an ARGB visual while other applications use RGB visuals, so different code pathsiin Mesa and the X server are exercised.

Discussed at 2012-04-02 QA meeting, acting as a blocker review meeting. Agreed that this is a blocker, under the criteria "The release must install and boot successfully as a virtual guest in a situation where the virtual host is running the previous stable Fedora release, using Fedora's current preferred virtualization technology", "The release must be able host virtual guest instances of the same release, using Fedora's current preferred virtualization technology" and "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention", in the case of a virtual machine using the cirrus driver.

We believe this is a sufficiently common case to consider this a blocker: any VM definition created prior to F16 that wasn't explicitly changed to use qxl will still be using cirrus, and people often re-use existing VM definitions rather than creating new ones. Also, any newly-created 32-bit VM will still default to using the cirrus driver. We believe qxl is only used by default on 64-bit VMs created with Fedora 16 or Fedora 17.

ajax is aware of the bug and working on a fix. It is a regression between mesa -1 and -9, caused by a performance improvement ajax does not want to lose.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

There's two changes I want to make for this.  One is to switch cirrus to 16bpp, which should both be a performance improvement and align it with the other fallback drivers, which prefer 16bpp to 24bpp.  The other is a fix to the Mesa code itself for paths other than 32bpp.  Note that the 24bpp path in Mesa might still be broken, but honestly 24bpp is pretty broken all the time anyway.

xorg-x11-drv-cirrus-1.3.2-19.fc17,mesa-8.0.2-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/xorg-x11-drv-cirrus-1.3.2-19.fc17,mesa-8.0.2-2.fc17

Fix confirmed, I installed the updated packages in a live boot, restarted X, and got a nice non-corrupted Shell. Thanks ajax!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

so I did notice one problem - if you boot KDE with cirrus/vnc and run Konqueror, you see this:

http://www.happyassassin.net/extras/kde_purple.png

with the new mesa and cirrus. With Beta RC2 - mesa 8.0.1-1 - there's no such issue. I don't know the status of 8.0.1-9.

overall, the state with 8.0.2-2 is still probably better, but I figured it was worth noting.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Confirmed that a VNC/cirrus VM displays Firefox just fine with the Beta RC3 desktop live.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

xorg-x11-drv-cirrus-1.3.2-19.fc17, mesa-8.0.2-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to comment #12)
> so I did notice one problem - if you boot KDE with cirrus/vnc and run
> Konqueror, you see this:
> 
> http://www.happyassassin.net/extras/kde_purple.png
> 
> with the new mesa and cirrus. With Beta RC2 - mesa 8.0.1-1 - there's no such
> issue. I don't know the status of 8.0.1-9.
> 
> overall, the state with 8.0.2-2 is still probably better, but I figured it was
> worth noting.
> 
> 
> 
> -- 
> Fedora Bugzappers volunteer triage team
> https://fedoraproject.org/wiki/BugZappers

This update really breaks the whole Plasma Desktop, it's not affecting the apps (here Konqueror) only. I already filled #810161 (I missed this bug report).