Bug 275616

Summary: Resuming Desktop Effects while Startup Feedback is visible leaves it there forever
Product: [Plasma] kwin Reporter: Kai Uwe Broulik <KaiUweBroulik2>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: kde, kdebugs, summerspam, zzyxpaw
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kai Uwe Broulik 2011-06-14 08:14:29 UTC 
Version:           unspecified (using KDE 4.6.4) 
OS:                Linux

When launching an application (especially applications that don’t resign the startup feedback aka bouncing cursor) and then resuming desktop effects while the bouncing cursor is visible leaves it at your mouse pointer forever. You can only remove it by temporarily disabling that thing in systemsettings → notifications. When another application starts, you will get two independent bounce things. Startup Helper Effect enabled.

Reproducible: Always
Comment 1 Martin Flöser 2011-06-26 09:28:20 UTC 
makes sense
Comment 2 Martin Flöser 2011-07-30 19:49:24 UTC 
*** Bug 278883 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Lübking 2014-01-14 01:26:09 UTC 
*** Bug 329906 has been marked as a duplicate of this bug. ***
Comment 4 Thomas Lübking 2014-01-14 16:11:09 UTC 
Gave it a try. I do not think, this is a bug in the effect.

The original bouncing stuff is not exited, ie. you got two bouncers: the original bouncing window as well as the bouncing icon in the compositor - latter ends as expected, but the original one apparently does not notice that it lost selection and goes on forever. ("proof": suspend compositing, icon continues to bounce)

It's not requred to re-login,  run "kcmshell4 launch" and disable feedback stops the boucing and re-enabling bouncing will not continue it.

Now we need to figure what usually controls this thing.
Comment 5 Vlad Zahorodnii 2018-10-06 21:35:34 UTC 
@Martin
Is this still the case? I can't reproduce the bug.
Comment 6 Martin Flöser 2018-10-07 08:57:22 UTC 
This must be fixed. The problem was caused by us having two places with the startup feedback functionality (one for compositing, one for no compositing). Nowadays we only have the composited startup feedback, thus the problem must be resolved.