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

"open with" duplicate entries

"at times" using "open with" shows many duplicate entries....reboot fixes it for a while..


I'm still trying to determine what is triggering this.


Any idea? Anyone see this in 10.8? I couldn't find anything searching the forums.

User uploaded file

Macbook Pro 15 (2.4 Santa Rosa), MacBook 13 (2.0), iMac 17, Mac OS X (10.7), iPhone 3GS v4.3.1, 100% Apple networking (AEs, AXs, TCs)

Posted on Aug 29, 2012 11:02 AM

Reply
Question marked as Best reply

Posted on Aug 29, 2012 11:23 AM

I am not familiar with all the causes of this phenomenon, but it happens to me from time to time, and I know why it is for me. I work with "clone" images all the time with dev work. When a clone is mounted alongside booting into the main volume, Launch Services, which keeps track of applications used to open certain file types, "sees" the other application files on the mounted clone volume, and adds them to the database, resulting in the apparent duplication of "open with" entries.


Resetting the 'Open With' menu will remove duplicates and ghost applications (ones you have deleted) from the list. You reset the 'Open With' menu by rebuilding the Launch Services database your Mac maintains. There are multiple ways to rebuild the Launch Services database, including third-party system utilities like Cocktail and Onyx.


If you don't own a system utility that can rebuild the Launch Services database, don't worry; you can perform the rebuild yourself using Terminal.


Using Terminal to Rebuild the Launch Services Database:


Launch Terminal, located at /Applications/ Utilities/.


For OS X 10.5.x and later, enter the following at the Terminal prompt:


/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -r -domain local -domain system -domain user


----------------


I don't know wjhy it is happening for you, but rebuilding the database will at least reset things to normal. The question to ask is whether you have other mounted volumes, say from other systems on your network, that contain Mac Apps.


I have also found a way to keep it from happening (in certain cases, for my dev work). When I create a clone, I also create what is called a "fstab" file entry, in the fstab file. This entry prevents named drives from auto-mounting. So, if I boot to a clone, my main volume on my internal SSD won't mount. Hence, no extraneous Launch Services database entries will created on the clone drive. If however, I boot to my main SSD, and then mount a clone, I don't use any fstab entries on the main SSD. This just means I have to periodically rebuild the Launch Services database. It is way too much trouble keeping fstab entries for all my clone drives on my main SSD. I only use the fstab method on the clones themselves.

88 replies
Question marked as Best reply

Aug 29, 2012 11:23 AM in response to justin_case

I am not familiar with all the causes of this phenomenon, but it happens to me from time to time, and I know why it is for me. I work with "clone" images all the time with dev work. When a clone is mounted alongside booting into the main volume, Launch Services, which keeps track of applications used to open certain file types, "sees" the other application files on the mounted clone volume, and adds them to the database, resulting in the apparent duplication of "open with" entries.


Resetting the 'Open With' menu will remove duplicates and ghost applications (ones you have deleted) from the list. You reset the 'Open With' menu by rebuilding the Launch Services database your Mac maintains. There are multiple ways to rebuild the Launch Services database, including third-party system utilities like Cocktail and Onyx.


If you don't own a system utility that can rebuild the Launch Services database, don't worry; you can perform the rebuild yourself using Terminal.


Using Terminal to Rebuild the Launch Services Database:


Launch Terminal, located at /Applications/ Utilities/.


For OS X 10.5.x and later, enter the following at the Terminal prompt:


/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -r -domain local -domain system -domain user


----------------


I don't know wjhy it is happening for you, but rebuilding the database will at least reset things to normal. The question to ask is whether you have other mounted volumes, say from other systems on your network, that contain Mac Apps.


I have also found a way to keep it from happening (in certain cases, for my dev work). When I create a clone, I also create what is called a "fstab" file entry, in the fstab file. This entry prevents named drives from auto-mounting. So, if I boot to a clone, my main volume on my internal SSD won't mount. Hence, no extraneous Launch Services database entries will created on the clone drive. If however, I boot to my main SSD, and then mount a clone, I don't use any fstab entries on the main SSD. This just means I have to periodically rebuild the Launch Services database. It is way too much trouble keeping fstab entries for all my clone drives on my main SSD. I only use the fstab method on the clones themselves.

Aug 29, 2012 11:34 AM in response to SP Forsythe

Apps on other volumes shouldn't cause multiple entries in "Open With" unless they are different versions of the application. i.e. Abode CS4, Adobe CS 5.


Try this syntax for the Terminal command...

(be sure to copy the entire line it's a scroll)



Code:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user


Then press return. Wait until terminal returns to the command line. Quit Terminal. After that, log out and back in or restart. Let us know



Or, use the free utiltiy OnyX to do the same via gui

Aug 29, 2012 11:34 AM in response to SP Forsythe

These two articles may be of interest to you, if you continue to keep those clones around on a physical drive that is mounted on boot.


http://www.tannr.com/2009/09/01/preventing-a-volume-from-automatically-mounting- in-os-x/


http://hints.macworld.com/article.php?story=20060930150059172


Just so you know, fstab files can be more easily made, without error, by using a program called TinkerTool System(not regular TinkerTool). Just be aware that TinkerTool System is somewhat advanced tweaking software, not the harmless version they have for consumers (TinkerTool)

"open with" duplicate entries

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