40581 - automigration and first time migration from 4.x profile gives error

Status: VERIFIED FIXED

(SeaMonkey :: Preferences, defect, P3)

Description

[Grace Bush]

Steps to reproduce:
1. Install build 2000-05-25-09M16 - on machines with one and more than one 4.x 
profile.
2. On machine with more than one 4.x profile, choose one and start netscape6
3. Choose to migrate/convert the profile

Actual result:  Error message
Netscape - JS Preference Warning
An error occurred reading the startup configuration file. Please contact your 
administrator.

Expected result: launch with migrated profile

Note* second launch succeeds

Comment 1

[selmer (gone)]

Bhuvan, please take a look.

Comment 2

[racham]

Looks like some garbage is getting written into prefs file during/after the 
migration process...will look into it.

Comment 3

[racham]

surprising...i don't see it on ymchine with today's build (sweetlou). Will come 
to your desk for further info..

Comment 4

[racham]

This is reproducible after clean install. Commercial build issue only.

Presence of component.reg is making the difference here. All I need to do to 
reproduce this delete compoenent.reg and try to run the app i.e., create a need 
for autoreg. [Note : Grace mentioned in her report that it runs ok on second 
time...and that is beacuse of already existing component.reg]. It happens all 
the time with fresh installs as autoreg happens all the time in this path.

Looks like this is related to the implementation that needs to read netscape.cfg 
in prefs code. I think after the migration process is over....profile manager 
calls ReadUserPrefs 
(http://lxr.mozilla.org/seamonkey/source/profile/src/nsProfile.cpp#380). Prefs 
service at this point tries to read netscape.cfg file and is failing. I will 
work with neeti to track this down further. A note here is that reading of 
netscape.cfg requires services of Netscape PSM. Need to see if this link has 
anything to do with the problem. 

This is windows only issue.

I already spoke to dan veditz, dp and neeti about this. Adding Seth to the 
discussion.

Comment 5

[neeti]

This does not happen, when I enable the feature for debug builds.(after deleting  
the component.reg file).

Sean, when I install the optimized builds from sweetlou, the progress dialog 
says that it is installing psm.exe, but I cannot find it anywhere. Where is psm 
being installed in the optimized builds?

Neeti

Comment 6

[Daniel Veditz [:dveditz]]

Generally under c:\program files\common files\netscape shared\security, 
although there is (or was) some code to try to install it over an existing one 
if the old one happened to be installed elsewhere. In that case you'd be on 
your own trying to find it.

You can do a windows file find for "psm.exe"

Comment 7

[racham]

Reassigning this bug to neeti. This error is occuring due to failure in reading 
of netscape.cfg in the absence of component.reg. I will continue working with 
neeti on this. Adding leaf in the cc list (for any possible build issues).

Comment 8

[Gagan]

prefs to mcafee

Comment 9

[Gagan]

prefs to mcafee

Comment 10

[Gagan]

argh... didn't work the last time. pardon the spam. ->mcafee

Comment 11

[scalkins]

On Win NT 4.0, with todays builds, I see the message 
"error with config , see admin" message if I do any of the following.
1)Install seamonkey to any directory other than the default ..i.e. I tried 
D:\seamonkey. (Default was c:\Program Files\Netscape)
2)Install and create a new profile with a name different from the default i:e: I 
tried "52608M16" for a new profile name. (Default was "New User")
If I do any of the above, Seamonkey fails to load browser, mail(with -mail 
parameter) aim (with -aim parameter) etc. if I install using any of above 
methods.
I saw this occur on two different NT 4.0 boxes in QA (Mine and Fenella's)

Additional Note: 
Fenella used the default install directory and a profile migrated with a 
previous NS 6 build, and that worked OK.

Comment 12

[Daniel Veditz [:dveditz]]

Why the heck should this be mcafee? It broke when neeti added netscape.cfg 
processing to the build, she should be the one to turn it off (fixing this 
bug, no doubt reopening the netscape.cfg feature bug) until it can be make to 
work correctly.

Comment 13

[don]

I agree, sending the bug to neeti ...

Comment 14

[neeti]

Turned off netscape.cfg feature, bug 5132.

Comment 15

[neeti]

*** Bug 40762 has been marked as a duplicate of this bug. ***

Comment 16

[Grace Bush]

this is working on both automigration and migration of >1 4.x profile
build 2000052920