Dolphin's Trash showing folders and cannot delete; ~/.local/share/Trash subdirectories are empty

Help
1

DolphinTrashIssue
DolphinTrashIssue1920×1080 156 KB

The above shows the issue.
Steps I have taken to try and resolve listed below - TiA for any suggestions as to how to resolve.

  1. sudo apt-get -y autoremove --purge dolphin

  2. sudo apt update
    sudo apt-get install dolphin

  3. Used Timeshift to go back a month and recover and then ran sudo apt update and upgrade to catch back up, issue still remains.

  4. Manually deleted the configuration files located at ~/.config/dolphinrc and ~/.local/share/dolphin to force a fresh setup, issue still remains.

System config overview:

OS Debian GNU/Linux 13 (trixie) x86_64
Kernel Linux 6.12.74+deb13+1-amd64
Packages 3420 (dpkg), 26 (flatpak), 1 (snap)
Shell bash 5.2.37

DE KDE Plasma 6.3.6
Window Manager KWin (X11)
Login Manager sddm 0.21.0 (X11)
WM Theme Breeze
Color Themes Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
System Icons breeze-dark [Qt], breeze-dark [GTK2/3/4]
System Fonts Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Terminal konsole 25.4.2

PC XPS 8940
Board 0K3CM7 (A00)
CPU 11th Gen Intel(R) Core™ i7-11700 (16) @ 4.90 GHz - 45.0°C
RAM 7.23 GiB / 31.00 GiB (23%)
GPU NVIDIA GeForce RTX 3060 Ti - 58.0°C [Discrete]
GPU Intel UHD Graphics 750 @ 1.30 GHz [Integrated]
OpenGL 4.6.0 NVIDIA 550.163.01
Vulkan 1.4.305 - NVIDIA [550.163.01]Intel open-source Mesa driver [Mesa 25.0.7-2]
Display(s) 1920x1080 @ 60 Hz in 25" [External]

3

These files do not reside in ~/.local/share/Trash as indicated by the error message. The files are on another partition and the path to these files is explicitely given in the error message. You may try to use the correct path to delte the files using the terminal, for the case that fails you’ll get most probably a more informativ error message,e.g. the reason why it failed. Probably running a file-system check on that partition might be helpfull.

4

Those folders do not exist in the path, as the error message indicates. I umounted the drive and then ran fsck on it. The exit code was 0 so there is nothing wrong with the drive.

This appears to be some kind of bug in KDE.