Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no item with selection of native notification display style (system notifications) #28820

Closed
voedev opened this issue Jan 2, 2025 · 8 comments
Labels

Comments

@voedev
Copy link

voedev commented Jan 2, 2025

Steps to reproduce

image

Expected behaviour

After upgrading to telegram 5.10, the option to select notification display style in the “Notifications and Sounds” section is gone. Previously I could choose between native notification style (system notifications) and telegram branded notifications (telegram style notifications).

Actual behaviour

Now I can't select a notification style and only get system notifications

Operating system

Fedora Linux 41 (KDE 6.2.4)

Version of Telegram Desktop

5.10

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

@voedev voedev added the bug label Jan 2, 2025
@ilya-fedin
Copy link
Contributor

Are you sure it's the update? Does it return if you downgrade?

@voedev
Copy link
Author

voedev commented Jan 3, 2025

Are you sure it's the update? Does it return if you downgrade?

I'm using the default wayland session. I tried running telegram in x11 compatibility mode, and there was one additional item in the settings. In the telegram.desktop file I have set the following compatibility mode:

Exec=env QT_QPA_PLATFORM=xcb /opt/telegram-desktop/Telegram -- %u

image
image

Strange why there are no similar settings with wayland session

@voedev
Copy link
Author

voedev commented Jan 3, 2025

Can someone please tell me how to use telegram style notifications on wayland?

@ilya-fedin
Copy link
Contributor

You can't, sorry. You have to use X11 in order to use them.

@Aokromes Aokromes closed this as completed Jan 3, 2025
@voedev
Copy link
Author

voedev commented Jan 3, 2025

You can't, sorry. You have to use X11 in order to use them.

Fedora KDE and GNOME have completely switched to wayland sessions and no longer provide even default packages to support X11 sessions. Wayland is being firmly implemented in Ubuntu as well and will even become a modern standard in LTS builds. It’s kind of weird to ignore this issue and just remove part of functionality from the application instead of adapting that functionality to a modern technology stack.

@ilya-fedin
Copy link
Contributor

It’s kind of weird to ignore this issue and just remove part of functionality from the application instead of adapting that functionality to a modern technology stack.

Wayland stakeholders ensured to prevent apps from implementing custom notifications while designing the protocol. And even in new protocol discussions they say things like "we need to make sure this protocol doesn't allow applications to implement custom notifications".

It's either Wayland or custom notifications, like you that or not.

@voedev
Copy link
Author

voedev commented Jan 4, 2025

It’s kind of weird to ignore this issue and just remove part of functionality from the application instead of adapting that functionality to a modern technology stack.

Wayland stakeholders ensured to prevent apps from implementing custom notifications while designing the protocol. And even in new protocol discussions they say things like "we need to make sure this protocol doesn't allow applications to implement custom notifications".

It's either Wayland or custom notifications, like you that or not.

For some reason, notifications are sometimes displayed incorrectly and graphic artifacts like this appear. I see this behavior only in telegram

image

@ilya-fedin
Copy link
Contributor

There's nothing tdesktop could about that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants