Bug 457959

Summary: Copying large number of folders (1000+) with many subfolders, when moving bar finish, its like continue some operation but feels like hanging.
Product: [Applications] dolphin Reporter: Ilias Tsolis <elias_0000_0000>
Component: panels: foldersAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kfm-devel, nate
Priority: NOR    
Version: 20.12.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Ilias Tsolis 2022-08-16 14:31:44 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Copying large number of folders (1000+) (to two different HDDs) with many subfolders, when info bar finished of process of movingfolders, its like that some operation occurs but dolphin looks like freezed - you cannot do any operation - only after some minutes (2-3m in my system).

So what such operation is? Cleaning inodes? Tidy up folder information? 
Why info bar of moving folders dont report it? 

STEPS TO REPRODUCE
1. move from HDD sda to HDD sdb large number of folders with subfolders eg. 10000+
2. Wait to show the infobar of movement that process is finished
3. Try to eg. create a new folder... u cant, u must wait 2-3m (depend on the machine power) until some "hidden" operation by dolphin is finished without reporting it to user which may feels distressed. 

OBSERVED RESULT

dolphin is like freezed after info bar report finish move of folders

EXPECTED RESULT
to report hidden operation in order user to know what is happening 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE with bullseye 11
KDE Frameworks 5.80.0
Qt 5.15.2 (built against 5.15.2)
The xcb windowing system

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-08-17 19:41:13 UTC

*** This bug has been marked as a duplicate of bug 416248 ***
Comment 2 Nate Graham 2022-08-17 19:41:30 UTC

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