Closed Bug 1152958 Opened 9 years ago Closed 9 years ago

Updater does not work on Mac OSX

Categories

(Firefox :: Installer, defect)

Product:
Firefox
Component:
Installer
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 394984

People

(Reporter: ajones, Unassigned)

Details

A new install of Firefox does not update on Mac OSX by default. The problem seems to be related to Firefox requiring admin permission to modify. The updater runs by fails silently without updating.
Are you switching between users (bug 394984)?
The about dialog does not display most of the errors that can occur per the UX design which is likely why you aren't seeing errors. After there have been 10 sequential background check errors you will be notified.

Paste the following in the error console to invoke the app update ui that does display errors and report back in this bug what the error was.

const Cc = Components.classes; const Ci = Components.interfaces;
Components.classes["@mozilla.org/updates/update-prompt;1"].createInstance(Components.interfaces.nsIUpdatePrompt).checkForUpdates();
Flags: needinfo?(ajones)
Apparently Component.classes is undefined.
Flags: needinfo?(ajones)
That sounds like it wasn't done in the error console. Type about:config in the url bar. Click the warning button to display the contents. Type errorconsole in the search box. Double click the entry so the value is true. Open the error console under tools -> web developer -> error console. Copy / paste the code in comment #2 all in one line.
Flags: needinfo?(ajones)
After finding the error console and pasting the above, it tried to update and complained about the privileges being incorrect to write to the file. The problem for ordinary users is that we don't usefully tell them what to do. We just continuously nag for updates. There is no point in even downloading the file if we don't have the right privileges to overwrite it.
Flags: needinfo?(ajones)
Can you provide the actual message so I can verify what is going on. Better still, toggle the app.update.log preference in about:config and each step of the process will be printed to the error console. If you could paste those into this bug we can verify exactly what is going on.

Note: this sounds like it would be fixed by bug 394984 which has repeatedly been deprioritized in favor of other work.
We'll also need the error console log entries since if we don't have write access we don't perform the download so if it is then this is definitely an unusual situation.
This is the same as the bug I opened a long time ago on this matter:

bug 1065820.
Can you provide the information asked for in comment #6?
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #6)
> Can you provide the actual message so I can verify what is going on. Better
> still, toggle the app.update.log preference in about:config and each step of
> the process will be printed to the error console. If you could paste those
> into this bug we can verify exactly what is going on.
> 
> Note: this sounds like it would be fixed by bug 394984 which has repeatedly
> been deprioritized in favor of other work.

I removed nightly and reinstalled it so I'm no longer able to reproduce the issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.