Signal-desktop: messages marked as read in left conversation pane, but not in thread

[jeremymasters]

* [x] I have searched open and closed issues for duplicates

Bug Description

Messages in left conversation pane show as "read" (two filled-in check circles) but not in conversation thread

Steps to Reproduce

1. Shut Signal desktop off for the weekend
2. Signal with friends via Android device over said weekend
3. Start Signal desktop back up on Monday morning

Actual Result:

Messages load and Signal starts up fine. In the left hand pane, the last message from a contact shows as "read" (the two filled-in circles). The same message in the right-hand side thread view shows only one checked circle.

Expected Result:

sent/received/read status will be the same in the left-hand pane as in the thread view on the right

Screenshots

Left-hand pane:

Thread view

Platform Info

Signal Version:
1.24.1

Operating System:
Win 10
Linked Device Version:

4.38.3

Link to Debug Log

https://debuglogs.org/2357b02b371be93d695459044a442f4d5061e3dd2d34826dfa67eb32af85df9b

[jeremymasters]

It does the same even overnight.

[scottnonnenberg-signal]

Okay, to confirm: when desktop displays messages you sent to other people while Desktop was offline, it doesn't have the right number of checkmarks. What happens if you restart - does that message then show the right number of checks?

[jeremymasters]

I don't think a restart fixed it for me but I'll check again tomorrow

[guimspace]

Yes, it fixes the checkmark when I restart Signal desktop.

[jeremymasters]

I accidentally left it on last night, but some messages I have texted this morning from the phone did the same thing. When I scrolled up and then back down, it looks like it was fixed too.

[jeremymasters]

Same occurred again. Tested that scrolling does NOT resolve it. Restarting DOES solve it. Log from right after it happened and was resolved.

https://debuglogs.org/7c0708525c66bc10944251d16e489f2a8e9443863ab771ed0b73b87bc8f3014c

[scottnonnenberg-signal]

Same occurred again. Tested that scrolling does NOT resolve it. Restarting DOES solve it.

Cool. We have a solution ready for the next beta which should fix this.