Openoffice causes display errors on plasma workspace when running compiz.

This is the same issue as that reported here: http://bugs.kde.org/show_bug.cgi?id=157017.
Disabling the blinking cursor in qtconfig-qt3 solves the issue.

I realize that this bug should not have been reported as affecting compiz.

Driver bugs, so switching this over to affecting the nvidia drivers.

Same here:
System is: KUbuntu v8.04.1 KDE4 (apt up-to-date as of today) with NVidia GeForce 6600 video card (latest propietary drivers) running Compiz.
This bug may be related to Plasma and plasmoids, or may not. The problem is that, from time to time (I could not detect a consistent trigger) my task manager bottom bar goes psychodelic as if it was on an acid trip. I mean:

-Portions of the bar, such as the clock or the task icons (aka: "Objects") disappear suddendly (they show transparent).
-Objects that have disappeared do appear suddendly, or on mouse rollover.
-Objects blink from time to time showing background desktop wallpaper. Sometimes they look altered pixel color look (very colourful! OMG it's full of stars!)
-Objects move along the bar switching positions during fractions of a second without user intervention.
-Objects show a striped look such as a broken television, for fractions of a second, when clicked or mouse-rolled-over.

What, can only NVidia fix this?

I hope there is a way around waiting for Nvidia to fix this, it seems they aren't collaborating much lately...
I can confirm that the bug occurs only when OpenOffice is active.
There are other problem possibly associated, such as al the "Leave" button icons not loading correctly (Logout, Lock, Switch User, Shutdown, Restart), neither the icons in the "End session" modal window.
By the way, it takes far too many mouse click to get outta the session... one or two less would be nicer.

I use intrepid and nvidia 177.80 report same symptoms as Aswarp, Changing to 2d accelerated driver "nv" fixed issue. The issues most happen when open office is the focused window.

I am on intrepid.

It is not only problem with OOo. The application tightVNC causes the same (and worse) things.

Prasisko wrote:
> It is not only problem with OOo. The application tightVNC causes the
> same (and worse) things.
>
Does using the nvidia-glx-180 driver fix it for you?

Vik :v)

I've not tried it yet.