[Hardy] Move To Trash broken with new gnome-vfs

Bug #209338 reported by Nick Lawson
8
Affects Status Importance Assigned to Milestone
baobab (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: baobab

(Hardy Beta patched up to date as of writing this bug)

In the folder/file list, Right-click Move to Trash
Disk Usage Analyzer moves the file to ~/.Trash instead of ~/.local/share/Trash/files, (or just trash:/// ) so nothing shows up in the gnome-vfs trash applet, etc.

Those files moved in that way will essentially sit there until the user manually deletes them out of ~/.Trash, and will not show up in the nautilus trash folder or the trash applet etc.

Revision history for this message
Jörn Schmidt (josc) wrote :

same problem here.
I think bug #208277 could be related to this.

Revision history for this message
Nick Lawson (vektuz-gmail) wrote :

Possibly. I was under the impression that each individual app that used to move things to trash needs to have gnome-vfs support to work properly now (ie, there is no universal fix). I could be wrong.

If it's indeed the case that individual apps needs upgrades, it means bug #208277 would be because of any random app that hasn't got the vfs support yet.

However, the 'symptoms' of this bug are different from whats described there... to be more specific the system-wide trashcan shows up as empty, and opening up the trash can using the trash applet (or vfs link) shows nothing there. (Becuase the files were moved to a different folder which the trash can applet is not watching).

Basically, if the user is not knowlegable enough to know that its moving the files to ~/.trash, it will appear to them as if the files are being erased, but they will gain no disk space. The trashcan itself won't actually show up as full or needing emptying

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

Still the case Jul 8, 2008, Hardy with all updates.

Revision history for this message
Jérémy Subtil (bigmadwolf) wrote :

I can confirm this bug on Aug 28, 2008.

Changed in baobab:
status: New → Confirmed
Revision history for this message
Hew (hew) wrote :

I can't reproduce this on Intrepid (gnome-utils 2.24.1-0ubuntu1). Is this still a problem for others with this version?

Changed in baobab:
status: Confirmed → Incomplete
Revision history for this message
Hew (hew) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in baobab:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.