If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

My profile settings were not migrated...

VERIFIED WORKSFORME

Status

Core Graveyard
Profile: Migration
P3
normal
VERIFIED WORKSFORME
17 years ago
a year ago

People

(Reporter: tao, Assigned: dbragg)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
build: nscp 09-26-06-m18 installer build.

None of my browser/mailnews settings were migrated...
(Reporter)

Comment 1

17 years ago
To make it clear,
I was referring to selection of an existing profile (migrated from 4.x before
PR2) from ProfileManager.
(Assignee)

Comment 2

17 years ago
Tao, Did you see the little migration progress window?  Were you given the 
dialog that tells you this is an old profile and will be migrated?  Do you see 
the profile directory on your Windows drive?
(Reporter)

Comment 3

17 years ago
> Tao, Did you see the little migration progress window?
NO

>Were you given the
dialog that tells you this is an old profile and will be migrated?
NO
>  Do you see
> the profile directory on your Windows drive?

What does this mean?

Comment 4

17 years ago
from the description it sounds like this profile was migrated before (PR2?) and 
is just being used again- has it been used all along and stopped showing setting 
s today?
is it the only 4.x profile?
profile settings have been changed and I would suggest removing registries and 
users50 
I will add attachment as to new locations for these files

Comment 5

17 years ago
Created attachment 15539 [details]
Profile changes
(Reporter)

Comment 6

17 years ago
It just stopped working today (w the new build).

Does N6 share the same profile w/ 4.x or it copy/migrate from 4.x and use the
new one thereafter?
(Assignee)

Comment 7

17 years ago
It copies and then uses the copy thereafter.  It never refers back to the 
original 4.x profile.

Comment 8

17 years ago
tao, see bug 52181- check your 4.x profile for any .rdf files and if they exist, 
please remove and try migrating again
(Reporter)

Comment 9

17 years ago
correct typo in the summary field.
Summary: My profile settings were not imgrated... → My profile settings were not migrated...
(Assignee)

Comment 10

17 years ago
Tao, I'm going through my bugs and I'd like to close this as WORKSFORME or
whatever.  I assume there was some configuration problem that you no longer
have. Is that true?
(Reporter)

Comment 11

17 years ago
yes, let's get it out of radar until the problem resurfaces.
(Assignee)

Comment 12

17 years ago
Per discussion with Grace, marking WORKSFORME.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME

Updated

17 years ago
Keywords: vtrunk

Comment 13

17 years ago
Migration has been working in MN6 builds - specifically 2000110801
narking vtrunk

Comment 14

17 years ago
trunk builds 11/17
Status: RESOLVED → VERIFIED
Keywords: vtrunk
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.