Closed Bug 1607017 Opened 5 years ago Closed 5 years ago

Nightly 72.0a1 to 73.0a1 update doorhanger loop despite fresh download

Categories

(Firefox :: Untriaged, defect)

73 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: davross, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

Been using Nightly for some years now, and managed to resolve most issues (minor or significant) through switching to a new profile and/or downloading a fresh copy of Nightly. I've missed almost 2 weeks of updates due to the holiday period

Firefox channel: Nightly
Firefox version: 73.0a1
Firefox Build ID: 20200102094341
Environment: Arch Linux Hardened (5.3.15.a-1-hardened)
Desktop: Gnome 3.34.2

Menu >> (Top status message: "Download a fresh copy of Nightly")

  1. Navigate to https://www.mozilla.org/firefox/channel/desktop/
  2. Select Download for the Nightly version
  3. Expand download local tar.bz2 file using Archive Manager [I perform this inside the "Downloads" directory]
  4. Delete legacy "Firefox" directory [in my case this is held inside my Documents directory]
  5. Rename fresh Nightly "Firefox" directory to "firefox-nightly"
  6. Move directory from Downloads to Documents
  7. Desktop file and hidden directories like ".mozilla" remain as before

Actual results:

If I simply restart Nightly, it continues to show this version needs updating. If I navigate to a new webpage the Restart splashpage drop in to encourage you to immediately restart.

Performing either method, using my everyday profile, I cannot seem to break out of this loop. About:Nightly, in both instances, shows the currently legacy version. About:Support shows 20200102094341 as the Build ID.

When using a fresh profile there is no warnings, and the browser appears to run the expected fresh version (73.0a1). About:Support shows Build ID as 20200103202240.

Expected results:

This update process should run near automagically. I suspect the profile has somehow corrupted, so will now:

About:Support >> Refresh Nightly

This refresh has resolved this issue. Leaving as unresolved to have some eyes on what I perceive as a bug in the matrix. Please feel free to close or escalate at will. Oh and a very Happy New Year to you and those dear to you!

Hi David,

Thanks for the well-wishing :) and thanks for taking the time of opening a detailed bug. We will mark it as WFM since the newest version has seemingly fixed this issue.

Have a nice and happy year, regards, Flor.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.