|
|
10.5: Force FileVault to read Launch Services data
Good tip, but please don't use this as a soapbox for your pet bug. You have LaunchServices issues you can work around - I have kernel panics coming from kernel firewalling code. Who should be prioritized here? Just file your bug and let them do their work.
10.5: Force FileVault to read Launch Services data
Pet bug? Yes, kernel panics are more serious, but since we FileVault-users have to logout every time we want to have TimeMachine generate a backup, I have to log out daily. Imagine the pain it is to revert to my own default Apps every morning!
10.5: Force FileVault to read Launch Services data
This has been intermittently happening to me since at least Tiger, but it's always after rebooting, never on logout.
10.5: Force FileVault to read Launch Services data
Yes, this does happen only on a reboot. This gives you lots of times to make many changes to the LaunchServices database, only to see them all fly away as soon as you have to restart for any reason. Fun!
10.5: Force FileVault to read Launch Services data
Yes, you're right, only on reboot. However, since SteerMouse stopped working for me after a logout/re-login with Leopard, Restarting is the only option I have in order to get my Backup... :-P
10.5: Force FileVault to read Launch Services data
"pet bug"? This is a serious issue, and it occurs for anyone using filevault, not just in specific circumstances. When using a major OS function, another major function does not work. I do not know what firewall bug you're talking so I can't say how wide ranging it is. In any case, the two are not related. I want lots of people to tell apple to fix this bug so it gets fixed sooner. If you want the bug you speak of fixed, publicize it and get people to submit bug reports. Don't go around complaining that other people want apple to fix different bugs. This doesn't help anything and just makes people mad.
10.5: Force FileVault to read Launch Services data
As Typhoon14 says below, this is a serious issue, affecting other people too, so his tip is not a soapbox for his "pet bug". MacOSXHints isn't just for reporting ways to get OS X to do things that aren't always obvious--it's also for reporting fixes and workarounds for bugs. This tip isn't out of place or self-serving at all--it's using MacOSXHints in exactly the way it was intended.
10.5: Force FileVault to read Launch Services data
This bug deserves to be fixed asap, as it does affect many users. It used to affect me too, before I switched to a non-FileVault account with a seperate encrypted disk image that holds my mail and personal stuff. I never figured out it had something to do with FileVault.
10.5: Force FileVault to read Launch Services data
Just because the workaround is 'easy', doesn't mean that the correct fix will also be as easy. It will most likely take an apple developer significantly more than 5 minutes.
10.5: Force FileVault to read Launch Services data
Now, there is one thing this does not fix, and that is the fact that the "this is the first time you've run this application" dialogs will appear every time after you logout or restart. For any appication not used prior to activating filevault. I believe these messages to be handled by the launchservices database as well, but for some reason this hint does not effect them. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.12 seconds |
|