Closed Bug 726488 Opened 13 years ago Closed 11 years ago

dylib shared libraries are associated with SeaMonkey on install

Categories

(SeaMonkey :: Installer, defect)

Product:
SeaMonkey
Component:
Installer
Version:
SeaMonkey 2.7 Branch
Platform:
All
macOS
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 806236

People

(Reporter: jake-bmo, Unassigned)

Details

When SeaMonkey is "installed" on a Mac (ie. when it is extracted and ran for the first time, and OS X looks through its Info.plist) it becomes associated with "*.dylib" files. Each one becomes a "SeaMonkey Shared Library" instead of the default "Shared Library". It is not appropriate for SeaMonkey to grab this file association - *.dylib files are definitely not specific to SeaMonkey, and making them appear as such can be harmful or confusing to users.
It looks like the problem arises from here: http://mxr.mozilla.org/comm-central/source/suite/app/macbuild/Contents/Info.plist.in#114
Hmm CVS blame says it comes from Bug 330053 - Make SeaMonkey capable of generating a reasonable build with MOZ_XUL_APP set. but was probably inherited from XPFE or something. cc KaiRo.
Looking even further back I see: 1.1 <dbaron@dbaron.org> 2005-02-19 13:02 Use MOZILLA_VERSION for the version in Info.plist so it doesn't need to be updated by hand. Rename Info.plist to Info.plist.in accordingly. b=229467 r+sr=bryner Even further back: 1.9 <lordpixel@mac.com> 2003-06-10 19:04 Fix for bug 88393 "Check in a high-resolution application and document icon suit e for Mac OS X". r=timeless, sr=sfraser@netscape.com
Actually Stefan would know more about OSX. Changing CC to Stefan.
Actually, there seems to be a lot of questionable file extensions in there...
Confirming - there's really no point to associate these file extensions to seamonkey. And then I don't just mean .dylib, I also mean the binary files listed and also the shlib extension (and possibly some more).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yes. I had a look at the Firefox and Thunderbird versions and they don't seem to have any of the junk we inherited from the Netscape days.
Hi anyone/all, how does one dissociate SeaMonkey from .dylib files? I would like my .dylib files with their original icon please. Thanks David
It seems like the latest version of SeaMonkey doesn't have these file associations anymore. If you have the latest version and SeaMonkey still associates itself with .dylib files, you somehow have to trick your Mac into reprocessing the program's Info.plist so it realizes that those extensions should no longer be associated with SeaMonkey.
Thanks Jake, I've solved the issue for the most part through various stumblings around that I'm probably unable to reproduce and a fair bit of reading. From memory it appears that when a program gets registered there are processes that make metadata stick pretty well globally whereas there are places that Spotlight doesn't ordinarily go (index). Hence, one can end up in a shizophrenic situation where there is different metadata for the same file type between Finder, Spotlight search and what one gets via mdls on command line-even after the info.plist is trashed. I'm no expert, but from what I recall an uninstaller that deregisters the app would help prevent this. Cheers David
This was fixed for 2.17 when I did a clean-up of the info.plist file in bug 806236, so I'm duping this one against bug 806236.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.