Tdesktop: "Do Not Disturb" is ignored on OSX

Created on 8 Mar 2017  Â·  21Comments  Â·  Source: telegramdesktop/tdesktop

Steps to reproduce

  1. Turn on "Do Not Disturb"
  2. Receive a message via Telegram Desktop

Expected behaviour

The entire app should remain silent.

Actual behaviour

The notification does not appear, but the "notification sound" does.

Configuration

OS Version: MacOS Sierra 10.12.3

Telegram Desktop Version: v1.0.14

Used theme: Default

bug macOS

Most helpful comment

OSX 10.14.4 / Tdesktop 1.6.7 still not fixed, I had to close it to watch my GoT episode ... 😄

All 21 comments

@FabianMeul Thank you for your report. This will be fixed in the next version.

Hi, @john-preston!
Reopen this issue.
I have the same problem right know on macOS Sierra 10.12.6 with Telegram Desktop 1.1.19
I hear notification sound and icon bounces.
Please fix it 😰

@FabianMeul , @john-preston come on people, re-open issue pls. v1.1.22 - the same problem 😑

I can't re-open the issue, but I have noticed this behavior as well...

@FabianMeul ok, thanks. do you have the same problem right now?

Confirmed -- even with DnD enabled icon still "flashes" (bounces), and sound is played.

MacOS High Sierra 10.13 -- the problem still persists.

Confirmed that this is still an issue in MacOS High Sierra 10.13.1.

Sierra 10.12.6 same problem

MacOS High Sierra 10.13.4
Please, fix that, I can't sleep :(

OSX 10.14.4 / Tdesktop 1.6.7 still not fixed, I had to close it to watch my GoT episode ... 😄

Same for WhatsApp desktop on MacOs 10.14.6

Telegram Desktop 1.9.21 still ignores DnD on macOS 10.15.4
Come on people, it's been three years …

I bet "next release" has never happened

Thanks @cpwc !!!

to be fair this still happens for telegram voice calls, they appear in the middle of the screen with do not disturb turned on

@rdednl you might want to open a new ticket on this with the various information required. Like the version of telegram you are using.

Still reproduce on 2.1.10 version.

try 2.1.12

@zagorulkinde That's strange, someone did fix the key in code. 2.1.12 should not really differ from 2.1.10 in this way. It should work after 2.1.7.

@zagorulkinde the fix went into v2.1.7 but no macOS build. There's a macOS release v2.1.8 and it works well for me thru v2.1.12. Could you create a new issue with the required information like your OS etc so I can take a look and try to reproduce it?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

LeonTheOriginal picture LeonTheOriginal  Â·  3Comments

Justinzobel picture Justinzobel  Â·  3Comments

Yanrishatum picture Yanrishatum  Â·  3Comments

hosseinab picture hosseinab  Â·  3Comments

qwitriy picture qwitriy  Â·  3Comments