Currently Being ModeratedApr 11, 2013 12:46 AM (in response to Linc Davis)
Thanks for the reply.
If I restart my mac and launch the app as you suggested, the OS does NOT give me the warning. ???
(If I then restart my mac again and now try to open a pdf in my usual manner (double-clicking on the pdf), I once again get the warning.)
Currently Being ModeratedApr 11, 2013 4:32 PM (in response to Linc Davis)
Thanks for the suggestion. I followed your instructions but I am still get the same behavior unfortunately.
Not sure if this is helpful or not:
Apps giving me problems include Skim, LibreOffice, Xee, MplayerX.
Apps NOT giving me problems are Pages, Xcode, Firefox, Thunderbird, Alfred, Picasa, iPhoto, QuickTime Player, VLC, ...
Currently Being ModeratedApr 11, 2013 4:55 PM (in response to eipi)
If you have more than one user account, you must be logged in as an administrator to carry out these instructions.
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Currently Being ModeratedApr 11, 2013 6:49 PM (in response to Linc Davis)
Linc, thanks again for your help.
I haven't as yet setup full backups for my system, and it will probably be a while before I do so. Is there anything else I might be able to try?
Currently Being ModeratedApr 11, 2013 8:03 PM (in response to eipi)
You need to back up before you do anything else. That's a higher priority than solving the problem in your original post.
Currently Being ModeratedApr 11, 2013 10:23 PM (in response to Linc Davis)
OK - lets leave it for now. Once I have a full back up in place I'll respond again to this thread. Hopefully you'll still be available/happy to help me out at that time.
By the way, if you don't mind, could you briefly outline what you believe has happened? Is the problem indeed a result of the lsregister command or could it have a different cause? (I'm new to macs and only used the lsregister command after others had mentioned they had had success with it.)
Currently Being ModeratedApr 11, 2013 10:29 PM (in response to eipi)
You seem to have some applications with the quarantine attribute set, which causes the warnings. What that has to do with the Launch Services reset is not clear.
Currently Being ModeratedApr 22, 2013 3:42 PM (in response to Linc Davis)
Well I no longer have this problem - it seems to have corrected itself. (I haven't done anything to try to correct the problem since I last posted here.) Perhaps it was some sort of cache issue?
ls -l@ /Applications
all the apps that were giving me problems still have a
entry. Not sure if that is normal or not.