Bug 220161

Summary:	Sliding popups leave artefacts
Product:	[Plasma] plasma4	Reporter:	Juha Tiensyrjä <juha.tiensyrja>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Kickoff menu leaving artefacts System tray notifications leaving artefacts

Description Juha Tiensyrjä 2009-12-26 19:09:29 UTC

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

I'm using KDE SC 4.4 beta 2 from the Kubuntu PPA.

I noticed that for example closing the Kickoff menu or waiting for system tray notifications to slide back in leave artefacts on the screen when the "Sliding popups" desktop effect is used. If desktop effects are not used or I disable Sliding popups, no artefacts stay on the screen.

My configuration is such that I have the panel on top of screen. I'm using a Lenovo Thinkpad T61 with a nVidia Corporation Quadro NVS 140M graphics adapter w/ proprietary drivers, if that changes anything. I'll try to post a couple of screenshots of the problem.

Comment 1 Juha Tiensyrjä 2009-12-26 19:10:59 UTC

Created attachment 39356 [details]
Kickoff menu leaving artefacts

This is a part of a screenshot that shows how the Kickoff menu leaves artefacts when Sliding popups desktop effect is used.

Comment 2 Juha Tiensyrjä 2009-12-26 19:11:39 UTC

Created attachment 39357 [details]
System tray notifications leaving artefacts

This is a part of a screenshot that shows how the system tray notifications leave artefacts when Sliding popups desktop effect is used.

Comment 3 Juha Tiensyrjä 2009-12-26 19:13:02 UTC

Oh, I forgot to include that the artefacts disappear at least when something is drawn over them (like the mouse cursor or some other window), or when the complete screen is redrawn (for example when I switch to another virtual desktop).

Comment 4 Dario Andres 2009-12-26 19:15:02 UTC

Reported at bug 215400 Thanks

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