Bug 164634

Summary: Weird Behavior on opening an app (taskbar + cursor)
Product: [Plasma] plasma4 Reporter: Bassio <ahmedbassi>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: alex.merry
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Bassio 2008-06-22 01:31:08 UTC 
Version:            (using KDE 4.0.5)
Installed from:    Ubuntu Packages
OS:                Linux

Using kde 4.0.5

It appears that when I open some CPU-intensive app that needs some time to open .. like the package manager for example, there is a strange behavior 

1) a jumping icon of the app continues jumping on the cursor although the app apparently finished execution 

2) A double entry of the app in the taskbar .. it takes time for the second "duplicate" entry to clear
Comment 1 Alex Merry 2008-08-07 19:47:35 UTC 
Do you still get this in 4.1?
Comment 2 Bassio 2008-08-07 22:40:48 UTC 
Yes.

But I found out the root of the problem.

Only happens with KDE 3 apps when run in KDE 4. That is why it happens with the kubuntu's package manager.

It seems that KDE 3 apps loading and rendering in KDE 4 is somewhat clumsy (maybe the distro's fault .. not sure), and when an intensive KDE3 app opens (or closes) for that matter its entry in the taskbar is still there.

Since the problem does not appear in 4.1 except with kde3 apps as expected then I won't put too much emphasis on this issue. Devs can review/confirm/deconfirm and close this bug accordingly. :)
Comment 3 Alex Merry 2008-08-08 17:57:26 UTC 
I can't reproduce this (tried with k3b and konversation kde3 applications on a kde 4.1.0 desktop).

It sounds like a startup notification issue with the kde 3 applications.  The application isn't telling plasma that it has loaded.

It is possibly a packaging or environment issue with Kubuntu.
Comment 4 Alex Merry 2008-08-21 23:52:47 UTC 
I'm going to close this, since it's almost certainly a Kubuntu or local setup issue.

You might want to try reporting it to Kubuntu.