User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.81 Safari/537.1 Build Identifier: Thunar 1.2.3 if, after you delete a file, you create a file with the same name as the deleted one in a terminal, thunar still says the type of the new file is that if the old one. Reproducible: Always Steps to Reproduce: 1.create a file (lets say an mp3 file) 2.delete this file 3.create in a terminal a file with the same name (lets say a symlink) Actual Results: thunar says this new file (the symlink) is still the same as the old one (an mp3 file) Expected Results: it should refresh and properly recognize the new file's type (a symlink).
Thunar 1.4.0git-ee26db2 on my end and I can't reproduce this. Whenever I delete a file and then create a symlink in its place it shows up as a symlink.
I just noticed that the permissions listed are those of the link's target. No idea if that's the desired behavior however.
I can also confirm this on Thunar 1.6.3 (Xfce 4.10). More specifically if you create a stale symlink from terminal $ ln -s nx nx-link Open thunar $ thunar & See that nx-link is viewed with broken link icon Create the link target $ touch nx Refresh thunar window (press F5) Thunar continues to believe this is broken link The link destination is cached. I use this configuration for removable medium and make links to a home folder. Unfortunately, if thunar caches the incorect link destination (e.g. broken) is it not being updated when the links are made working from external sources.
This is actually a duplicate of bug #11008. While the problem in the original post should be fixed by the patches, it will need more logic to fix the reload of symlinks when their targets change in a way that doesn't hurt performance too much, especially for folders with many files.
I suspect this bug is also the cause of thunar failing to refresh directory permissions. For example, I just loop-mounted a directory as root, and it Thunar (correctly) displayed it with a lock icon. I then unmounted it, deleted it, and created a new directory as myself, with the same name as the deleted directory. Thunar (incorrectly) displayed the new directory with a lock icon, no matter how many times I refreshed or navigated to a different dir and back again. This is on Thunar 1.6.6, Xubuntu 15.04 (vivid).
I retract the example in my last comment. (I made a mistake in my loop-mount-delete-recreate-lock-icon test.) Thunar still seems to have trouble with changed permissions, though. It recently failed to notice when I mounted an sdcard with the lock switch in place and then ejected and remounted it with the switch unlocked. Thunar refused to let me create a new directory on that card even though there was no longer a permissions problem. Killing all thunar processes and restarting thunar cleared the problem.
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/thunar/-/issues/42. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev