Comment 27 for bug 880533

I've been looking into this a bit.

As some have observed, it happens when the gvfsd-trash daemon has not spawned and thunar accesses the trash for the first time (yet causing it to spawn). So for the trash bin having the correct state it is necessary that the daemon has already spawned when reading the info. The gvfs-trash ls command or any other application accessing the gvfs trash does this.

To reproduce this more easily, simply kill thunar and gvfsd-trash and start a new instance of thunar (daemon or window shouldn't matter).

The code added to thunar-session-client.c could work, but it never gets called on my machine, presumably because I do not start thunar with the session manager. If that is true, all people with a similar setup will suffer from this too. Also the thunar trash panel plugin could exhibit the same problem.