Closed Bug 39423 Opened 24 years ago Closed 24 years ago

[regression] rename profile does not work

Categories

(SeaMonkey :: Startup & Profiles, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: agracebush, Assigned: bugs)

References

Details

(Whiteboard: [nsbeta2+][6/15])

build 2000-05-16-08 Linux 
Steps to reproduce:
1. remove ~/.mozilla
2. run ./netscape -profilemanager
3. choose a profile and press rename

Expected result: dialog asking to enter new name for this profile
Actual result: nothing ( console window says:  *** newName = || )
Putting on [nsbeta2+][6/01] radar.  This work must be done by 06/01 or we may 
pull this for PR2.
Keywords: nsbeta2
Summary: [regression] rename profile does not work → [regression] rename profile does not work
Whiteboard: [nsbeta2+][6/01]
Priority: P3 → P2
Target Milestone: --- → M16
Changing from [06/01] to [06/15]
Whiteboard: [nsbeta2+][6/01] → [nsbeta2+][6/15]
Move to M19.
Target Milestone: M16 → M19
bryner tells me this is failing because of something to do with hidden window 
initialization coming after the profile step, and commondialogs relying on 
hidden window, and ensuing train wreck. cc'ing rjc. 
(Historical info follows:]  Among other things, creating the hidden window 
causes bookmarks to be read in.  To read in the bookmarks, you have to know 
which profile is active.
some investigation shows that this bug was introduced in part by warren's 
checkin to nsNetSupportDialog.cpp on May 15. Giving the bug to him ;) 
Assignee: ben → warren
You're going to have to give me more to go on than that.
Assignee: warren → ben
*** Bug 40758 has been marked as a duplicate of this bug. ***
*** Bug 41603 has been marked as a duplicate of this bug. ***
fixed
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Commercial build on Linux showing the following error when trying to rename

JavaScript error: 
 line 0: uncaught exception: [Exception... "Component returned failure code: 
0x80004005 (NS_ERROR_FAILURE)
[nsIStringBundle.GetStringFromName]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  
location: "JS frame ::
chrome://communicator/content/profile/profileManager.js :: RenameProfile :: line 
69"  data: no] 
  
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Mac commercial build fails for rename also
Mozilla builds on all platforms have this fix- only one not checked is Win 
Commercial
failing on Linux M16 branch - 2000-06-07-13M16
if this is a string bundle problem, it is probably fixed on the tip.

(I recently remove profileManager.properties from the tip of the ns tree.)

I did not remove it from the m16 branch of the ns tree.

I can easily do that, just let me know.
release noted
what's the status here, is this working on the tip? if so, I can close this bug. 
this is fixed on the tip.  last week, I removed profileManager.properties, so
there are no more string bundle errors.

marking fixed.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Not working again in build 2000061312 on Win98.
I'm not getting a crash just:
*** newName = ||
in the console.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I think the nightly you have may be based on the M16 branch rather than the tip, 
as the profileManager.js file in it is out of date, compared with the file in 
CVS (see 
lxr.mozilla.org/seamonkey/source/profile/resources/content/profileManager.js)

re-closing. 
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
yes, this would be fixed on the tip only, not on a m16 build.
Status: RESOLVED → VERIFIED
fixed in M17 builds for 2000614- all platforms
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.