glxgears image split across screen in hardy 64-bit

Exact same problem by me, allmost same config (amd64, ati x200M, fglrx in use)

There have been reports of this sort of defect (vertical tearing, or is it horizontal tearing?) with fast-moving video for years. The OpenGL DRI configuration now allows a vblank_mode setting to control synchronization with vertical refresh, but it's not enabled in fglrx, only in the open-source radeon driver.
<rant>
What is irritating is that the behavior suddenly re-appears after an upgrade, and no-one takes any notice of bug reports. Ubuntu devs tend to say "Oh, it's a proprietary driver, we can't do anything", while the ATI people say "Works fine in other distros, must be a Ubuntu problem", and nothing gets fixed.

At the moment I have the following video-related problems, all on one machine (ati Radeon Xpress 200M (5955)):

Hardy 32-bit with open-source radeon driver: DRI falls back to unacceptable slow rendering running GoogleEarth; Firefox 3.0 fails to render pages containing transparent picture elements because of a Cairo-related bug; won't run compiz; suspends but won't wake up properly.

Hardy 64-bit with fglrx proprietary driver: vertical tearing (this bug); Googleearth renders frame, frame-contents, and extra windows (tips, photos, info) all independently, and can't synchronize over-lays properly - looks a mess; same Firefox 3.0 cairo bug as 32-bit; won't run compiz; won't suspend.

Meanwhile, Gutsy goes on running everything fine, with fglrx/xgl, including compiz; but won't suspend. And Windows XP just runs, without driver updates or fuss.

 I'm really looking forward to a release (Hardy?, Hardy+1?......) that FIXES problems rather than introducing new ones, or resurrecting old ones.........
</rant>

same problem in my laptop fs amilo a1650g ati x200m (hardy 64bit)
sometime system also crash with a black screen

this post http://ubuntuforums.org/showthread.php?t=698675 seems to indicate that the problem is not from fglrx, but from soething in the config that should be added.

--
Z.

well, one of the reports seems to be about a similar effect in a different machine (not ati/fglrx) that might be due to a program that isn't installed for the other two. No-one has suggested a fix for the original problem, which persists.

since we have a confirmation, I am changing this to "Confirmed". Can someone please pick it up?

I can confirm this bug too, the strange thing is, it doesn't always happen. I get this result about 9/10 tries. Sometimes it does run though, at the same framerate as the torn picture does.

This bug disappeared after I updated to the 8.3 fglrx driver using EnvyNG. I don't know whether it was a bug in the earlier drivers or an incorrect configuration setting that EnvyNG got right.

I can confirm this bug. The command glxgears produces exactly the same results as shown in the first post's screenshot.

I am using Gutsy 7.10.
Config: Amd 64 x2, ATI HD2600XT (latest driver installed through ENVY: Ver 8.455), Compiz disabled.

I have installed EVE-online and run glxgears through the game's configuration program. It runs perfectly (the gears appear as they should, as you can see in Screenshot_1).

But when I run the same command in terminal the results are like those in Screenshot_2.

Running Gutsy 7.10 64-bit (didn't mention earlier).

By the way, I can't play the game. It crashes just before entering the 3D world.

Installing latest fglrx drivers seems to fix this issue.

I don't know if they could be put in hardy, but it may be a good idea since it's probably the best simpelst way to fix that problem...

--
Z.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in fglrx-kernel-source.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Also I'm closing this report as the last post says that this is fixed in newer fglrx drivers.