Comment 7 for bug 718339

Bryce> Thanks for providing a good bug description.

You're welcome. I'm try to stay upto date with all the latest Natty
packages and doing full reboots on this desktop to test out any
changes.

Bryce> l8gravely, you should also run 'apport-collect 718339' to attach some
Bryce> logs and config files we like to have for troubleshooting X bugs.

I'll do this when I get home tonight, can't seem to make it or
'apport-cli -u 718339' work from the CLI properly.

Bryce> The specificity of this to compiz suggests an issue in mesa or
Bryce> kernel drm, rather than xterm. For now let's treat it as a
Bryce> mesa bug. Might be -radeon specific.

I suspect so too, esp once I saw it repeating in other terminals.

Bryce> On current natty running -radeon with no compiz, I can confirm
Bryce> that the issue does not occur (tested with xterm running top,
Bryce> mutt, etc. and resizing the window). (I'll test with compiz
Bryce> once I've finished building a new mesa to test.)

Do you find that screen refreshes or window moves are *slower* when
you do this? I was seeing a flash of the entire screen which was
quite annoying. It might be releated to the vsync blanking issues
Dave Airle was chasing down in DRM/MESA/Radeon drivers.

Bryce> Meanwhile, please do attach screenshots (or digital photos if
Bryce> the corruption doesn't show up with a simple screenshot). With
Bryce> corruption bugs we ALWAYS like to have images since often what
Bryce> looks like noise can reveal details to a knowledgeable expert
Bryce> about what the video memory is up to.

Will do, but with the latest updates, the screen isn't getting
corrupted anymore on re-size, but it *is* getting corrupted when I use
an xterm to ssh into another server and run emacs inside a 'screen'
session. The screen fails to update, or blanks lines or characters
randomly. Doing a Ctrl-L to force a refresh fixes it for a second,
but the problem comes back.

I'll send more details tonight when I get a chance.

Bryce> Also, there have been several other xterm/corruption bug
Bryce> reports lately (see also bug #713440 and bug #717114). A photo
Bryce> would help prove whether this is a dupe of one of those or not.

I've gone and looked at these bugs and while they sound similiar, they
don't quite have the same issues that I'm seeing. But I suspect that
since I'm on older Radeon hardware, that it's the same root cause, but
just manifests itself differently.

Bryce> Again, please provide a photo and run apport-collect 718339. Thanks!

Will do tonight! Thanks.

John