Version: (using KDE 4.3.1) OS: Linux Installed from: Ubuntu Packages When I click on the battery monitor plasmoid in my bar it appears as expected. However the animation lacks quite a bit. My guess is that the animation consists of two painted frames, the rest of the animation time the panel on the way up doesn't move. The strange thing is that the hiding animation works much much better. Not fully lackless, but almost. I'm using an nvidia Quadro NVS 140M with driver 185.18.36
- Are you using Desktop Effects / Compositing ? Thanks
yes
- Does the effect/appearance change if you disable the effects?
yes. There is no animation when the effects are off. It just appears and disappears-
- Does this also happen with some other widgets in the panel? (like the Kickoff menu, the Device Notifier, the Dictionary or the clock's calendar) Thanks
Created attachment 38736 [details] animations lack screencast Recorded this screencast of the lacky animations with KDE SC 4.3.2 and an nvidia graphics-card using nvidia driver 185. It handles all the kwin effects quite well, so it's weird that plasma animations still lack.
for comment #5: Yes. Other animations lack as well. As can be seen by the screencast above.
this is a bug of the slidingpopups kwin effect. the first time the effect won't work and i don't know how to resolve it
does the PopupApplet set the attributes correctly? WA_TranslucentBackground instead of WA_NoSystemBackground when compositing is enabled?
*** Bug 235695 has been marked as a duplicate of this bug. ***
( (In reply to comment #10) > *** Bug 235695 has been marked as a duplicate of this bug. *** I agree that this is a bug, but it is different from 235695. In the screencast, the background under the pop-up does not slide up, so in terms of appearance it look OK other than the time lag. However, in bug 235695 when the pop-up starts to slide up, the background that is to be covered slides up at the same time up creating a torn background above the pop-up.
The performance of sliding popups effect has been quite improved in recent versions. If you still encounter this issue in 4.8 please reopen and update relevant bug information.