Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

FileVault and Launch Services

I seem to have a conflict between FileVault and Launch Services. Whenever I assign a custom URL handler or file extension, the settings are forgotten on a reboot.

Can someone please verify if this happens with their set up too? It's exceptionally annoying for me, even though I don't reboot that often.

To duplicate:
1) Create a new account
2) Log in to the new account.
3) Enable FileVault
4) Modify Launch Services settings. I usually start Firefox and set it as the default browser when prompted. Changing assignments for file extensions (using Finder or RCDefaultApp) will also exhibit the same issue.
5) Reboot (don't just log out) and, if necessary, log into the new account.
6) Check Launch Services settings again. In my case, I start Firefox again. It will prompt to be set as the default browser again, indicating that the previous settings were not retained.

Some cases, it seems the settings seem to be retained over one reboot, but will be lost the next. Settings will be preserved when only logging in and out without a reboot.

The problems go away when I disable FileVault. I've checked ~/Library/Preferences/com.apple.LaunchServices.plist and it's fine across reboots. It seems that LaunchServices itself isn't reading the file when its in FileVault.

This a a clean installation of Leopard, not an upgrade of any sort.

Thanks in advance.

MacBook, Mac OS X (10.5)

Posted on Nov 12, 2007 8:39 PM

Reply
Question marked as Best reply

Posted on Nov 19, 2007 6:35 AM

Yes I see it too. In my case it seems com.apple.LaunchServices.plist is resetting with every boot. I typically change various video types from quicktime to vlc among other things. I'm plaaning on seeing if I can work around this with a login script.
In addition to this behavior I cannot get launch services to truly respect file extensions. My primary example: I have digital comics. These are typically zipped or rared sets of jpegs, using zip/rar purely for packaging purposes not compression. The extensions are then standardly set to cbz or cbr (comic book zip/rar). If I assign these to the comic reader, it works until reboot, but .zip and. rar extensions are also mapped to the reader. The opposite problem occurs if I set the zip/rar to something , The plist file does not record the extensions at all in in some cases, going strictly by the type of file, which actually are not different. This was no problem in 10.4.
77 replies

Oct 4, 2008 10:31 PM in response to thirteen37

It is truly amazing that Apple pays so little attention to making sure a major OS feature works right. This isn't some obscure issue that only occurs in very specific difficult-to-replicate circumstances. It's easily reproducible on any system using Leopard and filevault, and the fix seems to be quite simple as well (load the launchservices database a few seconds later). Many people have reported it - Apple just doesn't care if it works right or not, clearly. I love how the people at AppleCare and the genius bar will tell you, the second you mention filevault, that it doesn't work properly and you shouldn't use it. Clearly, no one at Apple does use it on a production system.

I can't wait for PGP WDE to support Boot Camp so I can be done with Apple's encryption once and for all.

Oct 25, 2008 5:15 PM in response to gordon142

One day, some high profile Apple guy (maybe even Jobs himself) will lose his laptop and regret not having proper encryption. FileVault is just another checkbox on the OS X feature list, not a real, usable system.

Anyone knows where to get Checkpoint's disk encryption software for the Mac? It seems the only versions on sale are the Windows ones. And more importantly, how well does it work?

Oct 26, 2008 2:01 AM in response to thirteen37

I called checkpoint about this the other day. They said to contact one of their regional resellers. Their focus is definitely on the enterprise, but they claim it is possible to get a single user version. Unfortunately, there is no demo available, and not even any specific information on exactly how it operates. Very mysterious. The guy on the phone claimed it supported partition-level encryption, so in theory it should work in a dual boot environment (an advantage over PGP).

I have not had much luck in contacting their partners. It seems most of them are not interested in selling to you unless you're buying a complete security solution for thousands of dollars for your company. Very annoying that it seems to basically impossible for an individual user to obtain their encryption product.

Jan 7, 2009 8:04 AM in response to Robertmtk

Not fixed. I just cannot believe they're ignoring so many users (though probably not the majority of OS X users)
The feedback page ( http://www.apple.com/feedback/macosx.html) states "We read all feedback carefully"... doesn't seem like that to me.

Actually, I don't think Apple sees this as a problem. It just defaults back to Apple's applications: Safari, Preview, Mail, etc. If it's a bug that would make Firefox the default browser and Adobe Reader the default PDF reader, then they'll certainly fix it.

Anyway, we should be sending feedback: http://www.apple.com/feedback/macosx.html
...even if there's almost no hope they'll fix it.

Feb 14, 2009 12:33 AM in response to thirteen37

I ran Software Update last night and was surprised to find Firefox/Thunderbird as the default apps when I restarted my computer. As a test, I set my prefs to Safari/Mail and they stayed that way after restart. After another change to Firefox/Thunderbird and restart, things seem OK.

I don't think I ever got around to applying a scripted solution suggested here, so I think this may be fixed.

Feb 14, 2009 1:44 AM in response to brentplump

Unfortunately, no, it is not fixed.

I downloaded and installed the Security Update, but the default browser would still revert back to Apple-preferred settings. (e.g.: Camino would revert back to Safari, Adobe Acrobat would revert back to Preview, etc.)

The tech people making Mac OS X must be stupid.

Send feedback here: http://www.apple.com/feedback/macosx.html

Mar 8, 2009 4:59 PM in response to thirteen37

Um, I finally got around to fixing the glitches in my FileVault Normaliser tool. Apologies to all who have hoped for it, or tried to contact me – life (you know, the real one) had me firmly in its clutches, and it took me ages first to notice the app did not kep file permissions up to date after its first run; then to figure out what I had done wrong (FYI: you can't daisy chain shell commands in a launchd command, if anybody is interested); finally, to fix it, give it a good long test run on my Air, and package it. Anyway, to make up for it, I will point you to the following link:

http://s3.amazonaws.com/filevault-normaliser/fvn-1.2.0-install.zip

where you can download the first official release of FileVault Normaliser. Download and unpack the zip and run the package inside it, following the setup prompts. Leopard ony, I'm afraid to say. The source (seeing the thing has to be GPL'ed, as it uses Platypus) is at

http://s3.amazonaws.com/filevault-normaliser/fvn-1.2.0-source.zip

The usual caveats apply (viz., I take no responsibility for any kind of effects the tool might have; for all I know, it might eat yout cat, burn your socks and run away with your hard disk, though it has done none of these in the last weeks on my computer). I will however gladly accept any kind of feedback at martin[DOT]kopischke[AT]googlemail.com, though my responses (and especially any enhancements) might be delayed. Sorry about that.

If things go right, you should run the app once when prompted to provide your admin password by the installer. Afterwards, your app permissions should be normalised and the launch services reset each time you log on, without you having to do anything about it. If you need to, you can also run the app manually (the installer should leave an alias to it in your Utilities folder); run without a parameter, it will normalise all your apps. If you drop an app on it, it will normalise just that one; note however that you will have to provide your admin password each time you do this, unlike the automatic process at logon.

To uninstall, do:
– /Library/Application Support/FileVault/
– /Library/LaunchDaemons/net.kopischke.fvn.NormaliseAppPerms.plist
– /Applications/Utilities/FileVault Normaliser
– ˜/Library/LaunchAgents/net.kopischke.fvn.ResetLaunchServices.plist

Note that app permissions will remain normalised even after uninstall.

Cheers.

FileVault and Launch Services

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.