7984 - M6 aprunner gives blank mail config form then aborts on first run

Status: VERIFIED INVALID

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

Description

[David Woolley]

When first run, aprunner puts out a form for email customisation.  All the
fields are blank, including the default directory.  Even if you fill them in, it
then crashes as follows and you are left back at square one.

I did have M4 installed previously, but after the first abort I delete the
Mozilla registry, and did so after each subsequent abort.

This is the last screen full of diagnostics.

Name does not exist
Name Value: FullName    David Woolley
Inside SetValue
Name does not exist
Name Value: Email       [e-mail]
Inside SetValue
Name does not exist
Name Value: SMTP        mailgate.bts.co.uk
before for loop
DATA IS: ProfileName=djw%ProfileDir=\fred\mozilla%FullName=David Woolley%SMTP=ma
ilgate.bts.co.uk%
calling javascript reflection
!profileCore
Created nsProfileCore
!profileCore
after ! yes profileCore in if loop
yes profileCore
Entered Create Profile RoutineCreated nsToolkitCore
JavaScript error: parent is not defined
URL: file:///D|/fred/X86REL/res/profile/navigationFinish.xul LineNo: 49

Comment 1

[David Woolley]

For clarification:  I ran it twice before first clearing the registry, which
is why I say that one cannot get past this stage.

Comment 2

[Grace Bush]

Currently, apprunner does not automatically start up when profile manager is
completed. (that is coming soon). After profile data is entered, you are
returned to console if using command line or to ?? if using icon. Rerun
apprunner using either method and the app will launch.
Marking invalid-See big 7327 for similar situation

Comment 3

[David Woolley]

It looks like the underlying problem was failing to prompt with a default
directory, even though the text implies that there is one.  I presume it
is this which caused it to fail when I ran apprunner the second time.

Subsequently, I reset the system state before each attempt, that a second
run would not have worked, as I thought I'd established that a second run
wouldn't solve the problem.

Comment 4

[Grace Bush]

The form you see is a preliminary UI for Profile Manager which should be hooked
up to apprunner by next week. See also bug 7016-the launching should be
transparent.

Sean,
This is a Profile Manager bug but I cannot change component or assigned-does it
have to be reopened to do that?

Comment 5

[Grace Bush]

Unable to change component to Profile Manager, this is not Install Wizard bug.
Changing assignee, remarking invalid
Launch occurs after creating a profile now (build 1999061308)

Comment 6

[Grace Bush]

Unable to change component to Profile Manager, this is not Install Wizard bug.
Changing assignee, remarking invalid
Launch occurs after creating a profile now (build 1999061308)