Open
Bug 1176439
Opened 9 years ago
Updated 2 years ago
Persistent "Restart Nightly to Update" when I'm already on latest Nightly. Service needs improvement to avoid missing registry key for install location
Categories
(Toolkit :: Application Update, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox41 | --- | affected |
People
(Reporter: vladan, Unassigned)
Details
Attachments
(5 files)
This behaviour is reproducible on this profile. It might be a symptom of a worse issue.
Which updater logs should I attach?
I'm on Windows 7 64-bit, 32-bit Nightly from June 19th, no extensions, logged in as a user with admin privileges.
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(robert.strong.bugs)
Reporter | ||
Comment 1•9 years ago
|
||
I should mention that restarting doesn't clear that button
Comment 2•9 years ago
|
||
In about:config change the app.update.log pref to true and the devtools.errorconsole.enabled pref to true. Open the about error console under tools -> web developer and click clear. Open the about window and check the error console for messages that start with aus. Paste these message into a file and attach it to this bug.
Flags: needinfo?(robert.strong.bugs)
Reporter | ||
Comment 4•9 years ago
|
||
The update.status file referenced in the error console has contents "succeeded", the chrome.manifest file is not at the indicated path, it's actually in c:\Program Files (x86)\nightly2\browser\chrome.manifest
Flags: needinfo?(vdjeric)
Reporter | ||
Comment 5•9 years ago
|
||
Additional messages were posted to the error console a few minutes after I attached error_console.txt
Comment 6•9 years ago
|
||
I noticed the install directory is Nightly2. Did you renamed the install directory recently?
Comment 7•9 years ago
|
||
Also, is this by chance an install from a zip build?
Reporter | ||
Comment 8•9 years ago
|
||
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #6)
> I noticed the install directory is Nightly2. Did you renamed the install
> directory recently?
No, I needed two installations of Nightly at one point, so I installed Nightly a second time in Nightly2 (a long time ago)
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #7)
> Also, is this by chance an install from a zip build?
Nope, I installed it using a Nightly installer a long time ago.
Comment 9•9 years ago
|
||
Is the other install of Nightly have working updates?
Reporter | ||
Comment 10•9 years ago
|
||
(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #9)
> Is the other install of Nightly have working updates?
I think I know what's going on now. The nightlies in Nightly1 and Nightly2 directories were both running. Nightly1 was out-of-date and Nightly2 was up-to-date. The Help->About dialog in Nightly2 was indicating that it needed to be restarted even though it was up to date, because Nightly1 was out of date.
Once I updated Nightly1 and restarted it, Nightly2 no longer displayed the incorrect "Restart to update" message and instead showed "Nightly is being updated by another instance".
Comment 11•9 years ago
|
||
Could you attach the registry entries under
HKCU\Software\Mozilla\Firefox\TaskBarIDs\
and
HKLM\Software\Mozilla\Firefox\TaskBarIDs\
Reporter | ||
Comment 12•9 years ago
|
||
You'll notice I've had a LOT of different Firefox versions installed, this is my development & testing machine :)
Reporter | ||
Comment 13•9 years ago
|
||
Comment 14•9 years ago
|
||
The registry key for this install location used by the service is missing. When time permits I'll look into making that code more robust.
Updated•6 years ago
|
Summary: Persistent "Restart Nightly to Update" when I'm already on latest Nightly → Persistent "Restart Nightly to Update" when I'm already on latest Nightly. Service needs improvement to avoid missing registry key for install location
Updated•5 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Updated•5 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•