Re: Trash Problems

["Nickolay V. Shmyrev" <nshmyrev yandex ru>]

В Чтв, 11/05/2006 в 17:19 +0200, Luca Ferretti пишет:
> Il giorno gio, 11/05/2006 alle 09.29 -0500, Travis Watkins ha scritto:
> > On 5/11/06, David M. Carney <carney1979 gmail com> wrote:
> > > Travis,
> > >
> > > Thanks for your reply.
> > >
> > > Perhaps I'm using the wrong list??
> > >
> > > My trash applet on my panel thinks my trash is on my USB stick. Nautilus
> > > does use ~/.Trash. My mistake.
> > >
> > > Got any ideas how to make my trash applet use ~/.Trash instead of my USB
> > > stick?
> > >
> > > David
> > >
> 
> > Moving back to list. I don't know, sorry.
> 
> Try to remove your  ~/.Trash directory, it will be recreated, mayby
> fixing some weird permissions (BTW versions??)
> 
> PS:
> 
> 1) When you "move to trash" a file or a folder inside your home
> directory with Nautilus, the file or the folder is moved to ~/.Thrash
> hidden directory (by GnomeVfs)
> 
> 2) When you "move to trash" a file or a foldler on a removable device
> (suck as USB stick) with Nautilus, the file or the folder is moved the
> a .Trash hidden directory in the toplevel directory of removable volume
> (i.e. on /media/usbdisk/.Trash/) (by GnomeVfs)
> 
> 3) When you open or look the trash:// location with Nautilus, you will
> see files in ~/.Trash directory and in all .Trash directories on mounted
> removable devices (by GnomeVfs)
> 
> 4) When you unmount removable devices, the trash:// contents is
> collected only by ~/.Trash content (by GnomeVfs)
> 
> 4) The only interaction of trashapplet with trash in on its tooltip and
> honestry it seems to me [1] that it's using only ~/.Trash
> 
> 
> PPS this is developers list ;-)

Yeah, and this is the development problem.

Mostly this behavior exists due to the bug in gnome-vfs - it's
impossible to xfer files between filysystems. So it's impossible to move
files to trash in home directory. See

http://bugzilla.gnome.org/show_bug.cgi?id=309592


Since people that are responsible for that bug are here, let me ask once
again:

Please review the patch attached to the bug while we are in the early
stage of release cycle, otherwise it will be postponed to the next year
once again. Of course, it will be pain to remove all existing
workarounds also, but at least new programs will be more consistent.