Version: (using KDE 4.4.1) OS: Linux Installed from: Fedora RPMs Running FC12 2.6.31.12-174.2.22.fc12.i686.PAE with both Gnome and KDE installed. Active = Gnome. Trying to delete image (del button or right click) but error message reports "trash has reached its maximum size - clear it manually" - Trash cleared of about 1600 files but no change in error message. Close and restart Digikam - no change. Unable to delete images.
Which digiKam release you use ? Gilles Caulier
Trash is handled by KIO
(In reply to comment #1) > Which digiKam release you use ? > > Gilles Caulier Version: 1.1.0 build date: 10th Feb 2010 Mike
Hope this helps: In Arch Linux, on KDE 4.4.3 (package v2), I went to Trash in Dolphin, selected all and clicked delete then OK, and then tried to delete an image, and got the message from Dolphin that the thrash was full and I had to manually empty it. ~/.local/share/Trash had no files (but an empty directory called "expunge" wot I haven't seen before), but the metadata said [Cached] Size=[really huge number] I exchanged it for a 10193617062 (copied from another profile) and then I could delete stuff again.
(In reply to comment #4) > Hope this helps: > > In Arch Linux, on KDE 4.4.3 (package v2), I went to Trash in Dolphin, selected > all and clicked delete then OK, and then tried to delete an image, and got the > message from Dolphin that the thrash was full and I had to manually empty it. > > ~/.local/share/Trash had no files (but an empty directory called "expunge" wot > I haven't seen before), but the metadata said > > [Cached] > Size=[really huge number] > > I exchanged it for a 10193617062 (copied from another profile) and then I could > delete stuff again. ============= Based on Kevin's comment I edited the cached size to a random 123456789; This allows deleting in images from Digikam.
Same problem here. Fedora 12, KDE 4.5.0. No DigiKam or Gnome installed. Everytime I want do delete a file: "trash has reached its maximum size - clear it manually" - trash is empty!
*** This bug has been marked as a duplicate of bug 245482 ***