Bug 202927 - Window decorations sometimes do not redraw properly
Summary: Window decorations sometimes do not redraw properly
Status: RESOLVED DUPLICATE of bug 199735
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-07 11:38 UTC by Ivo Anjo
Modified: 2009-08-07 11:45 UTC (History)
0 users

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


Attachments
Screenshot showing konsole with partially redrawn borders (78.64 KB, image/png)
2009-08-07 11:38 UTC, Ivo Anjo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivo Anjo 2009-08-07 11:38:23 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

I've been getting this intermittently since upgrading to KDE 4.3 earlier this week: sometimes when a window closes and focus changes to a window that was below, the decorations are not redrawn properly, and they stay a mix of the active state with the inactive state. If the focus is changed to yet another window, they are redrawn again correctly.

I was able to semi-reliably reproduce this by opening kwrite from inside konsole, and then closing it after some seconds: most of the time I can get this to happen.

It also seems to me that normally the part of the decoration that redraws correctly was the part that was covered by the window that disappeared, and that parts that were already visible are the ones that do not redraw (but should).

Finally, I don't think that this is style-specific: i'm using ozone but I can reproduce a similar thing using plastik.

Distro: openSUSE 11.1
X server: X.Org X Server 1.5.2
Driver: nvidia 185.18.14
Comment 1 Ivo Anjo 2009-08-07 11:38:53 UTC
Created attachment 35958 [details]
Screenshot showing konsole with partially redrawn borders
Comment 2 Martin Flöser 2009-08-07 11:45:16 UTC

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