>I'll try the try build from comment 18, and perhaps the beta version from comment 15. Just to be clear, the try version in **comment 19** (comment 18 is busted) and the beta mentioned in comment 15 address completely different problems. The beta only may affect possible folder corruption and doesn't affect the network problems that will hopefully be fixed by comment 19 try build. So I would recommend trying the "try" build first (comment 19) and see if it helps. If it does, I can incorporate the network fix into the current beta and make a try build of the patched beta and you can then run that. Hope this makes sense!
Bug 1901338 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>I'll try the try build from comment 18, and perhaps the beta version from comment 15. Just to be clear, the try version in **comment 19** (comment 18 is broken) and the beta mentioned in comment 15 address completely different problems. The beta only may affect possible folder corruption and doesn't affect the network problems that will hopefully be fixed by comment 19 try build. So I would recommend trying the "try" build first (comment 19) and see if it helps. If it does, I can incorporate the network fix into the current beta and make a try build of the patched beta and you can then run that. Hope this makes sense!
>I'll try the try build from comment 18, and perhaps the beta version from comment 15. Just to be clear, the try version in **comment 19** (comment 18 is broken) and the beta mentioned in comment 15 address completely different problems. The beta only may affects possible folder corruption and doesn't affect the network problems that will hopefully be fixed by comment 19 try build. So I would recommend running the "try" build first (comment 19) and see if it helps. If it does, I can incorporate the network fix into the current beta and make a try build of the patched beta and you can then run that. Hope this makes sense!
>I'll try the try build from comment 18, and perhaps the beta version from comment 15. Just to be clear, the try version in **comment 19** (comment 18 is broken) and the beta mentioned in comment 15 address completely different problems. The beta only may affect possible folder corruption and doesn't affect the network problems that will hopefully be fixed by comment 19 try build. So I would recommend running the "try" build first (comment 19) and see if it helps. If it does, I can incorporate the network fix into the current beta and make a try build of the patched beta and you can then run that. Hope this makes sense!