Closed Bug 1374835 Opened 7 years ago Closed 7 years ago

Daily will not restart after update

Categories

(Thunderbird :: Untriaged, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bobt07, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170620030208 Steps to reproduce: Installed update daily will not restart This happened to both daily and nightly after the latest update to windows 10 Actual results: Both nightly and daily should start normally after being updated YF (Yang) Updated • 2 days ago Component: Untriaged ? Application Update Product: Firefox ? Toolkit Robert Strong [:rstrong] (use needinfo to contact me) Comment 1 • a day ago Please open about:config, find app.update.staging.enabled, and provide the value in a comment in this bug. Thanks! Flags: needinfo?(bobt07@westnet.com.au) Bob (Reporter) Comment 2 • a day ago The value is set at false Flags: needinfo?(bobt07@westnet.com.au) Robert Strong [:rstrong] (use needinfo to contact me) Comment 3 • a day ago Thank you. There is a good chance this is a duplicate of bug 1370576 which also fixes bug 1368600. After updating Firefox to the next nightly please comment in this bug as to whether it is still happening. Thanks! Bob (Reporter) Comment 4 • a day ago Just had nightly inform me of an update clicked the download button While this was happening daily informed me that update was available Waited until I thought nightly update had down loaded closed nightly Started nightly it did not load Clicked the update button on daily then the restart button daily did not load Started task manager neither nightly or daily apps loaded Checked background processes Found a daily and a daily update process Ended daily process and daily immediately loaded Found 4 nightly process ended the 4 then clicked to start nightly it loaded correctly Checked help about nightly found there was an update 19 June available Clicked to download then clicked to restart it did not load Checked task manager found 5 background process Ended 2 and nightly immediately loaded Checked task manager nightly and daily had apps loaded Nightly had 6 background process and daily had none Checked update status both up to date Both programs working OK Robert Strong [:rstrong] (use needinfo to contact me) Comment 5 • a day ago Thunderbird hasn't made the change that Firefox has (a Thunderbird dev has been informed) so lets keep this to being about Firefox. Firefox has a 63 second timeout before it kills itself when exiting so an update can be applied. During the next update please wait a couple of minutes and hopefully that will provide more details to go on. Thanks! Bob (Reporter) Comment 6 • 23 hours ago Have just checked task manager again Did the above steps at approx 0300 and it is now 0620 WST Australia and nightly has 10 background process will wait as requested next update Robert Strong [:rstrong] (use needinfo to contact me) Comment 7 • 23 hours ago The number of processes when running Firefox has nothing to do with updating. This is how Firefox works now that it has support for multiple processes. That info *might* be of value when it doesn't startup correctly but this info definitely doesn't provide anything of value when running normally. Friday June 21 05:20 Booted machine this morning tried to start daily did not start Checked task manager found 1 background process daily but using no resources other than memory Ended task Started Daily it started normally Later checked found an update was available Downloaded then clicked restart Waited 3 minutes daily did not restart Checked background processes 1 daily using only memory ended task Daily started normally Checked about daily update had not been installed Clicked to update then clicked to restart Daily did not start 1 background process using only memory Waited 5 minutes then ended task Started daily started normally checked about daily still not updated Daily informed me update available downloaded it and clicked restart Daily did not start 1 background process using only memory (2.5MB) Ended task restarted daily it did not update Expected results: Daily should restart with the update installed
The date Friday June 21 should be Wednesday Version of last update 56.0a1 (2017-06-19) Daily informed me update available Clicked update then restart daily did not start Background processes 1 daily and 1 daily update I ended daily the the daily update shut down and daily started Checked version and it had been updated to 56.0a1 (2017-06-20) Thursday June 22 0511 clicked update button 0513 clicked restart button 1 daily and 1 daily update process open daily did not start the upate process closed itself after about 1 minute 0515 opened daily did not start now 2 processes opened 0517 ended processes 0519 opened daily started normally it did not update 0521 clicked update buton 0523 clicked the restart button 2 daily process opened then 1 closed and then a update process opened updater closed but daily did not start 1 daily process open 05267 closed process opened daily started normally did not update
Friday 23 June Check daily version 56.0a1 (2017-06-20) Click update daily button Click restart daily button 2 daily background processes open 1 process closes the other remains open daily software update process opens remains open for about a minute then this closes but daily does not start Start daily another daily process opens but daily does not start 2 daily processes open Start daily Same result as above now 3 processes open End 1st process 2 processes open Start daily a 3rd process opens daily starts normally 1 process closes Check version 56.0a1 (2017-06-20) daily did not update
Bob, is this still hpapening?
Flags: needinfo?(bobt07)
Whiteboard: [closeme 2017-12-15]
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
See Also: → 1374097, 1375242
Whiteboard: [closeme 2017-12-15]
Sorry I have only just seen this Yes it is resolved
Flags: needinfo?(bobt07)
Resolution: INCOMPLETE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.