Closed
Bug 797973
Opened 12 years ago
Closed 12 years ago
Applied updates should be removed from the Firefox installer
Categories
(Firefox :: Installer, defect)
Tracking
()
RESOLVED
FIXED
Firefox 18
People
(Reporter: jsmith, Assigned: bbondy)
References
Details
Attachments
(1 file)
1.08 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
Steps: 1. Install an old version of Firefox with the installer 2. Start updating firefox to the latest version 3. When the "apply update" phase is hit, close firefox 4. Uninstall firefox Expected: The updated folder shall be removed on uninstall. Actual: The updated folder is left behind on uninstall. This basically leaves behind an entire firefox installation on the machine in this folder. Note: If I then proceed to install firefox again, it will end up installing to the C:\Program Files (x86)\Nightly\updated folder, not C:\Program Files (x86)\Nightly. This isn't stub installer specific, but likely has do with silent update.
Comment 1•12 years ago
|
||
Should be as simple as a RmDir /r for that directory in the uninstaller.
Blocks: bgupdates
Assignee | ||
Comment 2•12 years ago
|
||
Assignee: nobody → netzen
Attachment #668232 -
Flags: review?(robert.bugzilla)
Updated•12 years ago
|
Attachment #668232 -
Flags: review?(robert.bugzilla) → review+
Assignee | ||
Updated•12 years ago
|
Summary: In the "apply update" phase of updating firefox, if I close firefox and uninstall it, the "updated" folder gets left behind on uninstall → Staged updates should be removed from the Firefox installer
Assignee | ||
Updated•12 years ago
|
Summary: Staged updates should be removed from the Firefox installer → Applied updates should be removed from the Firefox installer
Assignee | ||
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/e31bf74c3a40
Target Milestone: --- → Firefox 18
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e31bf74c3a40
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•