Closed Bug 235186 Opened 21 years ago Closed 17 years ago

Profile migration for NS4.x does not check whether the NS4.x profile is still in use

Categories

(Core Graveyard :: Profile: Migration, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: roland.mainz, Unassigned)

Details

(Keywords: dataloss)

Profile migration for NS4.x does not check whether the NS4.x profile is still in use. The profile migration code should check whether there is a "lock" file (~/.netscape/lock ; which indicates that NS4.x is still running) or not before trying the migration. Steps to reproduce: 1. Download a mozilla tar.gz via NS4.x 2. Unpack Mozilla % gunzip -c http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6/mozilla-i686-pc-linux-gnu-1.6.tar.gz | tar -xvf - 3. Run Mozilla (with no profile) % mv ~/.mozilla ~/.mozilla_disabled % ./mozilla/mozilla 4. Select profile migration Result: Profile migration starts and converts the data from the NS4.x profile, regardless whether NS4.x is still running or not (this may result in a data loss when NS4.x mail is still active and fetching emails while the migration is running (my "nsmail" folder has 1.4GB so migration will need some time... and while that is running NS4.x may likely fetch the one or other email (every 15mins in my case))). Expected result: Profile migration should check for the "lock" file and abort the profile migration if NS4.x is still running.
darin/bryner: Who can look at the problem ?
with the recent work done to add profile migration features to firefox, this bug might interest Ben.
Marking bugs related to migrating 4.7 profiles as wontfix, as this is no longer supported. If this bug isn't specific to 4.7, please reopen it.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.