I have noticed recently (month?) that moving files to trash using Plasma programs is extremely slow - about a second per file, regardless of size. Using Dolphin or Gwenview. Almost no disk access, as expected (it just change pointers not move data) But still using one CPU core 100%. In Plasma, using system monitor, I see it is the process trash.so, started by kdeinit. Also when using Gwenview when logged into Xfce, and I see it is the same process. Logged into Xfce, using its file manager moving files to trash is swift.
Also tried Thunar file manager when logged into Plasma: no problem. Tried uninstalling nextcloud-client packages, including Dolphin integration, no change. (I was thinking maybe some signalling interfered, and it also syncs with a painful fraction of second delays between files) Seen in journal when deleting a small file using Dolphin: nov 25 12:04:09 svarten.tribun plasmashell[3541803]: org.kde.plasma.notifications: Failed to generate job text for job with following properties: nov 25 12:04:09 svarten.tribun plasmashell[3541803]: org.kde.plasma.notifications: processedFiles = 0 , totalFiles = 1 , current file name = "" , destination url string = "Papperskorg" nov 25 12:04:09 svarten.tribun plasmashell[3541803]: org.kde.plasma.notifications: label1 = "" , value1 = "" , label2 = "" , value2 = "" nov 25 12:04:13 svarten.tribun plasmashell[3541803]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" nov 25 12:04:13 svarten.tribun plasmashell[3541803]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" - but the popup about moving to trash is popping up, and getting updated by number of files moved.
I wonder if this could be due to akonadi. I disable it on my day to day use install and don't use any applications that require it such as kmail. To disable it, edit ~/.config/akonadi/akonadiserverrc and change it to have StartServer=false
CC: (none) => davidwhodgins
Thank you for the idea, but sorry, no. 1. Verified akonadi processes was present 2. Edited akonadiserverrc 3. Logged out and in 4. Verified no akonadi* process running 5. Deleted files - same behaviour.