Closed Bug 28879 Opened 25 years ago Closed 25 years ago

Migrated profiles remigrate each launch.

Categories

(MailNews Core :: Profile Migration, defect, P3)

x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: laurel, Assigned: racham)

Details

(Keywords: platform-parity, Whiteboard: [PDT+] Fix in hand)

Attachments

(1 file)

Using 2000-02-22-11m14 mozilla build on linux rh6.0
Haven't yet migrated using current builds on mac, NT

Every time I launch, my migrated profile remigrates without having removed files
or registry.

1.  You have a 4.x profile
2.  Remove mozregistry and any lingering 5.0 user files.
3.  Launch mozilla -profilemanager
4.  Select the 4.x profile to migrate, click Start Mozilla button. Wait for
migration to complete. Go to mail, login and open the migrated profile's inbox.
5.  Quit.
6.  Launch mozilla -profilemanager. Select the same profile you just migrated
and click Start Mozilla button in profilemanager.

Result:  migration progress dialog appears, profile goes through remigration
process (or appears to).

Expected:  should only see migration dialog once.
Severity: normal → major
Doesn't happen using NT.
Having mac problems...

marking pp in keywords field
Keywords: pp
I'm seeing this too.

this is a bug for racham.
Assignee: sspitzer → racham
Keywords: beta1
Target Milestone: M14
see also bug 27861
I just switched to the feb22 commercial build, removed files/registry and tried
again.  Now I'm getting behavior as grace described in bug # 27861, where the
migrated profile won't relaunch.
Need to check why is this happening on Linux & Mac. Don't see it on Windows.
Status: NEW → ASSIGNED
[PDT+]
Whiteboard: [PDT+]
I have fix for this. Tested  it on Linux. Need to check on other platforms. 
Whiteboard: [PDT+] → [PDT+] Fix in hand
adding shaver.  

he's dying for the fix.
Registry entries were missing at the end of the session. That is causing this 
behavior to show up. Dan Veditz looking if there are any nsRegistry issues that 
are causing this. My fix was kind of work around for the problem. Creating an 
attachment (diffs) that solved problem for me. But we are now looking to see if 
we can attack this from registry side. Adding dan to cc list.

*** This bug has been marked as a duplicate of 28243 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verified
Status: RESOLVED → VERIFIED
How was this fixed without the change to prevent xpinstall from linking in an 
extra copy of libreg on Unix?
Originally I had a patch, that used to build the lost registry tree. But that 
was not the right way to go as we discovered there is problem with linkage on 
Linux. With the fix you put in for Makefile yesterday solves this problem as the 
profile information remains intact. So, this is marked as dup of 28243. Marked 
fixed as a dup.
reopening per dveditz
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
marking FIXED per dveditz
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
build 2000022808
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: