GNOME Bugzilla – Bug 699076
Nautilus upgrade resets hidden file status
Last modified: 2013-04-28 11:58:02 UTC
nautilus 3.8.1 on Archlinux Problem: Every time I open nautilus, it shows dot (hidden) files and directories. If I hide dotfiles (Ctrl+H), close and reopen nautilus these files are visible again. I would expect nautilus to remember my preferences. This is a regression over 3.6.x. Reproducible every time.
I think there was no change from 3.6 to 3.8 with relation to this. The "Show Hidden Files" option in the View menu (or Ctrl+H) affects only the current view. There is a "Show hidden and backup files" checkbox in the Preferences which controls the default for all new windows. Can you check your Preferences?
Looking at the preferences, the active option was indeed to show hidden files (and deactivating it produces the desired behaviour). So I think the report should be: nautilus does not remember user preferences when updating from 3.6 to 3.8. I don't know if you consider this a bug or a feature. Please close/fix appropriately.
(In reply to comment #2) > So I think the report should be: nautilus does not remember user preferences > when updating from 3.6 to 3.8. If the preferences were changed without any user intervention, that is a bug somewhere (not necessarily nautilus). This is not a reset to defaults, because the default option is not to show hidden files. Are you sure the preference was not changed by someone using your computer?
Yes, I am. No one else used the computer, nautilus did not show hidden files before the update to 3.8 but did show them after (with the option enabled). Anyway, it's not a major issue when setting the option works.
If you are ok with that, I'll close this bug. Testing the upgrade problem would require downgrading and upgrading again, and it may not even be reproducible. If I see another user reporting the same upgrade problem, I'll reopen this then. Aside from that, it seems that the difference between Ctrl+H and the option in the preference is not obvious for some users. We got a similar report a year ago, so I'm marking this as a duplicate. *** This bug has been marked as a duplicate of bug 640442 ***