Yes, I see this too. marking dogfood.
Note, I only see this after a clobber build.
reproduced on ftp://sweetlou/products/client/seamonkey/unix/linux/2.2/x86/1999-12-17-08-M13/ne tscape-i686-pc-linux-gnu.tar.gz Steps to reproduce: 1. run ./mozilla -installer 2. press new 3. enter profile (or leave default) 3. press next Actual results: blank screen comes up and hangs Expected results: ProfileWizard should close and seamonkey launch Next button should be disabled on this screen , and you should be allowed to press previous/cancel or finish. If you press finish, profile gets created Note: running ./mozilla (after deleting .mozilla) brought up wizard which allowed for a profile creation and launch. Invoking the wizard from the profile manager with new was the only way I could reproduce this. Also able migrate an existing 4.x profile.
This can be reproduced with ./mozilla also. After entering profile name or using default, pressing the next button causes the hang, pressing finish creates the profile and launches. Not a blocker
Putting on PDT+ radar.
M12 1999-12-17-10-M12/ does not exhibit this behavior-next button is disabled This is on the M13 builds - first one I tested today-sorry, Also seeing on Win95
*** Bug 22081 has been marked as a duplicate of this bug. ***
The following patch gets me through the error, but I did exit to shell after filling in the profile (maybe another bug). Next start, mozilla ran beautifully. syd Index: wizardHandlerSet.js =================================================================== RCS file: /cvsroot/mozilla/xpfe/global/resources/content/wizardHandlerSet.js,v retrieving revision 1.2 diff -r1.2 wizardHandlerSet.js 105c105 < ( arguments.length && nextButton ) ) --- > ( window.arguments && window.arguments.length && nextButton ) ) 108c108 < ( arguments.length && !nextButton ) ) --- > ( window.arguments && window.arguments.length && !nextButton ) ) 113c113 < ( arguments.length && finishButton ) ) --- > ( window.arguments && window.arguments.length && finishButton ) ) 116c116 < ( arguments.length && !finishButton ) ) --- > ( window.arguments && window.arguments.length && !finishButton ) ) 121c121 < ( arguments.length && backButton ) ) --- > ( window.arguments && window.arguments.length && backButton ) ) 124c124 < ( arguments.length && !backButton ) ) --- > ( window.arguments && window.arguments.length && !backButton ) )
The patch appears to be invalid, working with Ben and rginda on this...
Ben, this is in your wizardHandlerSet.js file so I assume it's related to changes you've made recently.
18 years ago
I have a fix that appears to work on Windows 95 at least, and corrects some unrelated dumbness on my part. Can someone test/approve it for me? I'll created it as an attachment to this bug.
(sorry bout all the spam..)
*** Bug 22197 has been marked as a duplicate of this bug. ***
Verified that the fix works under Linux/x86. r=cls
Ben, you can check the fix into the tip.
On M13 builds for Win 1999122109, NEXT button is not disabled last page, but pressing it does not cause a problem-it just does nothing. You can press FINISH and create a profile. I am finding that you can only create one profile per run-probably not an issue for most users, but found in testing renaming and deleting of profiles.
Ben, if this is checked in, can you mark this as fixed?
18 years ago
seems to be fixed now (although people are reporting other, different problems ;)
Linux build 1999122308 The original problem is fixed, I will log problem for other behavior I noted- ie can only create one profile per run and next button not disabled.
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.