Closed
Bug 1553532
Opened 5 years ago
Closed 5 years ago
[Stub installer] Updating Firefox without using Profile manager doesn't remove the previously installed add-ons
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1555117
Tracking | Status | |
---|---|---|
firefox68 | --- | affected |
People
(Reporter: asoncutean, Unassigned)
Details
[Affected versions]:
- 68.0b3
[Affected platforms]:
- Windows 10
- Windows 8.1
[Steps to reproduce]:
Preconditions:
- Make sure option “Use the selected profile without asking at startup” is checked inside the Profile manager.
- Download and install an old Firefox version
- Once Firefox opens, install several add-ons
- Close Firefox
- Install the latest version of Firefox stub installer
Note: Make sure the Paveover prompt appears and the option “Restore default settings and remove old add-ons for optimal performance” is checked before clicking on the Update button
[Expected result]:
- Firefox automatically opens using the same profile and the add-on installed previously are removed.
[Actual result]:
- Firefox in not opened, once the progress bar is completely filled, the prompt disappears and nothing happens (Note that here is an inconsistent behavior, if the option “Restore default settings and remove old add-ons for optimal performance” is unchecked Firefox opens instantly once the installation is finished).
- If I open Firefox manually, I have the same profile used previously, the add-on are still present, but the current Firefox version is the latest one as expected.
[Regression range]:
- I will provide information asap.
[Additional Notes]:
- When the Profile Manager (“Use the selected profile without asking at startup” is unchecked) is used, this issue is not reproducible. The moment the latest stub installer version installation finishes, the Profile Manager is triggered, and no add-on remains when opening the previously used profile.
Comment 1•5 years ago
|
||
I need to investigate this a little; since the paveover prompt is appearing, I think it's likely that the installer has done its job, so this might be an issue with how the profile refresh is starting itself up.
Updated•5 years ago
|
Priority: -- → P3
Updated•5 years ago
|
Has Regression Range: --- → no
Reporter | ||
Comment 2•5 years ago
|
||
Unfortunately I cannot determine if this issue is a regression. Firefox builds get automatically updated to the latest available version for the desired channel when using the paveover prompt.
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•