After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 765650 - Trash folders get created in subfolders but aren't added to "trash:/"
Trash folders get created in subfolders but aren't added to "trash:/"
Status: RESOLVED DUPLICATE of bug 747540
Product: nautilus
Classification: Core
Component: Trash
3.20.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-27 04:29 UTC by piedro.kulman
Modified: 2017-03-31 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20



Description piedro.kulman 2016-04-27 04:29:03 UTC
When deleting files in some folders within my home partition, all owned by me (with correct permissions, I guess) the tarsh folders ".Trash-1000" get created though theses are not external drives (nor mounted partitions)... 

While this is annoying it should still be fine when all these trashbins get collected in the nautilus trash bin. 

Opening "trash:/" should at least collect all the owners ".Tash-1000" trashbins and offer the option to delete them. 

But the common trash bin doesn't collect these trash bins at all. Deleted files do not show up within the nautilus window for the virtual folder "trash". Deleting leaves all the files in the "Trash-1000" in place... so there is no way of deleting them either than opening each one individually and removing the files within. 

I do not see how to fix this, I couldn't find any configuration files or configuration options for the trash bin, so I have no idea where to look or even how to start trouble shooting. 

thx for reading, 
piedro
Comment 1 Carlos Soriano 2016-09-27 15:07:39 UTC
That is really strange. What kind of filesystem are you using? What operating system and version?
Comment 2 Carlos Soriano 2016-09-30 09:30:51 UTC
I believe it's duplicated of this bug

*** This bug has been marked as a duplicate of bug 747540 ***