Closed Bug 493028 Opened 15 years ago Closed 6 years ago

Firefox fails to update when a Prism application is running

Categories

(Mozilla Labs :: Prism, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: beltzner, Unassigned)

References

Details

STR:

1. Run a Prism app (in my case it was Google Reader)
2. Run Firefox (using a nightly is best to ensure there's an update)
3. Check for Updates
4. Download and apply update

Expected:
Firefox restarts with an update applied.

Actual:
User gets an error message asking them to ensure no other copies of Firefox are running before trying to apply an update.

I worry about the confusion this will cause in Firefox users who don't think of their Prism app as being a "copy of Firefox".
Flags: blocking1.0?
This is the same issue as when a second user on a system is running Firefox or the same user runs multiple copies using -no-remote. There is currently nothing that facilitates this for Mozilla though the MSI update mechanism would likely not have this issue since it runs as a service using the local system account.

One possible solution I have been considering is creating a file named using the instance's PID on startup using a standard system location along with a way to identify the path to the currently running install location that could be checked by app update.
Once bug 314148 is fixed this will be fixed. Adding dependency since it isn't obvious that this bug is caused by the same underlying issue
Depends on: 314148
Note that the same problem occurs with Prism (since it has support for Application Update) if the user is running multiple Prism instances (a very common use case). I hope that any solution adopted for Firefox will also support other XULRunner-based applications that use Application Update.
No longer depends on: 314148
Updating dependencies since bug 525390 fixed bug 314148 without fixing this bug
Depends on: 466778
Robert, you have duped all bugs against bug 466778 which involve other files are blocked. So why you have added this one to the dependency list? We should be consistent and duping all of those bugs or using the dependency list.
Henrik, I have duped all bugs that require replacing files in use against bug 466778... I have duped all bugs that could have been fixed by bug 466778 but were specifically about preventing launching the app and other such scenarios to bug 525390. If you read / understand the root causes of the bugs in question this would make sense to you.
actually, duped or made dependent on.
In this specific instance for example, the text could be changed instead of going with bug 466778 to fix this bug
Flags: blocking1.0?
Prism isn't maintained anymore. Mass closing of the bugs.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.