Bug 400025 - Moving thousands of files freezes whole PlasmaShell, operation progress notification does not appear
Summary: Moving thousands of files freezes whole PlasmaShell, operation progress notif...
Status: RESOLVED DUPLICATE of bug 358231
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.14.1
Platform: Neon Linux
: NOR major
Target Milestone: 1.0
Assignee: David Edmundson
Depends on:
Reported: 2018-10-19 12:49 UTC by Mahendra Tallur
Modified: 2018-10-19 13:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Mahendra Tallur 2018-10-19 12:49:00 UTC

Moving thousand of files with Dolphin freezes Plasma Shell

1. in any directory, create 10 000 files (with a simple "for i in {1..10000}; do touch $i; done"
2. open this directory in Dolphin
3. create a subdirectory
4. cut / paste 5 000 of those 10 000 files into this subdirectory


The whole Plasma Shell freeze indefinitely. I have to kill & restart the plasmashell process.

The usual "(i)" appearing in the system tray / widget when a file operation is performed to indicate its completion level does not appear.


The usual file operation notification should appear while the copy is being performed.

Plasma should not freeze

Another side effect is that you don't know when the operation is really over.

(available in About System)
KDE Plasma Version: 5.14.1
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.1

Baloo enabled (for file search not actual content indexing).


Might be related to https://bugs.kde.org/show_bug.cgi?id=358231
Comment 1 Mahendra Tallur 2018-10-19 12:55:09 UTC
Just in case : I confirm it also occurs when Baloo is disabled.
Comment 2 Mahendra Tallur 2018-10-19 13:01:42 UTC
One more remark : the desktop remains frozen long after the actual operation completion. Sorry for the numerous posts.
Comment 3 Nate Graham 2018-10-19 13:23:43 UTC
Yep, the same issue as Bug 358231.

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