|
|
How to rebuild the LaunchServices database
I can't see it, but a "?" pops into the command when I paste it into Terminal. If anyone else has the same problem, you could try pasting into a text editor, deleting the backslashes and excess spaces, and then copying and pasting the result into Terminal. It worked for me!
How to rebuild the LaunchServices database
When I type "lsregister" in Terminal (bash or tcsh shell), I get "command not found" in 10.3.2. Anyone else?
How to rebuild the LaunchServices database
Would that not be because the directory where it is to be found is not in your search path? That must be why the hint includes the complete path to it.
How to rebuild the LaunchServices database
When I used the lsregister command as given in the hint, with the full path, it did not work. I had to do "locate lsregister" to find the complete path for my system, which included two "Versions/A" folders in the folder tree.
How to rebuild the LaunchServices database
If you use this hint and have applications located someplace other than /Applications you need to append the path to the end of the command. The first time I ran it without any paths and my LaunchServices database included only applications on the boot volume.
How to rebuild the LaunchServices database
I had a strange problem in Tiger that when I clicked on a folder in the dock or dragthing it would launch iPhoto or Entourage. Running this command fixed everything.
How to rebuild the LaunchServices database
I tried a couple of hints here. This is the one that finally worked for me. I added -f, and I also appended the path to my personal applications folder (within the applications folder) at the end: |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments 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.13 seconds |
|