Problems with network connect?
Bug Summary
I've been running geary for months. Roughly once per week geary stops syncing with mailbox on my remote server. The server runs debian with dovecot. Standard installation, nothing special.
Seems as if geary loses connection to the server and then never tries (or maybe cannot) reconnect. In geary's UI the loading icon keeps spinning, but no new emails are received. And no mails that I create get sent.
I opened up the debug console and it keeps writing:
[deb] 15:09:21.0817 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:993 reachable...
[deb] 15:09:21.0818 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:465 reachable...
Even if I let it sit for days, it won't reconenct. If I close geary by clicking on close button and if I relaunch it, it still stays disconnected. I have to do a killall geary
. Only then it starts a new server connection.
Today I tried clicking on main folders, while it was in this disconnected state. Suddenly all but last 20 emails were deleted from geary. They remained on server but it was still strange..
So, from debug console, there's a lot of these:
[deb] 15:08:21.0840 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:993 reachable...
[deb] 15:08:21.0894 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:465 reachable...
[deb] 15:08:30.0837 GLib-Net:CLIENT[0x55faba4010d0]: starting to write 6 bytes to TLS connection
[deb] 15:08:30.0838 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_WRITE
[deb] 15:08:30.0838 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_WRITE succeeded
[deb] 15:08:30.0853 GLib-Net:CLIENT[0x55faba4010d0]: yielding operation OP_WRITE
[deb] 15:08:30.0854 GLib-Net:CLIENT[0x55faba4010d0]: successfully write 6 bytes to TLS connection
[deb] 15:08:30.0862 GLib-Net:CLIENT[0x55faba4010d0]: starting to read data from TLS connection
[deb] 15:08:30.0863 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_READ
[deb] 15:08:30.0863 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_READ succeeded
[deb] 15:08:30.0865 GLib-Net:CLIENT[0x55faba4010d0]: yielding operation OP_READ
[deb] 15:08:30.0865 GLib-Net:CLIENT[0x55faba4010d0]: successfully read 25 bytes from TLS connection
[deb] 15:08:30.0872 GLib-Net:CLIENT[0x55faba4010d0]: starting to read data from TLS connection
[deb] 15:08:30.0872 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_READ
[deb] 15:08:30.0872 GLib-Net:CLIENT[0x55faba4010d0]: claiming operation OP_READ succeeded
[deb] 15:08:30.0873 GLib-Net:CLIENT[0x55faba4010d0]: yielding operation OP_READ
....
[deb] 15:09:08.0822 GLib-Net:CLIENT[0x55faba400ec0]: reading data from TLS connection has failed: WOULD_BLOCK
[deb] 15:09:21.0817 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:993 reachable...
[deb] 15:09:21.0818 geary:util-connectivity-manager.vala:109: Checking if xxxx.myserver.xxx:465 reachable...
Your installation
To obtain installation information, copy it from Geary's Problem Report dialog if shown (or else open the Geary Inspector by typing Shift + Alt + I) by selecting System, and clicking the Copy button, then pasting here.
- Geary version: 3.36.3.1
- Installation method: Flathub
- Desktop environment: GNOME
- Operating system and version: Ubuntu 20.04
- Email provider: dovecot
Steps to reproduce
It's hard to see when geary loses connection but I'm sure lot's of times I wasn't around so I cannot give reproduction steps. Seems that it just happens..