Stuck on Updating... after changing profile picture.

[dillfrescott]

I'm just using the latest version for flatpak on ubuntu. But this also happened on windows version as well before.

If I'm using my phone and computer on the same profile, and I change my profile picture on one device they become out of sync and one device says updating... forever. and closing and opening the app doesn't fix it.

It also cannot receive messages.

[dillfrescott]

it seems like it will sometimes say connected again after a long while of waiting. It also could have been me sending a message to someone from the working device that jump started it. Either way its still a weird and annoying issue.

[nicodh]

I could reproduce this:

1. change profile image on one device
2. send a message from another device
3. the device with changed profile hangs "Connecting"

This happens with Adroid 1.54.3 and Desktop 1.54.2 (even on master with newest core 1.157.1)

After 1-2 minutes the connection works again, even without any other activity

[nicodh]

This is a complete log after changing the profile image and sending a message to SELF chat from the other device:

36.4s [D]core/event: 2 AccountsItemChanged { kind: 'AccountsItemChanged' }
36.4s [D]core/event: 2 ConfigSynced { key: 'selfavatar', kind: 'ConfigSynced' }
36.5s [i]core/event: 2 src/imap/idle.rs:77: "INBOX": Received interrupt, stopping IDLE.
36.5s [i]core/event: 2 src/imap/idle.rs:92: "INBOX": Idle wait was interrupted manually.
36.5s [D]core/event: 2 AccountsItemChanged { kind: 'AccountsItemChanged' }
36.6s [D]core/event: 2 ConfigSynced { key: 'displayname', kind: 'ConfigSynced' }
36.6s [D]core/event: 2 ConfigSynced { key: 'selfstatus', kind: 'ConfigSynced' }
36.6s [i]core/event: 2 src/ephemeral.rs:609: Ephemeral loop waiting for deletion in 24h 0m 0s or interrupt

account changed ( 60 seconds without log entries)

96.4s [w]core/event: 2 /build/source/src/scheduler.rs:577: fetch_idle: send_sync_msgs: IMAP APPEND to INBOX failed for Msg#34: io: timed out: timed out
96.4s [w]core/event: 2 src/scheduler.rs:418: Failed fetch_idle: fetch_move_delete: fetch_new_messages: prefetch: io: timed out: timed out
96.4s [i]core/event: 2 src/imap.rs:327: Connecting to IMAP server
96.4s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
96.4s [i]core/event: 2 src/imap.rs:342: IMAP trying to connect to nine.testrun.org:443:tls.
96.4s [i]core/event: 2 src/net/dns.rs:133: Using memory-cached DNS resolution for nine.testrun.org.
96.4s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 37.218.247.14.
96.4s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 116.202.233.236.
96.4s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 2a01:4f8:241:4ce8::2.
96.4s [i]core/event: 2 src/imap/client.rs:122: Attempting IMAP connection to nine.testrun.org (116.202.233.236:443).
96.5s [i]core/event: 2 src/imap.rs:379: Logging into IMAP server with LOGIN.
96.6s [i]core/event: 2 src/imap.rs:388: Enabling IMAP compression.
96.6s [D]core/event: 2 ImapConnected {
  kind: 'ImapConnected',
  msg: 'IMAP-LOGIN as xxx@nine.testrun.org'
}
96.6s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
96.6s [i]core/event: 2 src/imap.rs:411: Successfully logged into IMAP server
96.6s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }

connected to IMAP but message is not received ( another 60 seconds without log entries)

156.7s [w]core/event: 2 src/scheduler.rs:418: Failed fetch_idle: fetch_move_delete: fetch_new_messages: Failed to select folder "INBOX": IMAP other error: failed to select folder INBOX: IMAP other error: io: timed out
156.7s [i]core/event: 2 src/imap.rs:327: Connecting to IMAP server
156.7s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
156.7s [i]core/event: 2 src/imap.rs:342: IMAP trying to connect to nine.testrun.org:443:tls.
156.7s [i]core/event: 2 src/net/dns.rs:133: Using memory-cached DNS resolution for nine.testrun.org.
156.7s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 37.218.247.14.
156.7s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 116.202.233.236.
156.8s [i]core/event: 2 src/net/dns.rs:179: Resolved nine.testrun.org into 2a01:4f8:241:4ce8::2.
156.8s [i]core/event: 2 src/imap/client.rs:122: Attempting IMAP connection to nine.testrun.org (116.202.233.236:443).
156.8s [i]core/event: 2 src/imap.rs:379: Logging into IMAP server with LOGIN.
156.9s [i]core/event: 2 src/imap.rs:388: Enabling IMAP compression.
156.9s [D]core/event: 2 ImapConnected {
  kind: 'ImapConnected',
  msg: 'IMAP-LOGIN as xxx@nine.testrun.org'
}
156.9s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
156.9s [i]core/event: 2 src/imap.rs:411: Successfully logged into IMAP server
156.9s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
157s [i]core/event: 2 src/imap.rs:632: Not moving the message e18ec6d6-4c77-4181-a7ab-7cf53404d5dc@localhost that we have seen before.
157s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
157s [i]core/event: 2 src/imap.rs:1353: Starting a full FETCH of message set "15".
157s [i]core/event: 2 src/imap.rs:1464: Passing message UID 15 to receive_imf().
157s [i]core/event: 2 src/receive_imf.rs:226: Receiving message "2fb82fce-e2ba-4ab4-a0e5-566bc65bf5e3@localhost", seen=true...

now the message is fetched

[nicodh]

Also tested with core 1.157.1 (on Desktop master)

[nicodh]

I'm just using the latest version for flatpak on ubuntu. But this also happened on windows version as well before.

If I'm using my phone and computer on the same profile, and I change my profile picture on one device they become out of sync and one device says updating... forever. and closing and opening the app doesn't fix it.

It also cannot receive messages.

How long does this state last? I can reproduce it but after 1-2 minutes the connection is up again.

[dillfrescott]

It would appear the duration can vary? Although I havent tested it enough to be sure!

[dillfrescott]

I dont know if its a deltachat app issue or a chatmail server bug

[WofWca]

Could #6477 be related?

[dillfrescott]

I dont know. Sounds like it could be though!