65586 - Profile names ending in a space cannot be migrated

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Profile: BackEnd, defect)

Description

[Conrad Carlen (not reading bugmail)]

This was discovered while debugging bug 62073. From that bug:
Finally had a chance to debug using the Netscape Registry you sent. Found the
problem - The first profile name in that registry ends with a space. That name
is added as-is to the new registry. Turns out that a registry key cannot end in
a space or will cause an error. That's what happens. When migrating, we error
out on the first entry because of the space, nothing else gets migrated, the
profile list ends up empty, and all hell breaks loose.

Comment 1

[[e-mail]]

What a coincidence -- I was sitting on the Mac today, and was trying out a Mac 

build for the first time in a long time, and noticed it hadn't been fixed.

Great to see you've found the problem.



Looking into the issue of there being space in the profile names -- there's no 

spaces in the folder names, which were created from the profile names, hm, but 

I'll see. Have to restart NS to check it out.

Comment 2

[[e-mail]]

The profile that seems to have caused the problem did not end in a space, but was 
called "Torbjörn Sundlöf (stadshypotek)" -- probably it got confused with the 
parenthesis'. I renamed that profile to "Torbjörn Sundlöf-stadshypotek", removed 
Mozilla settings (Component Reg., Documents, Mozilla Registry) and now it finds 
that profile, but none of the others with sane names. Hrm.

Comment 3

[[e-mail]]

I renamed the profiles to

"Ann-Sofi"
"Petter"
"Stadshypotek"
"Torbjörn"

...and now Mozilla sees them all, and is able to migrate.

Of course, I shouldn't have to do this.

Comment 4

[Conrad Carlen (not reading bugmail)]

No, you shouldn't. That's why I filed the bug ;-)