Closed Bug 123360 Opened 23 years ago Closed 22 years ago

ProfileManager/ProfileMigration icons do not launch application

Categories

(Documentation Graveyard :: Help Viewer, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME
Future

People

(Reporter: agracebush, Assigned: ccarlen)

Details

build 2002020403 Application can only be launched with N6 icon. User has to have more than one profile to see Profile Manager. Not sure this belongs to Profile Manager component- cc'ing jj to see if it is build issue
What happens when you double-click on "Netscape Profile Manager"? this launches NS6 for me and displays the PM dialog. If it doesn't for you, please document what happens instead. Also, you can try to _drag_ the Profile manager icon onto Netscape 6.
When I double click on either icon I get a message: Application Launch failure: The application 'Netscape 6' could not be launched because of a shared library error "<Mozilla><><><>" ( I thought something in Profile registry or profiles themselves may be corrupted so I deleted the appropriate files - still get the error however.) Drag/drop does work- thanks I don't see this behavior on Mac OS 9 however
doesn't sound like a fe issue
Assignee: ben → ccarlen
Component: Profile Manager FrontEnd → Profile Manager BackEnd
maybe not frontend but even less backend. this is just a MacOS Finder issue. when double-clicking on a document, the Finder launches the first app in its internal database that can open that file type, which in Grace's case is probably another copy of Netscape 6 she has somewhere else. Proof is that drag-and-drop method to force launching the most recent copy of NS6 works for her. The best we can do is release note this issue: "if you have multiple versions of Netscape installed on your mac and wnat to invoke the Profile Manager, drag-and-drop the Netscape Profile Manager icon onto Netscape 6 rather than double-click it." Conrad, feel free to change the product/component/owner of this bug accordingly.
The only thing that can be wrong on our end is if the file creator of those files (Mozilla Select Profile, etc.) is not set correctly, or a bundle issue. As far as which application, if any, opens when you double-click one, we're at the mercy of the OS. It's not a profile mgr issue either way. JJ, what component would packaging be?
profile manager and profile migration have indeed their file type and creator set correctly (MOZZ for Mozilla and MOSS for Netscape), so it's not a packaging issue -- if it was, the right component would be Build/Config. cc'ing Steve Rudman for him to decide if this should be added to the release notes for future releases.
Component: Profile Manager BackEnd → User
Product: Browser → Documentation
Version: other → unspecified
Futuring until then.
Target Milestone: --- → Future
The Profile Manager and Profile Migration icons were not working for me in previous OS X builds, but I just tried with Build 2002032608 and the Profile Manager came up just fine. With the same build, the Profile Migration icon only brings up Mozilla; there is no sign of any attempt to migrate any profiles. This may be the expected behavior though, but I am not sure. I do not have any 4.x profiles, but I do have some profiles for the Classic Mozilla builds. Shouldn't the Profile Migration utility migrate over my profiles from the Classic build?
This seems to work properly with Mozilla 1.2b 2002101612 on Mac OS X 10.2.1
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Verified. Grace tried this again with the branch build on OS X and it works fine. Thanks Grace!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.