Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Preserve app preferences and settings when using FileVault' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Preserve app preferences and settings when using FileVault
Authored by: Typhoon14 on Nov 23, '09 09:30:30AM

As the submitter of the original hint referenced here regarding this problem, this issue seems to be fixed on all versions of Snow Leopard. Is the submitter using an installation that was upgraded to snow leopard (especially while FileVault was active)? This may have something to do with it. A clean install of snow leopard should definitely NOT exhibit this issue.

Actually, there seem to be quite a lot of improvements to FileVault in Snow Leopard. In addition to fixing this issue, login times is greatly improved (it used to absolutely crawl with FileVault enabled) and some general compatibility issues seem to have been fixed (for instance, some installer packages would not run properly with FileVault active on Leopard - all of these seem to work fine on SL though.)

FYI, the issue on Leopard was never that the launchservices database was actually getting reset, but that it was not getting properly read at boot time. If you open the actual file you should fine that all your user-set associations are still alive and well. What the system was doing was trying to read this file before the user directory (which is an encrypted disk image with filevault) had actually been mounted. This would result in an error and revert to the master database file.

Not to criticize the submitter here, but it still seems that my earlier solution is better. It doesn't force you to use one launchservices database for all users — in fact, it as closely as possible duplicates what the system should be doing on its own.

Again though, if you are using OS 10.6, you should NOT be having this issue. This was a 100% reproducible issue on 10.5, but I have not over several installs been able to find this problem occurring in 10.6. My first suspicion is that the submitter did an upgrade install. I would highly recommend a clean install. Failing that, it is possible simply turning off filevault and activating it again will fix the issue.



[ Reply to This | # ]