Linked by Thom Holwerda on Wed 20th Feb 2013 10:52 UTC
Thread beginning with comment 553106
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2008-07-15
The problem occurs not because the database is corrupted, but because application developers don't check for existing entries when installing updates. For example, most applications on OS X use the Sparkle framework (or an in-house equivalent) to check for application updates at launch if the user has enabled this. Upon finding an update, you have the option to install it. However, at the install phase, the proper thing for the update to do is to query the LaunchServices database and, if an entry already exists there, to skip creating one. Sadly, particularly in apps that use their own updaters, this is forgotten and the result is duplicates. That being said, I do think that either OS X should do this automatically or else have an easily accessible option to do this (perhaps at the bottom of the open with submenu).
I haven't seen this on my current install of OS X which I've had for about a year, but I used to see this much more several years back. Maybe some application developers are starting to clean up their messes.