'open with' duplicates wont go away

[Rossatron]

i tried using

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain user;killall Finder;echo "Open With has been rebuilt, Finder will relaunch"

which works - temporarily, but after some time all the duplicate entries just come back :/ anyway to solve this?

 

[Weaselboy]

When you say after some time they come back, are they coming back after app. updates? If so, that is a bug in the way certain apps update. For example every freakin' time Skitch updates in the App Store I get the duplicate entries.

If this is what you are seeing, it is not something you are doing wrong, it is just a bug.

 

[Rossatron]

No, it's not after an update. Friday before last, I cleaned the list. Today (no updates what-so-ever) all the duplicates are back. I can even tell you that on Sunday before the said Friday it also happened - at first it was just wierd, but when I noticed I tarted tracking the problem and it does come back after a whole. I can do a clean install of ML if that'd work, but I feel it's just an exaggerated solution to (what should be) a simple problem

Edit: tell you what, though: it's possible this two-weeks period I had an ML update. Will that cause the problem, even though its not an app update?

 

[Weaselboy]

No, it's not after an update. Friday before last, I cleaned the list. Today (no updates what-so-ever) all the duplicates are back. I can even tell you that on Sunday before the said Friday it also happened - at first it was just wierd, but when I noticed I tarted tracking the problem and it does come back after a whole. I can do a clean install of ML if that'd work, but I feel it's just an exaggerated solution to (what should be) a simple problem

Edit: tell you what, though: it's possible this two-weeks period I had an ML update. Will that cause the problem, even though its not an app update?

Hmmm... I am baffled. I double checked and you are running exactly the correct Terminal command to fix it. A ML point update would not cause this. A clean install seems pretty drastic.

Can you think of perhaps anything else going on that seems to coincide with this? All I have ever seen cause it is app updates.

 

[Rossatron]

Nope, no updates