Installer needs to detect running apps using GRE

RESOLVED INCOMPLETE

Status

--
major
RESOLVED INCOMPLETE
16 years ago
9 years ago

People

(Reporter: ssu0262, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Right now, there isn't a way for the installer to detect an app that has GRE
loaded in memory.  If there is such an app and we're trying to upgrade GRE, this
will force the installer to reboot the system at the end because there will be
files in use.

Here's what needs to happen:
 * Mozilla installer needs to look in the GRE's windows registry key to
determine which apps could potentially be running (and holding GRE in memory)
 * The installer then needs to check to see if any of the apps are either
mozilla or netscape.  If they are, then offer to quit for them.
 * If the apps are not either mozilla or netscape, then show dialog with list of
found apps requiring to be shutdown by the user.
 * Also offer "Skip" or "Ignore" button.  Installer should allow a way to opt
out of this check.
 * This check needs to happen after all the files have been successfully
downloaded, not before.  If one of these other apps happen to offer internet
connectivity, the installer will not be able to download required files if the
app shutsdown.

The whole purpose of this is to prevent the user from requiring to reboot their
system.

Comment 1

16 years ago
I am not sure there is a requirement when installing a new client of the GRE,
but lets not forget the case when we want to uninstall a GRE - there would be a
requirement to know if the GRE is running when uninstalling, right?
(Reporter)

Comment 2

16 years ago
I'm not sure there is because from what I can tell on what the requirements are
for a shared GRE to be uninstalled is that the app that requires GRE should no
longer require it.  Meaning that it should have already been uninstalled before
GRE is uninstalled.

However, I'll keep the uninstall scenario in mind just in case I'm missing
something.
Status: NEW → ASSIGNED
Installer triage team: nsbeta1+/adt2
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt2]
(Reporter)

Updated

16 years ago
Target Milestone: --- → mozilla1.4beta

Comment 4

16 years ago
Installer triage team: nsbeta1-
Keywords: nsbeta1+ → nsbeta1-
Whiteboard: [adt2]
Product: Browser → Seamonkey

Updated

13 years ago
QA Contact: bugzilla → general
Assignee: ssu0262 → nobody
Status: ASSIGNED → NEW
Target Milestone: mozilla1.4beta → ---

Comment 5

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

9 years ago
old XPFE installer is dead.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.