Bug 408348 - Bouncing cursor keeps running
Summary: Bouncing cursor keeps running
Status: RESOLVED DUPLICATE of bug 408571
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-05 13:53 UTC by J.Novo
Modified: 2019-06-11 17:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description J.Novo 2019-06-05 13:53:16 UTC 
SUMMARY
In dolphin, with the open in tab changes, when i open a folder the busy cursor keeps running after the folder is open.


OBSERVED RESULT
The busy cursor shows till it times out.


EXPECTED RESULT
Busy cursor should stop when the location is open.


SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.0
Kernel Version: 4.18.0-21-generic
OS Type: 64-bit

ADDITIONAL INFORMATION

Dolphin
Version 19.07.70
Comment 1 Nate Graham 2019-06-10 22:24:52 UTC 
Cannot reproduce, but it's a bit hard to tell what's going on from the description. Do you think you could attach a screen recording that shows the problem? Thanks!
Comment 2 J.Novo 2019-06-11 08:27:18 UTC 
Sorry, i didnt explain it well.

Go to settings and set the application launch feedback to bouncing and set stop animation after 20 seconds.

After that when you open an application the cursor bounces before the application is ready and stops when it is ready (or at least is what i understand); it does not bounce for the 20 seconds but just the time it takes the application to be ready.

With the latest changes made to dolphin when i open a folder that opens in a new tab the cursor keeps bouncing till it times out, in this case for 20 seconds, even if the folder takes less time to open.
Comment 3 Nate Graham 2019-06-11 17:10:33 UTC 
Thanks!

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