Bug 268997 - Very often the displayed text and images in Google Chrome and Open Office are not fully refreshed while scrolling
Summary: Very often the displayed text and images in Google Chrome and Open Office are...
Status: RESOLVED DUPLICATE of bug 264259
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 22:43 UTC by Cadar Marius Emilian
Modified: 2011-03-29 20:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Cadar Marius Emilian 2011-03-20 22:43:51 UTC 
Version:           4.6 (using KDE 4.6.1) 
OS:                Linux

For example, when I open a .doc or .odt Open Office document, after scrolling, the text does not keep up the pace. I first noticed this bug when using Google Chrome and trying to select some text. It's displaying the text whit a row or two "behind" the normal position.

A similar bug noticed in System Configuration when trying to modify my theme or when trying to costumize the power options. The contents of the window remained stale when scrolling or when changing to another tab.

Reproducible: Sometimes




I also noticed this behaviour in the previous version of KDE but I think that after updating to KDE 4.6 it occurs more often.
Comment 1 Thomas Lübking 2011-03-21 18:06:08 UTC 
I assume you're using compositing?

Cross check this bug #264259
Seems exporting LIBGL_ALWAYS_INDIRECT=1 or upgrading Mesa (to 7.10) fixed it over there.

In any case please specify your GPU/Driver.
Comment 2 Cadar Marius Emilian 2011-03-29 20:23:42 UTC 
running this "LIBGL_ALWAYS_INDIRECT=1 kwin --replace&" in konsole seemes to fixed the problem
Comment 3 Cadar Marius Emilian 2011-03-29 20:25:55 UTC 
setting this bug as duplicate of bug #264259

*** This bug has been marked as a duplicate of bug 264259 ***