Bug 167738 - Wastebin plasmoid says "Trash Empty" despite plenty of files inside
Summary: Wastebin plasmoid says "Trash Empty" despite plenty of files inside
Status: RESOLVED DUPLICATE of bug 168733
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-trashcan (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-30 14:32 UTC by David Dempster
Modified: 2008-11-20 07:42 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Dempster 2008-07-30 14:32:16 UTC
Version:            (using KDE 4.1.0)
Installed from:    Ubuntu Packages
OS:                Linux

I have just added the Wastebin plasmoid to my desktop.  

It appears as an empty-looking bin.  It is labelled "Trash", and under that, it says "Empty".  If I click on it, I can see lots of files inside.

Perhaps the thingy that checks whether there are files is looking in the wrong place (e.g. ~/.Trash instead of ~/.local/share/Trash).
Comment 1 David Dempster 2008-07-30 14:33:41 UTC
WTF?  I clicked on "plasmoid" because the Wastebin is a plasmoid, and somehow this got filed under KGet!!
Comment 2 Lukas Appelhans 2008-07-30 14:58:10 UTC
Yes, KGet has a Plasmoid as well. Probably we should rename that Component...

Lukas
Comment 3 David Dempster 2008-07-30 15:09:51 UTC
OK, thanks.

I have new information.

KDE just crashed on me (I'll file a bug if it does it consistently), so I had to restart X and log back in.  The Wastebin then correctly reported the number of deleted files!

So, I did an experiment.  I removed the plasmoid, and then put it back.  It started to misreport the bin as "empty" again.  I logged back in again, and again the reporting of the state of the bin was fixed.

In conclusion, the Wastebin plasmoid fails to correctly report the status of your trash until the subsequent time that you log in.  It seems to do this consistently.

The fact that it fixes itself will probably mean that most people will not report the bug here, but the bug is still very real, and could be quite frustrating at first.
Comment 4 Aaron J. Seigo 2008-07-30 22:56:15 UTC
i can't reproduce this =/

it's using the proper URL (trash:/) and i can't see what would be different between plasma start up and first creation.
Comment 5 David Dempster 2008-07-31 03:06:02 UTC
Really?  I know it's weird, but it's real.

Here are the exact steps to follow:
* Get KDE 4.1.0 (preferably on Kubuntu 8.04.1)
* Create a new user (so there are no left-over configuration files at all)
* Open Dolphin, and delete some files.
* Add the Wastebin plasmoid to the desktop.

I've just tried it again right now.  I found that if I put the plasmoid on first, and then deleted some files, the total was correctly updated.  But if files were already in the bin, and I then added the plasmoid (as described in the above steps), then it continued to claim it was empty.
Comment 6 Fritz Heinrichmeyer 2008-09-06 10:56:58 UTC
with libplasma from 4:4.1.1-0ubuntu1~hardy1~ppa1
under Ubuntu 8.04.1 the situation has not changed.
Comment 7 Fritz Heinrichmeyer 2008-09-06 11:00:06 UTC
forget my last comment, i confused the bug number
Comment 8 Mike FABIAN 2008-09-22 12:21:15 UTC
See also: http://bugzilla.novell.com/show_bug.cgi?id=413629

I can reproduce it like this:

- Move some items into the trash can. The icon of the trashcan
  shows the number of items.
- Add a new trash can with "add widget". The newly created trashcan
  does not show the number of items, instead it shows “empty”.

Comment 9 Marco Martin 2008-09-22 20:02:55 UTC
probably is the lack of filesystem alteration monitoring support, kde compiled without fam support or something like that
Comment 10 Mike FABIAN 2008-09-22 20:14:49 UTC
Then why does the first trashcan work correctly?
Comment 11 Paweł Prażak 2008-09-23 17:02:22 UTC
I can confirm this bug for Kubuntu KDE versions 4.1.0/4.1.1 and I can't confirm it for SuSE 11 KDE 4.1.1/4.1.67 
Comment 12 Aaron J. Seigo 2008-11-20 07:42:51 UTC

*** This bug has been marked as a duplicate of bug 168733 ***