Bug 177267

Summary:	graphical glitches with notifications and shadows
Product:	[Plasma] kwin	Reporter:	S. Burmeister <sven.burmeister>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aseigo
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screenshot

Description S. Burmeister 2008-12-08 23:23:54 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

As you can see in the screenshot the shadow of the amarok window shines through the notification window. If this is a kwin issue, please re-assign.

Comment 1 S. Burmeister 2008-12-08 23:24:37 UTC

Created attachment 29160 [details]
screenshot

Comment 2 Aaron J. Seigo 2008-12-09 06:07:10 UTC

that actually looks like a driver problem; what x.org driver are you using?

Comment 3 S. Burmeister 2008-12-09 07:36:36 UTC

Sorry, forgot to add that. NVIDIA 177.80

Comment 4 Aaron J. Seigo 2008-12-09 15:55:16 UTC

can you try quickly with the open source nv driver and/or update to the latest nvidia beta to see if that resolves these issues.

Comment 5 S. Burmeister 2008-12-14 12:41:39 UTC

The nv driver does not do any shadows, so I cannot say whether it works or does not. I tested 180.11, which shows the same behaviour. If I do not add anything, 180.16 does too.

Comment 6 Aaron J. Seigo 2008-12-15 18:08:12 UTC

"If I do not add anything, 180.16 does too."

can you follow up either way just to confirm? that way we know you didn't just forget ;)

Comment 7 Aaron J. Seigo 2008-12-25 09:03:39 UTC

i can confirm this with Intel chipset with desktop effects on.

not really sure it's related to kwin or x.org though. let's see what our friends at kwin think.

Comment 8 lucas 2008-12-25 09:12:43 UTC

Is your Amarok window configured to always be on top of other windows?

Comment 9 S. Burmeister 2008-12-29 14:04:25 UTC

No.

Comment 10 lucas 2009-01-05 03:54:16 UTC


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