https://bugs.kde.org/show_bug.cgi?id=452074

            Bug ID: 452074
           Summary: Deleting files to trash with kio very slow | rm works
                    correctly
           Product: frameworks-kio
           Version: 5.92.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Trash
          Assignee: fa...@kde.org
          Reporter: 88zo26...@mozmail.com
                CC: kdelibs-b...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Create an empty file named test.txt on the Desktop or wherever
2. Try to delete it either via GUI or using kioclient5 move "the_filename.txt"
trash:/

OBSERVED RESULT
1. Screenshot 1 shows and 1-3 minutes pass while waiting for something to
happen
2. Screenshot 2 happens - 5 seconds up to 1 minute pass waiting for progress
3. File is deleted

This happens also with VS Code which seems to use kioclient on KDE for deleting
files, only without the notification showing but instead the VS Code own
progress bar showing.

EXPECTED RESULT
Immediate deletion of file, just as rm does

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.16.16-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFO
I was chatting on the KDE Chat with someone about this and when I launched with
the appropriate env variables to produce log it appeared stuck at some Qt
function and we said that it is possible to be a Btrfs issue. Chatted with
Btrfs and they said they fixed some such bug but after updating the Linux
kernel bug stays. Before opening an official issue with Btrfs I want to get
official statement from KDE that it's not a kioclient bug. I don't want to send
Btrfs devs to chase Unicorns.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to