Closed Bug 15792 Opened 25 years ago Closed 25 years ago

Javascript error when Profile manager tries to launch Seamonkey

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bijals, Assigned: sspitzer)

Details

Setup: 1) Launch Seamonkey (today's 4:00pm install.exe build on NT) 2) Choose a migrated profile 3) Click on Start button Actual Results: This only occurs the first time. All other times I do not see the profile picker since it uses the last profile I used. This brings up an interesting question which is how do I switch profiles if I never see the Profile Manager again. Anyway, here's the Javascript error in the dos prompt: run LoadDetectorsMenu() Javascript Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FIALURE) [nsIProfile.startCommunicator]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///C:/Program Files/Netscape/Seamonkey/x86rel/chrome/profile/content/default/profileManager.js :: Start Communicator :: line 120" data: no] Expected Results: Navigator or Mail comes up. Build date and platform: 1999100713 on NT
Status: NEW → ASSIGNED
I added some try / catch statements to the js, so now you should just get an alert. but you still won't be able to start up. please try again with tomorrow's build. if you still can't launch (I'm not expecting it to work) call me at x4129 and I'll come take a look and see if I can debug it. I just checked in some debugging statements to help us tomorrow. accepting bug.
Received the dialog saying that I can not start with my bijals profile.
when it failes, and you get that alert, is any additional information coming out at the console window? I added some printfs late last night to help track this down.
The dos prompt text that appears every time I hit the START button and the OK button on the can't use bijals profile is as follows: commonDialogOnLoad Move window by 47,105.4 screen x 0screen y 0
I am having trouble reproducing this bug. I downloaded this build, migrated my single profile and launched with no profile errors noted on console, only progress statements for Profile Manager. Bijals, try using apprunner -installer to get to Profile Manager to add a second profile-once you have more than one profile, apprunner alone will take you to Profile Manager where you can select which profile to use.
Bijals, Are you still seeing this Javascript error on more recent builds? Are you able to create a 2nd profile with the mozilla -installer (win command)? Grace
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Works for me now. No Javascript error since Monday's build.
Status: RESOLVED → VERIFIED
no errors on 1999101908 build either
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.