Closed Bug 15570 Opened 25 years ago Closed 25 years ago

[REGRESSION] Apprunner will not launch after profile is migrated

Categories

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

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: agracebush, Assigned: sspitzer)

Details

Steps to reproduce: 1.Remove mozregistry.dat/Users50 directory 2.Run apprunner -installer 3.Select a profile for migration Expect: to launch seamonkey with the selected profile Actual: ProfileManager window stays open, apprunner is not launched, the following error shows on console: JavascriptError: uncaught exception: {Exception....Component returned failure code: 0x80004005 <NS_ERROR_FAILURE> [nsIProfile.startCommunicator] nsresult: "0x80004005 <NS_ERROR_FAILURE>" location: "JS frame :: file://~~~/x86rel/chrome/profile/content/default/profileManager.js :: StartCommunicator :: line 77" data: no] WIn build 19991005 so far Note Profile does get migrated to Users50 directory but is not usable
Assignee: selmer → sspitzer
I'll look into it.
gbush, do you still have this problem?
I should have said: "do you still have this problem with the latest 10-5-99 build?"
the first respins on Win and Mac were bad, still waiting for next ones
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-10-05-12-M11/ this migration problem did not occur in this build- or today's build
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I think this is fixed. marking fixed.
Status: RESOLVED → VERIFIED
Target Milestone: M11
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.