If I delete any asset in the ‘Project’ tab of the Unity Editor, it momentarily forgets about it.
But as soon as I click the editor (and it scans for changed files), it reimports the deleted files because they weren’t actually deleted in the file system.
This bug was introduced somewhere around 5.4 but hasn’t been fixed since.
I am no longer experiencing this bug, though I can’t pinpoint whether it was an update to Unity or to my system that fixed it.
A possible cause could be that I was hosting my Unity projects on an NTFS partition which I mounted with default settings (thus, everything belongs to ‘root’ and has 777 permissions).
At some point, I changed my fstab so the files on the NTFS partition are owned by my user (permissions set to 775)
I am still experiencing the issue. I’m using ext4 filesystem with proper permissions on my user (my home directory).
When I select an object in the Project view and I choose Delete it disappears instantly and then reappears almost instantly. I always have to go to the containing directory and delete the file+meta.
This is definitely not normal behavior - information on anything “unusual” about your system, project directory, etc., that could help us pin this down would be useful.
Currently I’m on openSUSE Tumbleweed 20170808.
Filesystem Ext4 on an SSD drive (Samsung Evo 850 Pro) with mount options “defaults,discard,noatime,errors=remount-ro”.
Path for my projects is ~/projects/Unity/, tried with and without spaces in project folder name.
Permissions on my home folder are default, 0755 for directories, 0644 for regular files.
There are any logs I can cat where Unity stores debug informations that can help uncover this issue?
I’m also having the same issue. My project folder have the same user group by which unity editor is running. Still I cant delete any asset from editor.
But replacing or renaming works fine, so I dont think its a file/folder access issue.
I can confirm @jayadratha behavior, same for me. Creating, renaming and moving are all working fine, deleting is the only issue. I tried with the latest release, 2017.1.0xf3Linux, same issue as above, nothing changed.