Screen corruption after the latest upgrade

[Martin Albisetti]

After today's upgrade, I get corruption on my screenl Attaching a photo (a screenshot cleans up the corruption) and a screenshot, since windows now also seem to overlap behind the menus.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.0-0ubuntu5
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Tue Apr 10 16:05:02 2012
DistUpgraded: 2011-12-02 04:59:49,632 DEBUG The following packages are marked for removal: linux-headers-3.0.0-13-generic linux-image-3.0.0-14-generic linux-image-3.0.0-12-generic-pae python-cherrypy3 libgdata1.7-cil linux-headers-3.0.0-14-generic-pae libx264-116 python-clientform linux-headers-3.0.0-12 linux-headers-3.0.0-13 linux-headers-3.0.0-14 linux-image-3.0.0-12-generic linux-image-3.0.0-13-generic-pae linux-headers-3.0.0-14-generic liblzma2 libpython2.6 linux-headers-3.0.0-12-generic linux-image-3.0.0-13-generic libexiv2-10 linux-headers-3.0.0-13-generic-pae
DistroCodename: precise
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO 05962RU
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=7879f0a9-2c49-4bde-b095-b134e2626300 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to precise on 2011-12-02 (130 days ago)
dmi.bios.date: 11/03/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8FET32WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 05962RU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn05962RU:pvrThinkPadX120e:rvnLENOVO:rn05962RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 05962RU
dmi.product.version: ThinkPad X120e
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Bryce Harrington (bryce)]

Hmm. Well nothing graphical has changed in X recently (there's been some synaptics fixes, but that wouldn't cause this.) However, the fact that it shows up in photos but not screenshots fairly strongly suggests a video driver issue rather than, say, a compositing bug.

Nothing indicative in the logs (for corruption bugs there usually isn't though). The fglrx installation looks fine. I do notice in your xorg.conf there's some things set, like TargetRefresh. I don't know what that parameter does, so you might try commenting it out to see if it has any effect. Everything else looks normal. (Btw, you may be able to run fglrx with no xorg.conf now; that might be worth testing, but be prepared to copy it back in place in case X doesn't boot.)

Can you tell me more about the symptoms? Does the corruption show up 100% of the time, or only in certain apps? Is it only associated with text fonts? Does it always look the same as in the photo, or does it vary?

Can you reproduce this behavior with Unity2D or Gnome Classic (no effects)?

If you disable fglrx and boot with -ati, does the corruption still occur?

[Martin Albisetti (beuno)]

On Wed, Apr 11, 2012 at 3:42 PM, Bryce Harrington
<email address hidden> wrote:
> Hmm.  Well nothing graphical has changed in X recently (there's been
> some synaptics fixes, but that wouldn't cause this.)  However, the fact
> that it shows up in photos but not screenshots fairly strongly suggests
> a video driver issue rather than, say, a compositing bug.
>
> Nothing indicative in the logs (for corruption bugs there usually isn't
> though).  The fglrx installation looks fine.  I do notice in your
> xorg.conf there's some things set, like TargetRefresh.  I don't know
> what that parameter does, so you might try commenting it out to see if
> it has any effect.   Everything else looks normal.  (Btw, you may be
> able to run fglrx with no xorg.conf now; that might be worth testing,
> but be prepared to copy it back in place in case X doesn't boot.)

The current xorg.conf has been full generated by the amdaccel control
panel, so no manual futzing.
I commented out TargetRefresh and it didn't help.
Removing xorg.conf, however, did.
From what I can tell, it was created because I wanted to have a dual
monitor set up, and without tweaking it from the amdaccel app, I can't
get more than 1600x1600 between both monitors, which makes it feel
like 1994 all over again :)

> Can you tell me more about the symptoms?  Does the corruption show up
> 100% of the time, or only in certain apps?  Is it only associated with
> text fonts?  Does it always look the same as in the photo, or does it
> vary?

It seems to happen with everything, not linked to a specific app.
Images, text, all of it. If I scroll up and down, it fixes the
corruption, but only until something draws itself again.

> Can you reproduce this behavior with Unity2D or Gnome Classic (no
> effects)?
>
> If you disable fglrx and boot with -ati, does the corruption still
> occur?

I haven't tried these, but am happy to if you think it'll add valuable
information.

--
Martin

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.