Well, he's not a Kubuntu developer, that's for sure. No Kubuntu developer in their right mind would blame python-kde4, a source package that hasn't been used for two releases for corruption issues. The default desktop doesn't even really use it. All it is are python bindings to the KDE api, and since I have to explain that its pretty clear that RK is not a developer. He probably is just trying to jerk my chain. If you ever actually contribute anything more than a few bug reports here and there I may start to respect your judgment, but as it stands it is pretty clear that you do not know what you are doing.

But, being the nice guy that I am, I did do some more research on the bug. (I am also a KDE developer) Previously, the consensus between KDE developers was that this was a graphics driver bug. (For example, https://bugs.kde.org/show_bug.cgi?id=189059 , https://bugs.kde.org/show_bug.cgi?id=187991)

In reality this is a somewhat complex issue, with many factors determining whether or not the user will actually see the issue. It should be noted that two issues have been reported in this bug report initially. 1) The disappearing of the Plasma elements and b) the actual corruption in the panel. The panel corruption likely is a driver bug, and the disappearance issue is the complex one.

Anyways, on to the issue. As it turns out, graphical Plasma elements start to disappear when the video card runs out of pixmap space. Normally this doesn't happen, unless something is leaking pixmaps and is not destroying them after they are done being used. This explains why people using different video cards see this, and why not all people using the same video card see this. it could even be said that one person using the same driver as another but having a card with less VRAM could see this more often than the one who had a card with more VRAM (if he saw it at all)

Recently such a leak was found in Qt that fits the ticket. (Documented here: http://bugs.kde.org/show_bug.cgi?id=183191) There was a leak in the digital clock applet that exasperated the issue further, although it was not the core cause of the bug. (And definitely even the KDE component of this bug was not a kde4libs issue.)

In conclusion:

- This is not, I repeat *not*, and never ever was at all a kde4libs bug as you so adamantly proclaimed.
- Not a pykde issue, though this goes without saying
- Not an issue with the python-kde4 package which has been unused since Hardy
- This is a Qt issue which is scheduled to be fixed in Qt 4.5.2
- The KDE portion of this (which affected kdebase-workspace, but was not the main bug) has already been fixed in KDE 4.3 beta2.
- It was understandable to have thought that this was a driver issue, as that had been the previous consensus
- RK's little shenanigans would have not really changed anything, and the issue would have gone away once everybody upgraded anyway. All you did was cause me unnecessary stress in an attempt to piss me off. 

You are quite lucky that I even took time to research this answer and give you this information, though I suppose I did it for those who care more about the bug than for those who care more about pissing me off.

Anyway, this is a duplicate of bug 343944, and you better not screw that one up.