Bug 164330

Summary:	Graphical corruption when right clicking on desktop or bringing up KickOff
Product:	[Unmaintained] plasma4	Reporter:	Adam Spain <bugs>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	lucas
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Adam Spain 2008-06-17 20:28:40 UTC

Version:            (using KDE 4.0.80)
Installed from:    Ubuntu Packages
OS:                Linux

After I login, when I first right click on the desktop there is graphical corruption for a fraction of a second in the area of the right click menu before it appears and displays normally.  Usually it doesn't happen if I right click on the desktop again, but it does seem to randomly happen at other times when I right click on the desktop.  Also, sometimes there is similar graphical corruption for a fraction of a second when I click the 'K' icon to bring up the KickOff menu the first time after I login.  I had this problem in KDE 4.03 (Kubuntu Hardy) and it is still present in the Kubuntu KDE 4.1 Beta 1 packages.  

I'm running the nvidia proprietary driver using two monitors, with the KDE compositing features turned off.  I've found some other users have the same problem (1) and another user (2) who claims it happens with the ATI proprietary drivers too (although I can't test that).

1: http://www.kubuntuforums.net/forums/index.php?topic=3095128
2: http://ubuntu-utah.ubuntuforums.org/showthread.php?t=788023&page=3#post5009121

Comment 1 Adam Spain 2008-06-17 20:51:02 UTC

One other point.  The graphical corruption when right clicking on the desktop only happened when using the Oxygen theme.  I couldn't get it to happen when using Plastique.

Comment 2 Aaron J. Seigo 2008-07-06 23:23:17 UTC

this seems to have gone away here, which is good. however, this was not a plasma issue. it was either an oxygen style isssue, a qt4 issue or an x.org driver issue (not sure which it was, tbh). upstream in any case ...