Bug 334911

Summary: Tooltip fade animations flicker
Product: [Plasma] kwin Reporter: Sebastian Kügler <sebas>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: rynunes
Priority: NOR    
Version: git master   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sebastian Kügler 2014-05-16 23:01:17 UTC 
When tooltips are fading in and out, the animation flickers and isn't smooth.

This seems to happen for all the tooltips. It is most visible in systemsettings' default overview tooltips. Hovering and unhovering an item doesn't show a smoothly blending animation, but a flickering between shown and hidden for the time the animation runs. This leads to a jarring user experience.

My naive interpretation is that either or both of the following might be wrong:

- Some effect doesn't correctly identify the item as tooltip and animates them while it shouldn't
- Another effect gets in the way, and manipulates the opacity as well, one or the other wins, more or less randomly for every frame -> opacity jumps up and down, it flickers.

Reproducible: Always

Steps to Reproduce:
1. Open systemsettings
2. Hover mouse over an item
3. Wait for tooltip to show, move away or to another item
Actual Results:  
Tooltips shows a flickery animation while appearing

Expected Results:  
Tooltip smoothly fades in and out
Comment 1 Martin Flöser 2014-05-17 07:01:08 UTC 
the problem is "Save intermediate rendering results" in the blur effect. I'm quite sure we already have a bug report for this problem.
Comment 2 noons 2014-06-24 00:21:19 UTC 
(In reply to comment #1)
> the problem is "Save intermediate rendering results" in the blur effect. I'm
> quite sure we already have a bug report for this problem.

Yes, appears to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=307112

I can confirm disabling the blur effect resolves this issue.
Comment 3 Martin Flöser 2014-06-24 05:57:46 UTC 

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