when I delete a file it takes long time to move to trash KDE. It doesn’t matter if it’s small file, big file or multiple files. I tried disabling 10% quota. I have 128 gb ssd.
But directly deleting is quicker (shift+del).
Any solution?
What’s the output of
df -h
this is my df -h.
❯ df -h
df: /tmp/.mount_appimaDy5rcl: Transport endpoint is not connected
df: /tmp/.mount_appimaUOQOZN: Transport endpoint is not connected
df: /tmp/.mount_appima0INarT: Transport endpoint is not connected
df: /tmp/.mount_appimaYijzD1: Transport endpoint is not connected
df: /tmp/.mount_appimapnAOCg: Transport endpoint is not connected
df: /tmp/.mount_appimaIW2kes: Transport endpoint is not connected
df: /tmp/.mount_appimaHalfgS: Transport endpoint is not connected
df: /tmp/.mount_appima7XtSKW: Transport endpoint is not connected
df: /tmp/.mount_appimazsmwI0: Transport endpoint is not connected
df: /tmp/.mount_appimaIlHBTq: Transport endpoint is not connected
df: /tmp/.mount_appimawF3Cfz: Transport endpoint is not connected
df: /tmp/.mount_appimaJiJEgd: Transport endpoint is not connected
df: /tmp/.mount_appimaxPXIZr: Transport endpoint is not connected
df: /tmp/.mount_appimaamfru5: Transport endpoint is not connected
df: /tmp/.mount_appimaDVZxeG: Transport endpoint is not connected
df: /tmp/.mount_appimav6zN2o: Transport endpoint is not connected
df: /tmp/.mount_appimaHmRMvP: Transport endpoint is not connected
df: /tmp/.mount_appimaMid5cI: Transport endpoint is not connected
df: /tmp/.mount_appimao58FK8: Transport endpoint is not connected
df: /tmp/.mount_appimaHbBiDX: Transport endpoint is not connected
df: /tmp/.mount_appimacDITQr: Transport endpoint is not connected
df: /tmp/.mount_appimaVgaQYl: Transport endpoint is not connected
df: /tmp/.mount_appimak30yBo: Transport endpoint is not connected
df: /tmp/.mount_appima67PH7b: Transport endpoint is not connected
df: /tmp/.mount_appimaDAR1Fu: Transport endpoint is not connected
df: /tmp/.mount_appimaNyBwsV: Transport endpoint is not connected
df: /tmp/.mount_appimaF2Eez9: Transport endpoint is not connected
df: /tmp/.mount_appimaKCYjV9: Transport endpoint is not connected
df: /tmp/.mount_appimaOxvSGI: Transport endpoint is not connected
df: /tmp/.mount_appima8NA2nm: Transport endpoint is not connected
df: /tmp/.mount_appimahU4V2d: Transport endpoint is not connected
df: /tmp/.mount_appima1fsx6X: Transport endpoint is not connected
df: /tmp/.mount_appimaAMcIvS: Transport endpoint is not connected
df: /tmp/.mount_appimauRZLFt: Transport endpoint is not connected
df: /tmp/.mount_appimaY8JKZv: Transport endpoint is not connected
df: /tmp/.mount_appimauzoJq0: Transport endpoint is not connected
df: /tmp/.mount_appimaWaF8JB: Transport endpoint is not connected
df: /tmp/.mount_appimajphyk0: Transport endpoint is not connected
df: /tmp/.mount_appima4sZV8j: Transport endpoint is not connected
df: /tmp/.mount_appimazzA3Wo: Transport endpoint is not connected
df: /tmp/.mount_appimatBklN0: Transport endpoint is not connected
df: /tmp/.mount_appimaNYKsE5: Transport endpoint is not connected
df: /tmp/.mount_appimaA496Dt: Transport endpoint is not connected
df: /tmp/.mount_appimamhB9gY: Transport endpoint is not connected
df: /tmp/.mount_appima1PSvN0: Transport endpoint is not connected
df: /tmp/.mount_appimagszsw2: Transport endpoint is not connected
df: /tmp/.mount_appimaqIy1Ge: Transport endpoint is not connected
df: /tmp/.mount_appimaiDePpU: Transport endpoint is not connected
df: /tmp/.mount_appimaoiD9La: Transport endpoint is not connected
df: /tmp/.mount_appimaChTVpt: Transport endpoint is not connected
df: /tmp/.mount_appimahW2t9w: Transport endpoint is not connected
df: /tmp/.mount_appimajeCzW2: Transport endpoint is not connected
df: /tmp/.mount_appimaYcL2Ya: Transport endpoint is not connected
df: /tmp/.mount_appimaShZUCE: Transport endpoint is not connected
df: /tmp/.mount_appimaH2EMNN: Transport endpoint is not connected
df: /tmp/.mount_appimajXtYYS: Transport endpoint is not connected
df: /tmp/.mount_appimaIpmBCy: Transport endpoint is not connected
df: /tmp/.mount_appimaCOWtPK: Transport endpoint is not connected
df: /tmp/.mount_appimaJSTbnL: Transport endpoint is not connected
df: /tmp/.mount_appimajwRjg6: Transport endpoint is not connected
df: /tmp/.mount_appimaMtWoSz: Transport endpoint is not connected
df: /tmp/.mount_appimaiXFSkn: Transport endpoint is not connected
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 1.6G 9.5M 1.6G 1% /run
/dev/sda3 111G 20G 90G 18% /sysroot
tmpfs 3.9G 12K 3.9G 1% /tmp
/dev/sda3 111G 20G 90G 18% /var
/dev/sda2 974M 194M 713M 22% /boot
/dev/sda1 511M 12M 500M 3% /boot/efi
/dev/sdb1 932G 464G 468G 50% /var/home
tmpfs 781M 180K 781M 1% /run/user/1000
/dev/sdc1 932G 221G 711G 24% /run/media/badshah/My Passport
When did you last reboot? I ask because /tmp is a virtual file system in RAM and when one cold boots or restarts that file system should initially be totally empty except for what is created at boot time.
I reboot everyday.
My home partition is on HDD. Could that be the reason? Because on other desktop it deletes instantly
Normally a delete within nautilus that moves items to the trash is rapid since it simply links that file into the trash folder instead of an actual delete. It may be a tiny bit longer on an HDD than on an SSD but not nearly as long as you indicate.
Whatever is leaving those /tmp/.mount_appimaXXXXXX links was my concern and triggered that question. On my system I see nothing like that and never have. The name seems to indicate it may be from an appimage that has been run and either crashed or shutdown without a proper cleanup.
I think it’s from appimage launcher that I have installed. Could that be any reason for trash becoming slow?
Also I see many people also have this problem on internet.
Cannot answer the question about appimage laucher being the cause of the slowdown since I have never tried it. I can say that the command used (df) obviously tried to read those devices as it certainly saw them as block devices and failed to connect.
An easy way to check would be to uninstall the launcher then reboot and see if the situation shows any change
1 Like
Uninstalled appimage-launcher. Issue still exist unfortunately.
❯ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 1.6G 9.5M 1.6G 1% /run
/dev/sda3 111G 20G 90G 18% /sysroot
tmpfs 3.9G 12K 3.9G 1% /tmp
/dev/sda3 111G 20G 90G 18% /var
/dev/sda2 974M 194M 713M 22% /boot
/dev/sda1 511M 12M 500M 3% /boot/efi
/dev/sdb1 932G 464G 469G 50% /var/home
tmpfs 781M 188K 781M 1% /run/user/1000
revokefs-fuse 111G 20G 90G 18% /var/tmp/flatpak-cache-XROD81/com.microsoft.Edge-FWOD81
I do not see the root file system / in that listing from df. It apparently was incomplete or there may be a problem with the file system. I also see /sysroot which does not exist on my system. Are you by chance running kinoite? (which could explain the differences in the file system structure)
Please also show lsblk -f and uname -a
/sysroot usually is where the root file system is mounted while running in the initrd envronment. Then /sysroot and / are swapped and you are now running using the real root. In this case, something non-standard seems to be happening.
Strange also is that /dev/sda3 occurs twice, and /var/home is also a bit strange.
I thought that might be the case, but I question as well the revokefs-fuse listing. /dev/sda3 shows a size of 111G with both entries then the revokefs-fuse line shows the same size and usage numbers. Really strange as if it erred in the initrd stage and continued to user space without switching root.
Right. I am running Fedora kinoite 38.
One thing I found out. During the file deletion loading. If I close Dolphin. File deletion completes instantly. I don’t know why
There were still some file left in ~/.local/share/Trash/. Emptying the trash don’t remove those files. I don’t know the reason why those files were stuck. So, I did hard delete.
rm -rf ~/.local/share/Trash/
Which remove all those files stuck in Trash folder. And now file moves to Trash instantly.