[dolphin] [Bug 457959] New: Copying large number of folders (1000+) with many subfolders, when moving bar finish, its like continue some operation but feels like hanging.
Ilias Tsolis
bugzilla_noreply at kde.org
Tue Aug 16 15:31:44 BST 2022
https://bugs.kde.org/show_bug.cgi?id=457959
Bug ID: 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: dolphin
Version: 20.12.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: panels: folders
Assignee: dolphin-bugs-null at kde.org
Reporter: elias_0000_0000 at yahoo.com
CC: kfm-devel at kde.org
Target Milestone: ---
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
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list