Release 66.0.5 has now given network connection problems and deleted my new tab tools add-on tabs completely
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: stephenlangtonriley, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Discovered that another automatic update has corrupted the DNS table.
This update as also lost the new tab tools add-on tabs, I will now have to re-enter 99 tabs, not very happy after last weeek when 66.0.4 halted all add ons.
Actual results:
I had to reset the internet connection, and login again.
Blank new tab tools page.
Expected results:
ths shouldn't have happened, not after what occurred, and has compounded, last week. I have now had to do what I have with windows and switch off automatic updates as they are no longer reliable.
It came up during the win10 network problem connection fix that there was a DNS error, which it fixed and I could access the internet again. I could access the router and as far as it was concerned there were no issues, it was firefox not talking to it and that was the problem.
Unfortunately the New Tab Tools problem still requires me to rebuild all 99 entries and that is a very slow process, pity the tabs in firefox are so big or I would have used them.
I must say that 2, (3 if you include the DNS error, sorry I didn't take the exact details down as I know my way around to fix it if windows didn't), problems in consecutive releases is worrying as up until now I have had very minor issues with Firefox and updates, unlike windows 10 that has required a complete rebuild, 3 times, in the past, bit like rebuilding all the tabs now.
|
||
Comment 3•7 years ago
|
||
Hi Steve R, I want to double check with you if I understood the problem. After the update to FF release 66.0.5 you tabs where blank and you had to login again to the internet? Did you try after the update to restore your last session? Also, do you think you can reproduce the issue if you install a release version 66.0.4 and update it to 66.0.5?
I also give it a try on Windows 10 x64 with ff release 66.0.4 update it to release 66.0.5 and everything worked as expected.
Thanks but the update slipped under my radar, I was in the middle of a de-install and re-install of AVG, I had lost the stored password and that proved to be a complex operation. That process did complete successfully with no change on release levels, but in the meantime FF had done its bit automatically, trying to go back to recreate it when I was also trying to rebuild all the tabs for new tab tools wasn't something I was going to do, even though all the thumbnails were still stored.
I have learned, yet again, a valuable lesson in not permitting automatic updates to occur, I need to control whatever else may interrupt, unknown to me, what I am doing at the time. I am in no doubt that the AVG work was unrelated but it also means I cannot recreate identicle parameters for Firefox before it went wrong.
When I managed mainframes I had total control and could stop automatic jobs with ease, these days they run application programs independently so I must remember to switch the default to off.
|
|
||
Comment 5•7 years ago
|
||
Thanks for your updates, just to be sure that I understood correctly now you can't see the issue and everything works ok for you?
Well I corrected the network issue and am rebuilding all the tabs, so I can still see the results but cannot recreate out it as time and variables have moved on. I will mark this as completed.
|
|
||
Comment 7•7 years ago
|
||
Thanks for the updates, I will mark this as Resolved WFM. Please feel free to reopen it if you can still reproduce the issue.
Description
•