Bug 202624

Summary:	kwin: rendering problem with colorized window-borders in "Ozon" Window-Style when compositing is enabled
Product:	[Plasma] kwin	Reporter:	Marc Schiffbauer <mschiff>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Rendering_NOT_ok_01 Rendering_NOT_ok_02 Rendering_ok_01 Rendering_ok_02

Description Marc Schiffbauer 2009-08-05 14:05:28 UTC

Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Gentoo Packages

Following setup:

* nvdia driver (problem persists with several version that existed during last year or so)
* kde 4.3.0
* compositing enabled
* "Ozon" win style with blue color for active windows and grey color for windows without focus

It happens often that the vlue color is not rendered corectly, if it happens only the buttons on the window border look correct, the rest ist just grey, not blue.

How to trigger the issue:
SOmetimes its hard to trigger the issue, but I think it has something to do with minimizing/maximizing windows. Best was to trigger it is to just keep the settings like I described and work with it. It will showup then at some time.

Comment 1 Marc Schiffbauer 2009-08-05 14:13:40 UTC

Created attachment 35861 [details]
Rendering_NOT_ok_01

Comment 2 Marc Schiffbauer 2009-08-05 14:14:32 UTC

Created attachment 35862 [details]
Rendering_NOT_ok_02

Comment 3 Marc Schiffbauer 2009-08-05 14:15:27 UTC

Created attachment 35863 [details]
Rendering_ok_01

Comment 4 Marc Schiffbauer 2009-08-05 14:17:39 UTC

Created attachment 35864 [details]
Rendering_ok_02

Comment 5 FiNeX 2009-08-05 18:50:43 UTC

Does it happen only with compositing enabled?

Comment 6 Marc Schiffbauer 2009-08-06 03:04:37 UTC

(In reply to comment #5)
> Does it happen only with compositing enabled?

Yes, exactly.

Comment 7 Thomas Lübking 2009-08-06 15:01:09 UTC


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