If one trashes a file it may be impossible to delete it from the trash later. Apparently that happens when the user does not own the original path of the file. The specification suggests to warn the user that he will not be able to delete the file, but actually it is trashed. The only workaround is to remove the file manually from ~/.local/share/Trash with root access.
The bug still persists. Could you please look into it?
If this bug still exists with GIO, it should probably be forwarded to the GVfs maintainers.
Yes, I can still reproduce. You can reproduce like this: 1. Pick any source code folder 2. Have configure/ make/ waf already built once. 3. Edit a .c or .vala source file that will trigger a rebuild. 4. Do ‘sudo make install’ or ‘sudo ./waf install’. 5. Object files will be updated as root. 6. Delete the files with Thunar. 7. Try to empty the wastebin.
Close bug reports of archived products.