Closed Bug 266221 Opened 20 years ago Closed 20 years ago

Migration dialog not coming up despite the absence of a profile

Categories

(Firefox :: Migration, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: marcia, Assigned: bugs)

Details

Seen using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Gecko/20041026 Firefox/1.0RC1

STR:
   1. Before installation delete the Firefox folder in the Application Data dir 
   2. Launch Firefox
   3. At the Migration dialog, select cancel or Do not import anything

Migration dialog does not come up at all on the WIndows XP machine I was testing on.

Asa said he sees this on Windows 2K as well.
This worked in the previous round of builds today so it regressed from either
Ben's or jst's changes this afternoon.
Flags: blocking-aviary1.0+
This is showing up on Linux too, I trashed my profile and did not get the
migration dialog. I did get the extension update dialog.
OS: Windows XP → All
this doesn't seem to be a problem for me on linux fc2 using 2004102618-0.11:

a. start with mozilla or opera profile -> able to migrate with either mozilla or
opera data, new firefox profile starts fine.

b. start with mozilla or opera profile -> able to use "do not import anything"
option, new firefox profile starts fine.

c. start with no profile from any browser (mozilla or opera) -> no migration
wizard appears and new firefox profile starts fine.

there are no existing firefox profiles in the above tests. or perhaps I missing
something?
OS: All → Windows XP
This works for me on Windows XP sp1; firefox branch build 2004-10-26-17-0.11

Note:  I was doing upgrade testing earlier.  So I made certain all instances of
any Firefox/Phoenix profile were removed from the application data folder. Doing
so allowed the migration dialog to appear before Firefox launched, as expected.
Is this really an issue with the build or with the test instruction?  The steps
to reproduce say to delete the Firefox folder from the Application Data folder.
 This is not the location where Firefox creates the profile and has not been
since at least 0.9 time.  So, the reason that the migration dialog did not
launch could well be that there was a profile at the new location, which is in
"Applications Data\Mozilla\Firefox".
Yes, the directory in this case was deleted from the Applications
Data\Mozilla\Firefox - last night I rushed to get the bug in and just did a fast
cut and paste from our test case.

(In reply to comment #5)
> Is this really an issue with the build or with the test instruction?  The steps
> to reproduce say to delete the Firefox folder from the Application Data folder.
>  This is not the location where Firefox creates the profile and has not been
> since at least 0.9 time.  So, the reason that the migration dialog did not
> launch could well be that there was a profile at the new location, which is in
> "Applications Data\Mozilla\Firefox".
Very strange. This works for me with the late night build form 10/26 that still
had the 0.11 versioning under WIN/XP SP2.  Did you check to make sure there was
not a profile in both Applications Data foders?  That is both the one for the
specific username you were logged in as as well as in the "All Users"
application Data folder  (although if there was one in the All Users folder that
would bring up the how did it get their issue).
Asa and I retested this morning on the same Linux machine, and we *were" able to
get the Migration dialog. Sorry for the confusion on this platform.

(In reply to comment #2)
> This is showing up on Linux too, I trashed my profile and did not get the
> migration dialog. I did get the extension update dialog.
This seems to be resolved with the latest builds. We should try to get to the
heart of this problem but the bandaid gets us an RC.
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
Just so we have it memorialized in the bug, I downloaded last evening's Mac
build (2004-10-26-22-0.11 - we did not have it at the time I filed this bug
since it was being respun). Migration worked fine in this build.
According to Comment #9 and #10 this bug seems resolved. Can this be confirmed?
marking w4m.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
wfm on all platforms today
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.