Tdesktop: Linux Telegram app freezes on message

Created on 7 Oct 2020 · 34Comments · Source: telegramdesktop/tdesktop

Steps to reproduce

Install Telegram Desktop on Linux (tested on [Fedora/Pop/Manjaro] + Gnome 3)
Turn on notifications sounds (Turned on by default)
Enjoy frozen application whenever new message comes (freezes till the notifications appears)

Expected behaviour

Telegram should continue working

Actual behaviour

The app freezes (even if the message is already in chat list) and continues working when the notification appears

Configuration

Operating system: Any Linux distro with latest Gnome 3
Audio solution: Creative Sound Blaster Z, internal audio

Version of Telegram Desktop: 2.4.2

Installation source (Linux Only) - the official website + GitHub releases + flatpak (tested all)

Used theme: Dark mode

waiting for answer

Source

Alex-Blade

👍3

All 34 comments

Is this reproducible with with X11 or only with Wayland?

ilya-fedin on 7 Oct 2020

I have the same issue, Archlinux using Awesome as window manager (X11). This started happening in Telegram desktop 2.3+. 2.2 works fine.

It only happens when using native notifications and for me it also happens when notification sounds are turned off.

krims0n32 on 7 Oct 2020

👍1

I can't reproduce, native notifications are working just fine for me

ilya-fedin on 7 Oct 2020

I have the same issue :(

Telegram 2.3.2 (manjaro repo)
Manjaro + awesomewm + x11

GustavoKatel on 7 Oct 2020

The same issue here: Awesome WM on Arch Linux / x11, currently telegram-desktop- 2.4.0-1. The issue started after upgrading to 2.3.x
When I get a message, the red number appears to systray icon, the sound notification sounds, and then telegram freezes completely for 10-20 seconds, after telegram is revived the actual notification appears.

cyberpunkrocker-zero on 7 Oct 2020

👍1

Same issue:

√ ; rpm -qa | rg telegram-desktop
telegram-desktop-2.3.2-1.fc32.x86_64
√ ; uname -a
Linux nightwatch.neverness.org 5.8.12-200.fc32.x86_64 #1 SMP Mon Sep 28 12:17:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
√ ; awesome --version
awesome v4.3 (Too long)
 • Compiled against Lua 5.3.5 (running with Lua 5.3)
 • D-Bus support: ✔
 • execinfo support: ✔
 • xcb-randr version: 1.6
 • LGI version: 0.9.2
√ ; rpm -qa | rg X11
libX11-devel-1.6.12-1.fc32.x86_64
libX11-xcb-1.6.12-1.fc32.x86_64
libX11-common-1.6.12-1.fc32.noarch
libX11-1.6.12-1.fc32.x86_64

kierun on 7 Oct 2020

It's been a long time since 2.3.x, why there are a lot of people here now?

ilya-fedin on 7 Oct 2020

A Reddit-effect? Me, I was about to report this over a week ago, but never did. Now people are asking about it in Reddit, so...

cyberpunkrocker-zero on 7 Oct 2020

👍1

A Reddit-effect?

Can you give a link?

ilya-fedin on 7 Oct 2020

It's been a long time since 2.3.x, why there are a lot of people here now?

Because that's what is in the package manager on Fedora and I saw a reddit post on it in /r/awesomewm…

kierun on 7 Oct 2020

Here is the reddit post.

kierun on 7 Oct 2020

It's been a long time since 2.3.x, why there are a lot of people here now?

Because that's what is in the package manager on Fedora and I saw a reddit post on it in /r/awesome…

same for manjaro

GustavoKatel on 7 Oct 2020

Does awesome has its own notification daemon? Is this reproducible with any other notification daemon?

ilya-fedin on 7 Oct 2020

Does awesome has its own notification daemon? Is this reproducible with any other notification daemon?

yes, awesome has its own notification daemon, but the OP mentioned they're using gnome 3?

GustavoKatel on 7 Oct 2020

👍1

but the OP mentioned they're using gnome 3?

Ok, is this reproducible with any other notification daemon rather than awesome and gnome?

ilya-fedin on 7 Oct 2020

I am afraid that the bug is still appearing on 2.4.2 with native notifications

read previous messages

ilya-fedin on 7 Oct 2020

but the OP mentioned they're using gnome 3?

Ok, is this reproducible with any other notification daemon rather than awesome and gnome?

I can reproduce this using mako on sway.

fuzxi on 8 Oct 2020

Oh, that's bad, we still don't know what cause this. And I can't reproduce, I don't experience any freezes.

ilya-fedin on 8 Oct 2020

I have tested using Dunst (https://dunst-project.org/) instead of Awesome's notification manager and that does not give me any freezes. So it seems to be a combination of Telegram and notification daemon. I'm not sure what Gnome uses for notifications but apparently it is not an Awesome specific issue.

Has something changed in the content of the notification Telegram sends, perhaps the profile picture or something that borks out on some notification daemons?

krims0n32 on 8 Oct 2020

Has something changed in the content of the notification Telegram sends

dbus library that Telegram uses to send a notification

ilya-fedin on 8 Oct 2020

Is this reproducible with with X11 or only with Wayland?

@Aokromes
Right now I'm on:
Fedora 32 (Workstation Edition) with GNOME Shell 3.36.6, X11. I'm not sure about Wayland though

Alex-Blade on 8 Oct 2020

How do I check what notification manager do I use? Didn't change anything, so I guess it's default Gnome thing

Alex-Blade on 8 Oct 2020

Tried to use a more low-leverl. Can anyone check if this fixes the issue?
https://github.com/ilya-fedin/tdesktop/actions/runs/296715634

ilya-fedin on 9 Oct 2020

This seems to fix the issue for me!

krims0n32 on 10 Oct 2020

QCoreApplication::postEvent: Unexpected null receiver
Tried all three versions, didn't help. Got that thing during last attempt, though idk if it's smth to do with the fact that I force closed Telegram

Alex-Blade on 10 Oct 2020

Since opinions were divided, more testers are needed.

Tried all three versions

It is enough to try only just "Telegram"

ilya-fedin on 11 Oct 2020

Just got the patched version compiled and tested; so far, the patch seems to work as intended, no more freezes or any other oddities, desktop notifications are on.
Patch applied to 2.4.3 on Arch Linux / Awesome wm / x11

cyberpunkrocker-zero on 12 Oct 2020

Maybe @Alex-Blade's issue is another after all? :thinking:

ilya-fedin on 12 Oct 2020

@Alex-Blade can you check if downgrading to 2.2 helps for you like for others?

ilya-fedin on 12 Oct 2020

@ilya-fedin, that's extremely weird, I've been using Telegram Flathub version for the whole day and only now understood that there have been no freezes... All the versions you've provided are also working correctly. Will continue to observe and investigate, hope the issue is resolved

Alex-Blade on 13 Oct 2020

that's extremely weird, I've been using Telegram Flathub version for the whole day and only now understood that there have been no freezes...

Maybe the issue was on GNOME side and you updated the system?

ilya-fedin on 13 Oct 2020

Maybe it was on hardware optimization side at all, I'm actually not really satisfied with stability of Ryzen + NVMe combo on Linux (needed to solve problems for both separately and then combine). Didn't notice any updates, but possible, I regretfully don't have a log of updates

Alex-Blade on 13 Oct 2020

Could the issue be closed then?

ilya-fedin on 13 Oct 2020

Seems like it

cyberpunkrocker-zero on 13 Oct 2020

Was this page helpful?

0 / 5 - 0 ratings