tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard
verified publisher icon telegramdesktop

Notifications being unmuted for some topics in forum chats, but not for real

Open RememberTheAir opened this issue 2 years ago • 8 comments

Steps to reproduce

This is something that has been happening since the introduction of topics, and apparently it only happens with public chats (with an username). I haven't figured out how to reproduce, but I can describe what happens.

Context: I have a folder which contains two forums-enabled public chats. These chats are muted, and no topic has ever been an exception, and they are also archived (my apps are set not to un-archive archived chats if I get mentioned there. It's probably not relevant but better to include this detail).
Sometimes I notice that the folder shows a colored unread counter, meaning there are messages from an unmuted chat:

screen_01

If I open the folder, there is no unmuted chat. But I know the issue is with this specific chat (or with another public forum, but today I've been able to catch the issue with this chat):

screen_02

In fact, if I open the topics list, this is what I see:

screen_03

None of the unmuted topics has ever been unmuted. In fact, if I right-click on a topic, tdesktop shows me the "unmute" option:

screen_04

If I open the chat's details, notifications are muted:

screen_05

Enabling and disabling again the chat's notifications toggle will make tdesktop remember that notifications are actually muted

Expected behaviour

Notifications stay muted

Actual behaviour

The behavior described above

Operating system

Windows 10

Version of Telegram Desktop

4.11.7

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

RememberTheAir avatar Nov 23 '23 08:11 RememberTheAir

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar May 22 '24 01:05 github-actions[bot]

unstale

RememberTheAir avatar May 23 '24 06:05 RememberTheAir

it's happening more and more frequently, apparently, but I still have no idea why and when it happens

RememberTheAir avatar Sep 05 '24 12:09 RememberTheAir

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Mar 05 '25 02:03 github-actions[bot]

still happens, very regularly

RememberTheAir avatar Mar 05 '25 08:03 RememberTheAir

Any update on this? Still happens very often

RememberTheAir avatar May 06 '25 07:05 RememberTheAir

I'll try to remember to take a look.

23rd avatar May 06 '25 21:05 23rd

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Nov 03 '25 02:11 github-actions[bot]