Option to completely exit Telegram when closing window (Instead of close to tray)

[loxoron218]

Is your feature request related to a problem?

Yes, on Linux, closing the Telegram desktop app currently minimizes it to the system tray instead of fully exiting the application. This behavior is fine in itself, but requires an additional manual step to close the app completely, which can be inconvenient for users who prefer to terminate the app immediately upon closing the window.

Describe the solution you'd like

An option in the settings menu to choose the behavior on window close:

1. Close to tray (current behavior)
2. Exit application (kill the app and remove it from running processes)

This setting would give users the flexibility to decide how Telegram behaves when the window is closed, catering to different usage preferences.

Describe alternatives you've considered

1. Manually closing from the tray: This works but is not user-friendly and adds unnecessary steps.
2. Use other Telegram Desktop forks: This doesn't really work, because it forces me to ether use applications which are not up to date (Kotatogram) or either have that functionality (64gram or materialgram)

Additional context

This feature exists in other applications with a tray icon (e.g., messaging clients like WhatsApp and media players) and would align with user expectations. The added setting would improve user experience, especially for those who prefer to conserve system resources or ensure the app is entirely terminated after use.

[ilya-fedin]

duplicate

[loxoron218]

Can you add the number of the issue for me to follow it?

[ilya-fedin]

Please use issue search

[loxoron218]

Found it 👍

[DPDmancul]

Please use issue search

It is better to link the issue: I used the search but I could find only issues where there is a comment saying the issue is duplicate, but cannot reach the original issue for this annoying bug ;)

[loxoron218]

Please use issue search

It is better to link the issue: I used the search but I could find only issues where there is a comment saying the issue is duplicate, but cannot reach the original issue for this annoying bug ;)

I guess this was the issue: #8941