FVWM: OpaqueMove smears windows content with fglrx 10.x and above

2011-02-07 Thread Harald van Pee
Hi,

since I use amd/ati driver fglrx with version 10.x (currently I use 11.1)
I have the problem that the content of a window which was moved fast around in 
OpaqueMove mode becomes smeared. Depending on how fast and how long one moves 
one can not read any text in that window. 
Firefox redraws the window content directly after releasing the mouse (xterm 
does not), but the window title and frames are still damaged until I change 
the size of the window.
Slow Moving of the window does not result in smearing of the content.
Switching off  OpaqueMove helps for most programs, but for example nedit has 
still some problems.

Has anybody an idea what option in fglrx or fvwm one can use to avoid that 
smearing?
With the kde desktop the problem does not occur.
 
I use debian lenny on my notebook with ati radeon HD 2400 XT graphics card and 
the debian fvwm package.
I have also installed a self compiled fvwm 2.5.31 which works but have the 
same problem.
I can not see this problem with fglrx 8.x or 9.x but the more recent drivers 
has better support for my notebook.

Since I use lenny I have no problem with fvwm even not in combination with 
beamers and openoffice or acroread, it just works.

Thanks,

Harald

  



Re: FVWM: OpaqueMove smears windows content with fglrx 10.x and above

2011-02-07 Thread Thomas Adam
On Tue, Feb 08, 2011 at 02:33:25AM +0100, Harald van Pee wrote:
> Hi,
> 
> since I use amd/ati driver fglrx with version 10.x (currently I use 11.1)
> I have the problem that the content of a window which was moved fast around 
> in 
> OpaqueMove mode becomes smeared. Depending on how fast and how long one moves 
> one can not read any text in that window. 
> Firefox redraws the window content directly after releasing the mouse (xterm 
> does not), but the window title and frames are still damaged until I change 
> the size of the window.
> Slow Moving of the window does not result in smearing of the content.
> Switching off  OpaqueMove helps for most programs, but for example nedit has 
> still some problems.

Nothing FVWM can do about this.  Sounds like a display driver issue to me.

-- Thomas Adam

-- 
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.