> Actually, there _is_ a workaround which works all the time at the cost
> of a bit cpu time (at least for me). Just go to the compiz settings
> manager (ccsm). Activate the 'draw fire' plugin
It was of no help to me with any settings. The only thing that really
works, sort of, is manually "refreshing" the screen. I don't need any
extra gadgets to keep it under control, because I run a widget layer,
which is a big part of why I want compiz. So when anything on my screen
goes bad, I clean it up with two keystrokes -- activate and deactivate the
widget layer.
Those of us who remember working on remote machines through a VT100 will
not find it terribly annoying. Remember how we used to send Ctrl-L
whenever something wrote garbage on the screen? Same thing here. It's
wired in my brain. Much I as want to be rid of the bug, I can manage it
this way.
On Fri, 20 Feb 2009, Jan Krieg wrote:
> Actually, there _is_ a workaround which works all the time at the cost
> of a bit cpu time (at least for me). Just go to the compiz settings
> manager (ccsm). Activate the 'draw fire' plugin
It was of no help to me with any settings. The only thing that really
works, sort of, is manually "refreshing" the screen. I don't need any
extra gadgets to keep it under control, because I run a widget layer,
which is a big part of why I want compiz. So when anything on my screen
goes bad, I clean it up with two keystrokes -- activate and deactivate the
widget layer.
Those of us who remember working on remote machines through a VT100 will
not find it terribly annoying. Remember how we used to send Ctrl-L
whenever something wrote garbage on the screen? Same thing here. It's
wired in my brain. Much I as want to be rid of the bug, I can manage it
this way.