unread notification count is wrong and won't go away

[dgobaud]

• [x] I have searched open and closed issues for duplicates
• [x] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

notification count is stuck on 2 should be 0

Steps to Reproduce

no idea

Actual Result:

unread notification count shows 2 - should be 0. this started last night on 2 different osx computers

Expected Result:

should be 0

Screenshots

Platform Info

Signal Version:

6.36.0 production (Apple silicon)

Operating System:

OSX 12.3 (21E230)

Linked Device Version:

iOS 6.46.1.0

Link to Debug Log

https://debuglogs.org/desktop/6.36.0/8489aa8d26d48d6a49926da43ff4d95911bfbfa1c8e05ae5bb8d47f47311ab2b.gz

iOS https://debuglogs.org/ios/6.46.1/5a91a2a441bcec47e396664348da11f3ca3f42785e50c26c1f0fe6a7d9b78435.zip

[trevor-signal]

Hi @dgobaud, if you type !unread in the search box, do you see any chats with unread messages?

[dgobaud]

that's cool didn't know about that! that shows it - someone did a safety number update but it didn't push the chats to the top so could only see them with !unread

[trevor-signal]

We'll review the desired behavior here; thanks for investigating!

[patricklucas]

I also ran into this, having apparently 1 unread message for the past month or so. Using @trevor-signal's trick I found the offending thread, a single message, also safety number-related, from March 2022! On all of my other devices this same thread was marked as read; I'm not sure why it spontaneously became unread on my desktop. (Windows 10 Pro 19045.3693, Signal Desktop 6.40.0 production)

[orborde]

Chiming in:

I've been piling up unreads due to this problem for ... years? and got up to like 70 mystery unreads. I finally figured out that it was safety number changes in long-silent group chats, came here to file a bug, and found this thread.

The !unread search trick has allowed me to find all the offending group chats and mark them read. Inbox zero, baby!

In case it's relevant: I'm on the Linux client, version 6.42.0

[travis-symbolscape]

Was this resolved? Have a persistent unread message that wont go away, only shows on desktop app. No matter what I do I can't get Signal to mark as read. ¯_(ツ)_/¯

[scottnonnenberg-signal]

What conversation(s) do you see when you type !unread in the search bar?

[Limfjorden]

I have a persistent unread message. It does not seem to be a security number update, as this is a person i communicate with daily. It only appears on the desktop app.

OS: macOS Ventura 13.6.6 Signal version: 7.13.0

[scottnonnenberg-signal]

@travis-symbolscape @Limfjorden Would you consider reaching out to support at [email protected]? We'd like to ask for more detailed information to try to track this down. Specifically I think we'd need a debug log not long after receiving a problematic message like this, the 'sent id' (the timestamp next to Sent on the detail screen), and a redacted screenshot of the message. Thanks!

[lumbric]

Having the same issue, I am also using the Linux Desktop client. It is a very old conversation and I think i have selected it when a new message (from a different person) arrived. Not sure if the bug is related to the arrival of the message, but I am pretty sure it is related to the selection of the conversation. The person where I see the unread message might have deleted their Signal account (msgs do not arrive on their side).

$ flatpak list|grep Signal                
Signal Desktop	org.signal.Signal	7.20.1	stable	user

This might be a duplicate of #3711.

[lumbric]

#3711 suggests that deleting the messages is a workaround (but the messages are gone on the Desktop client after that).

@scottnonnenberg-signal I have not reached out to [email protected] as many others in #3711 have done already.

Others have reported a deleted Signal account too, but one person also mentions the Windows client, so it might not only be a Linux issue.

Please let me know if you need more information.

I suggest to close this ticket as duplicate of #3711.