Bug 48836

Summary:	Visual glitch when moving window
Product:	[Plasma] kwin	Reporter:	JWoltman <woltmancrap>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	chp802, xtreyreader
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Sample of glitch

Description JWoltman 2002-10-07 17:21:00 UTC

Version:            (using KDE KDE 3.0.8)
Installed from:    Compiled From Sources
Compiler:          GCC 3.2 
OS:          Linux

Moving windows sometimes produces a glitch in the window menu/icon. It looks like the Window's outline (the outline drawn when moving/resizing) is not erased, and appears over the icon. I'm using the nVidia drivers, version 2960. I have a screenshot if needed.

Comment 1 JWoltman 2002-10-07 17:21:44 UTC

Created attachment 164 [details]
Sample of glitch

Here's an example of the glitch

Comment 2 Lubos Lunak 2002-10-08 14:07:45 UTC

 What Qt version do you use? In some quite recent Qt version there was a XRender related fix 
that could be possibly related (I don't remember the exact Qt version though).

Comment 3 JWoltman 2002-10-08 17:54:29 UTC

Qt 3.0.5, the version I used for KDE 3.0.3. Should I upgrade to Qt 3.1 beta 2 also?

Comment 4 Lubos Lunak 2002-10-08 18:33:37 UTC

 Qt-3.0.5 should be enough IIRC. Do you use transparent window moving? It looks a bit like if 
the transparent move frame stayed there. Does it happen also on other places than the icon?

Comment 5 JWoltman 2002-10-08 18:50:37 UTC

It happens on with the icon (KDE default theme) and the Arrow (window menu)
button on the Keramik theme. I'm not sure what you mean by transparent moving. I
just have the outlines enabled (when I move a window all I see is the outline,
not the window's contents).

Comment 6 Lubos Lunak 2003-01-02 17:29:18 UTC

*** Bug 52416 has been marked as a duplicate of this bug. ***

Comment 7 Lubos Lunak 2003-03-18 19:29:13 UTC

I believe I have fixed the problem, but if it appears again, please reopen the bug.