Closed Bug 357626 Opened 18 years ago Closed 18 years ago

Minefield installed on the directory of other Mozilla Products.

Categories

(Firefox :: Installer, defect)

x86
Windows Vista
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: fullmetaljacket.xp+bugmail, Assigned: robert.strong.bugs)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061019 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061019 Minefield/3.0a1 when installing minefield using STANDARD setup type on a machine with other mozilla product already installed (in my case thunderbird 3.1a) it will be installed on that directory (C:\Program Files\Mozilla Thunderbird\) instead on the default directory (C:\Program Files\Minefield\). Reproducible: Always Steps to Reproduce: 1. install other mozilla product (e.g. thunderbird) 2. install minefield using STANDARD setup option Actual Results: minefield was installed on C:\Program Files\Mozilla Thunderbird\ Expected Results: minefield should be installed on C:\Program Files\Mozilla Thunderbird\
OS: Other → Windows Vista
Summary: Minefield will be installed on the directory of other Mozilla Products. → Minefield installed on the directory of other Mozilla Products.
Severity: normal → major
Version: unspecified → Trunk
this was confirmed on moz forum
Status: UNCONFIRMED → NEW
Ever confirmed: true
erratum: Expected Results: minefield should be installed on C:\Program Files\Minefield\
Assignee: nobody → robert.bugzilla
Flags: blocking1.8.1.1?
Flags: blocking-firefox2?
Is this vista-only, or does it also happen with XP? Is this trunk-only, or does it also happen on branch builds?
Firefox 2 installs into the correct location, so I'm not sure why this would block us. I think we need to fix this before the next release that will use this installer, if I understand the problem correctly. That would be either Fx 2.0.0.1 or Tb 2, depending on schedules.
Flags: blocking-firefox2? → blocking-firefox2-
Prolly deserves a relnote. Rob, can you tell me if this is an accurate description of the problem: "If you have installed a Thunderbird or Firefox Alpha driver, the new Windows installer may pick the wrong default folder for installing Firefox 2. Please use a "Custom" install and make sure the right folder is selected when installing."
Keywords: relnote
(In reply to comment #5) > "If you have installed a Thunderbird or Firefox Alpha driver, the new Windows > installer may pick the wrong default folder for installing Firefox 2. Please > use a "Custom" install and make sure the right folder is selected when > installing." Great. Just great. There's now a bugzilla record of my IBM-brain jumping into my main consciousness and taking control. I KNEW that happened from time to time. Let's try that again, but in English: "If you have installed an alpha or beta version of Firefox 2 or Thunderbird 2, the new Windows installer may select the wrong default folder when installing Firefox 2. Please use a "Custom" install and make sure the right folder is selected when installing."
Apparently this is trunk only .. removing relnote.
Keywords: relnote
STANDARD and CUSTOM setup routine on todays build will both install minefield to "C:\Program Files\Mozilla Thunderbird\". so i had to uninstall first thunderbird before installing minefield. ----------- Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061026 Minefield/3.0a1 ID:2006102604 [cairo]
i filed another minefield installer bug: [url]https://bugzilla.mozilla.org/show_bug.cgi?id=358116[/url]
Does this affect Minefield only, or all versions of the current installer? Will Thunderbird 2 install over Firefox 2? If it's just Minefield this doesn't need to block 1.8.1.1, please set the blocking flag back to ? in that case (or leave a note if you can't).
Flags: blocking1.8.1.1? → blocking1.8.1.1+
Minefield only
Flags: blocking1.8.1.1+
Flags: blocking-firefox3?
This will be fixed by the patch in bug 354005
Depends on: 354005
No longer blocks: 358116
(In reply to comment #12) > This will be fixed by the patch in bug 354005 > fixed indeed. thank you :)
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Flags: blocking-firefox3?
You need to log in before you can comment on or make changes to this bug.