Tdesktop: Native Notification option gone if Telegram autostarts

[null-von-sushi]

Steps to reproduce

1. Autostart Telegram
2. Receive a message

Actual behaviour

Telegram draws it's own notification instead of using the native notification system.
Also, the native notification toggle in the Telegram settings is gone.

Expected behaviour

Telegram should continue to use native notifications if that option was previously set.
The option should not disappear either.

Workaround

Fully quit and restart telegram manually.

Configuration

Operating system: Antergos Linux (Arch Based)

Desktop Environment: KDE Plasma 5.14.5

Version of Telegram Desktop:
1.5.4

Used theme:
On Telegram?
Arc-2 Bright

[Aokromes]

this bug is still valid?

[null-von-sushi]

I think so yes. It's nearly a Year since this bug was posted, so I am not 100% sure what my system configuration at the time was.
I am fairly confident it's a race condition at login between telegram starting and a notification daemon starting though.

If I kill latte-dock (which is responsible for drawing notifications for me, I think), restart telegram it will use it's own style. Even if latte-dock is started later on, telegram will use it's own notifications. I worked around it by having telegram start with sleep 5 && telegram-desktop for now (though that's obviously not a real fix).

It is worth noting that (assuming latte-dock is running again) closing telegram, and relaunching it does re-enable native notifications without the user having to manually enable it again, which is nice. So I guess it's either the default now, or it remembers our preferences even if they become 'invalid' for a certain period of time.

[Storm-Engineer]

Interestingly this bug only started happening for me at the end of January this year, even though it was reported here over a year ago.

See the trail of tickets leading me here for additional information: #7130 #7308

[chaptergy]

Unfortunately I'm having the same issue. Is there a plan when merge request #7321 will be included in the official release? Or which version will contain this fix?

[Aokromes]

Unfortunately I'm having the same issue. Is there a plan when merge request #7321 will be included in the official release? Or which version will contain this fix?

it was merge on 6 march.

[chaptergy]

So it was merged to master right away as well and was included in v1.9.20? Because I'm on version 2.1 and unfortunately still experiencing this issue.

[Storm-Engineer]

Issue still present, BTW... looks like this will never get fixed. :/