can't move files to trash without any owner/permission issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Unknown
|
High
|
|||
nautilus (Ubuntu) |
Low
|
Unassigned |
Bug Description
This is something that wouldn't happen before upgrading from Ubuntu 14.10 / Nautilus 3.10 to Ubuntu 15.04 / Nautilus 3.14:
I have a proper HOME partition and most User folders there (Documents, Downloads, Music, Pictures, Videos) are merely SYMLINKS to folders with the same names in a DATA partition which is mounted automatically at startup with proper options in fstab.
Now -- unlike before -- when I attempt to delete an item in one of these folders after I open it via the SYMLINK I get the message "... can't be put in the trash. Do you want to delete it immediately?" although it is immediately moved to the Trash after I open the folder via the Data partition in the sidebar. (Naturally there are no such problems with items in other (real) items in my Home folder.
Nautilus now seems confused about / not knowing where to move the item in question; to the Trash folder in the Home partition (symlink location) or the Data partition (real item location).
Sadi Yumuşak (sa-yu) wrote : | #2 |
FYI I've made a bug report, which is here:
Changed in nautilus: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in nautilus: | |
status: | Confirmed → Unknown |
Emmanuel (emmanuelturinetto) wrote : | #4 |
Happens the same to me. I have two symlinks to two specific folders on my NTFS partition, that has all my personal files and data (Dual-Boot PC). When I access to this folders via Home Folder using symlink folder and try to delete some file that is inside this, the next message appears "... can't be put in the trash. Do you want to delete it immediately?". Not happening the same when I acces via Data partition to the folder.
By the way, I had observed that this weird behavior only appears to happens on the symlinked folder, and not on the folders that can be contained inside of it.
If, after accessing via Home Folder to you symlinked folder, you create any new file and a new folder, put this file on the folder, and try to delete this last one, no problem occurs. But if you try the same with any file inside symlinked folder, the message appears. I do not know how to explain it well, but what I try to said is that there is no problem at all in folders contained (and the files this folders contain) inside symlinked folder. The problem is with files contained inside symlinked folder.
IE: if my symlink folder is /media/
Hope this help to someone to fix this.
Sadi Yumuşak (sa-yu) wrote : | #5 |
Emmanuel,
1) You should better go to the bug report mentioned above: https:/
2) Your case might be due to a different Nautilus version (or maybe some sort of custom configuration). I understand the root of this problem is Nautilus has this problem when it "mistakenly" regards (tries to treat) an item in that other partition like it is in the Home partition. For example the Location Bar in that case shows: HOME | Documents | ...
In a case where no such problem occurs (for instance I've modified the entries in "~/.config/
Rob T Firefly (7-rob) wrote : | #6 |
Confirmed, this happens to me on a fresh install of 15.04 where the Documents/
Sadi Yumuşak (sa-yu) wrote : | #7 |
This annoying problem has been finally solved for me; THANKS A MILLION TO CzBix :-)
Duplicate bug reported by CzBix: https:/
Patch kindly offered by CzBix to fix it: https:/
I hope the developers up there incorporate this soon.
petersaints (petersaints) wrote : | #8 |
This still happens on 16.04. Any progress on fixing it?
Matthew Gregg (mcg) wrote : | #9 |
Wow. I was hoping this would be fixed in 16.04. Still can't use the trash on mounted/linked partitions/drives.
Sadi Yumuşak (sa-yu) wrote : | #10 |
Interestingly, after upgrading to 16.04;
I can now move files to Trash any where and any way EXCEPT ONLY the 1st level of a directory symlinked in my Home folder!!!
✔ /home/$
✘ /home/$
✔ /home/$
✔ /media/
✔ /media/
✔ /media/
My new Nautilus is smarter than before, and puts items deleted under sub-directories of "/home/
CzBiX (gliuwr) wrote : | #11 |
Just updated my binary patch for Ubuntu 16.04.
https:/
Sadi Yumuşak (sa-yu) wrote : | #12 |
@CzBix Thanks again! It works like magic : -)
./patch_
nautilus -q
Voila!
I just wonder why the package developers cannot do this and save you and all of us all from going through all of this periodically ;-)
Jimmy Pan (dspjmr) wrote : | #13 |
I have the same problem in ubuntu 16.04.
Dmitry (crazydimson) wrote : | #14 |
I have the same problem in ubuntu 16.04.1 x64
Matthew Gregg (mcg) wrote : | #15 |
Same problem in 16.10 as up updating today.
tags: | added: xenial yakkety |
Sadi Yumuşak (sa-yu) wrote : | #16 |
Unfortunately the problem has got worse in Ubuntu 16.10 with Nautilus 3.20.3: nothing can be moved to the "Rubbish Bin" anywhere in an NTFS partition on the hard disk now (the reason given for this is "Unable to find or create wastebasket directory" and manually creating such a directory leads to nothing) although no such problem exists for removable media such as USB hard disks :(
Sadi Yumuşak (sa-yu) wrote : | #17 |
IMPORTANT UPDATE:
Now that we know the root cause of this problem thanks to CzBix (see https:/
https:/
It seems we need to wait for a patch to be made to a patch made to the original package, as that patch --I'm told-- also serves an important purpose which should not be omitted (as the workaround above, although it seems quite harmless, I don't know)
Therefore I think it is better to follow the developments there, and close this one.
Aravind R (araviaravi) wrote : | #18 |
Ubuntu 17.10 same issue
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.