[Bug 685223] New: Thunar will not allow emptying trash after deleting files from USB, Space for deleted files is unrecoverable from GUI.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c0 Summary: Thunar will not allow emptying trash after deleting files from USB, Space for deleted files is unrecoverable from GUI. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce@forge.provo.novell.com ReportedBy: dac1138@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 When plugging in a USB thumb drive and deleting files, Thunar does not provide me with an option to empty the trash. Thunar looks as if the files are deleted, but it doesn't show the space taken up by the files added back to the total amount of empty storage. If I browse to the USB drive using the command line, I can navigate to the .Trash folder and see the files/folders that I had just deleted and I can delete them this way. Thunar 1.3.0 OpenSuSE 11.4 with the latest updates as of 4/5/2011 Reproducible: Always Steps to Reproduce: 1. Insert USB thumb drive with files ready to be deleted 2. Select and delete files 3. Take note that there's no ability to empty the trash. 4. (optional) Using the command line, navigate to /media/Path-to-USB/.Trash and do "ls". You'll see the files that were deleted in step 2. Actual Results: After the steps above were performed to delete the files using Thunar, the disk space was unrecoverable. If I navigated and removed the files using the command line, everything worked fine and the space was useable again. Expected Results: Deleting files using Thunar should allow you to either permanently remove files without adding them to the trash, or move them to the trash with the ability to recover or permanently remove. Either way, when permanently removing files the space should be recovered and be useable again without having to go through the command line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c1 Guido Berhörster <gber@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gber@opensuse.org Component|Xfce |GNOME AssignedTo|bnc-team-xfce@forge.provo.n |bnc-team-gnome@forge.provo. |ovell.com |novell.com Severity|Minor |Normal --- Comment #1 from Guido Berhörster <gber@opensuse.org> 2011-04-17 16:13:53 UTC --- This is not specific to Thunar, I can e.g. reproduce the same with Nautilus, the problem seems to lie with gvfs here. gvfs does not seem to show files which are in the trash on external media, this can e.g. be confirmed by "gvfs-ls trash://", I'm thus reassigning this to GNOME. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c Andre Klapper <a9016009@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a9016009@gmx.de See Also| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=662946 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c2 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Dominique Leuenberger <dimstar@opensuse.org> 2013-11-23 20:02:51 UTC --- Dear Reporter, Thank you for taking the time to report this bug and helping to make openSUSE better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in openSUSE since the time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a current, supported openSUSE version. When you test it and it is still an issue, kindly reopen this bug and move it to the tested version of openSUSE. Truly yours. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c3 --- Comment #3 from Andre Klapper <a9016009@gmx.de> 2013-11-24 01:11:50 UTC --- dimstar: You closed this as RESOLVED FIXED. https://bugzilla.novell.com/page.cgi?id=fields.html defines FIXED as "A fix for this bug is checked into the tree and tested." There is no indication that anything has been fixed except for a vague optimistic assumption based on the fact that time passes by. Do you really think that "RESOLVED FIXED" is appropriate in this case and would not pollute queries for reports that actually do have an identifiable code commit? Because it feels utterly wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=685223 https://bugzilla.novell.com/show_bug.cgi?id=685223#c4 Andre Klapper <a9016009@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #4 from Andre Klapper <a9016009@gmx.de> 2013-12-11 18:08:30 UTC --- Reopening due to obviously wrong action in comment 2, as explained in comment 3. Or change the documentation to cover your actions... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com