compositor produces artefacts starting in maverick

[Baptiste Mille-Mathias]

Binary package hint: xorg

Since I migrated my two machines to maverick they experience the same issue, under certain circonstances I didn't succed to define, there are some artefacts created on the display.
On the attached screenshot, you can see the artefact was created on the right part.

My two machines have different hardware, like nvidia versus intel, desktop versus laptop, dell versus lenovo.

I seems to be related to metacity as restarting it makes the artefacts go away.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAwrjFAAAAAAAEQAQOAHhN46ofFlFdPjCclUFQAAAABAQEBAQEBAQEBAQEBAQEBDRsAfFAgFjAwIDYAML4QAAAYixYAfFAgFjAwIDYAML4QAAAYAAAADwCBCjKBCigSAQAGr0RHAAAA/gBCMTQxRVcwNCBWNyAKAJk=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Oct 4 20:45:29 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
MachineType: LENOVO 7660RPG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=ddc7f73c-27c1-445c-ba5b-db3b6cbc9c0d ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.name: 7660RPG
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:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn7660RPG:pvrThinkPadT61:rvnLENOVO:rn7660RPG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7660RPG
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
     Subsystem: Lenovo T61 [17aa:20b5]

[Baptiste Mille-Mathias (bmillemathias)]

To reproduce:
- open a terminal and place it above or below a gnome-panel.
- click on a panel menu, and make sure the menu will hover the terminal.

you should have some artefact.

[Baptiste Mille-Mathias (bmillemathias)]

Killing gnome-panel will remove all interfact created by panel menu, but not all.

[Chris Halse Rogers (raof)]

I don't seem to be able to reproduce this. Do the steps that you've posted reliably reproduce this problem for you?

It looks like you're possibly running Compiz - if so, do you have any non-standard settings there? Is this reproducible under metacity?

[Baptiste Mille-Mathias (bmillemathias)]

On Wed, Oct 6, 2010 at 6:54 AM, Chris Halse Rogers <email address hidden> wrote:
> I don't seem to be able to reproduce this.  Do the steps that you've
> posted reliably reproduce this problem for you?
>
> It looks like you're possibly running Compiz - if so, do you have any
> non-standard settings there?  Is this reproducible under metacity?
>
I'm not running Compiz but metacity with compositing enabled. I should
test without compositing to see if the problem appears also.

--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés
[w] http://damnpeople.fr

[Baptiste Mille-Mathias (bmillemathias)]

Hi Brice,

Actually this is not only related to intel as I experience the same problem with a nvidia powered machine.

[bugbot (bugbot)]

Hey Baptiste,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Bryce Harrington (bryce)]

Think I'm seeing this same behavior from time to time, on an -ati system. In fact I reported it upstream as a driver bug before finding this report:

  https://bugs.freedesktop.org/show_bug.cgi?id=36699

So like the commenter above I think it's not a problem specific to -intel. Think this is the same as bug #708749 which is -nvidia. That user also found that killing metacity made the regions go away. So I think it's not an X issue at all, but I'll leave it open against xorg-server until it's more definitively understood.

[Bryce Harrington (bryce)]

Fwiw, I did not experience this issue in maverick, only in natty. And I don't use metacity compositing, just the non-composited environment. So possibly I have the same symptoms but a different bug?

[Bryce Harrington (bryce)]

Bugs 781536 and 781983 look vaguely similar

[Bryce Harrington (bryce)]

Also see bug 802747 which implicates 16-capture-before-unmap.patch in metacity.

[Bryce Harrington (bryce)]

Looking at metacity's change history, I see that 16-capture-before-unmap.patch was introduced for Unity2D, but caused bug #740387. A gconf option "capture-before-unmap" was added but this was left on by default. In metacity version 1:2.30.3-0ubuntu8 it was switched back off by default, but those who upgraded during the period that it was on would have seen it left on, and thus the corruption would remain.

So, it would make sense that anyone seeing corruption similar to what's described in this bug, check your gconf setting for the key:

  apps/metacity/general/capture-before-unmap

If that is ticked 'on' and you're seeing corruption, switch it off (and maybe restart?)

[Launchpad Janitor (janitor)]

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

[Bryce Harrington (bryce)]

As per the upstream bug report and my last few comments, this was pinpointed to a bug in metacity rather than X.

I think it may be resolved in metacity, as well, since it's been a long time since I saw this.

[Bryce Harrington (bryce)]

I've verified on Precise that this issue is no longer occuring.