Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

Thunderbird 78.6.0 hangs up downloading email when first opened

  • 2 përgjigje
  • 1 e ka hasur këtë problem
  • 12 parje
  • Përgjigjja më e re nga eberger5

eberger5
eberger5
more options

I have recently installed 78.6.0 on my mail laptop and also a Surface GO. Both are running win10, but the Surface GO is updated with the 20H2 and the main laptop is not. It is current except for the 20H2 feature update. Both TBirds are configured the same, linked to my AOL/Compuserve account and 3 Comcast emails accounts. The server for AOL is imap.aol.com and for comast is imap.comcast.net. I have the following Add Ons on both PCs: EditEmailSubject MX, FileLink Provider for Box, and PopmailListRecipients. The install on my mail laptop is fine. The one on the GO has the issue described below.

If the GO sleeps too long, then TBird (which I always leave open), will hang on trying to connect to servers and download emails. No error message. But the timer just spins, the green progress bar does not show up and nothing happens. If I close TBird and restart it all is fine and it continues to work well until the PC nexts sleeps for too long. If the GO just sleeps for short while then that is ok.

I am not using hibernate on the GO, just sleep. It doesn't seem to matter if it is sleeping so long that I have to push the power button to start up, or even just a long sleep that allows me to start up by just hitting the space bar.

I do not believe that I had this problem with 78.5 and certainly didn't have it with the last version of 68. But I the 20H2 update may have been done after my update from 78.5 to 78.6. I'm not sure.

Any thoughts on what may be the issue?

I have recently installed 78.6.0 on my mail laptop and also a Surface GO. Both are running win10, but the Surface GO is updated with the 20H2 and the main laptop is not. It is current except for the 20H2 feature update. Both TBirds are configured the same, linked to my AOL/Compuserve account and 3 Comcast emails accounts. The server for AOL is imap.aol.com and for comast is imap.comcast.net. I have the following Add Ons on both PCs: EditEmailSubject MX, FileLink Provider for Box, and PopmailListRecipients. The install on my mail laptop is fine. The one on the GO has the issue described below. If the GO sleeps too long, then TBird (which I always leave open), will hang on trying to connect to servers and download emails. No error message. But the timer just spins, the green progress bar does not show up and nothing happens. If I close TBird and restart it all is fine and it continues to work well until the PC nexts sleeps for too long. If the GO just sleeps for short while then that is ok. I am not using hibernate on the GO, just sleep. It doesn't seem to matter if it is sleeping so long that I have to push the power button to start up, or even just a long sleep that allows me to start up by just hitting the space bar. I do not believe that I had this problem with 78.5 and certainly didn't have it with the last version of 68. But I the 20H2 update may have been done after my update from 78.5 to 78.6. I'm not sure. Any thoughts on what may be the issue?

Krejt Përgjigjet (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

try setting the connection uses in options to "no proxy". It has been known to work on Macs that exhibited similar issues on resume from sleep.

eberger5
eberger5 I zoti i pyetjes
more options

Matt, Thank you but it didn't help. With "no proxy" selected I no longer get the spinning timer spinning forever, but instead just get nothing. It is as though I never clicked "get messages," but again, as soon as I close TBird and reopen it pulls in the mail just fine. Is this a known bug? Shall I post this in Bugzilla or do you? Elliott