Linux Telegram app freezes on message #8768

Alex-Blade · 2020-10-07T00:16:34Z

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

ilya-fedin · 2020-10-07T00:38:37Z

Is this reproducible with with X11 or only with Wayland?

krims0n32 · 2020-10-07T10:18:37Z

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.

ilya-fedin · 2020-10-07T11:23:29Z

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

GustavoKatel · 2020-10-07T13:00:31Z

I have the same issue :(

Telegram 2.3.2 (manjaro repo)
Manjaro + awesomewm + x11

cyberpunkrocker-zero · 2020-10-07T13:25:57Z

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.

kierun · 2020-10-07T13:36:16Z

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

ilya-fedin · 2020-10-07T13:38:19Z

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

cyberpunkrocker-zero · 2020-10-07T13:46:30Z

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...

ilya-fedin · 2020-10-07T13:48:29Z

A Reddit-effect?

Can you give a link?

kierun · 2020-10-07T13:48:48Z

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 · 2020-10-07T13:49:36Z

Here is the reddit post.

GustavoKatel · 2020-10-07T13:49:45Z

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

ilya-fedin · 2020-10-07T13:51:07Z

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

GustavoKatel · 2020-10-07T13:52:26Z

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?

ilya-fedin · 2020-10-07T13:53:15Z

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 · 2020-10-07T14:44:26Z

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

read previous messages

fuzxi · 2020-10-08T01:56:09Z

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.

ilya-fedin · 2020-10-08T04:02:44Z

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

krims0n32 · 2020-10-08T07:27:44Z

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?

ilya-fedin · 2020-10-08T07:43:29Z

Has something changed in the content of the notification Telegram sends

dbus library that Telegram uses to send a notification

Alex-Blade · 2020-10-08T15:00:17Z

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 · 2020-10-08T15:09:58Z

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

ilya-fedin · 2020-10-09T05:13:04Z

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

krims0n32 · 2020-10-10T20:32:02Z

This seems to fix the issue for me!

Alex-Blade · 2020-10-10T21:31:16Z

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

ilya-fedin · 2020-10-11T06:21:53Z

Since opinions were divided, more testers are needed.

Tried all three versions

It is enough to try only just "Telegram"

cyberpunkrocker-zero · 2020-10-12T05:38:59Z

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

ilya-fedin · 2020-10-12T08:09:16Z

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

ilya-fedin · 2020-10-12T08:31:45Z

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

Alex-Blade · 2020-10-12T23:20:30Z

@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

ilya-fedin · 2020-10-13T10:56:11Z

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?

Alex-Blade · 2020-10-13T13:05:38Z

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

ilya-fedin · 2020-10-13T14:34:45Z

Could the issue be closed then?

cyberpunkrocker-zero · 2020-10-13T14:37:56Z

Seems like it

github-actions · 2021-03-04T15:02:09Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Aokromes added the waiting for answer label Oct 7, 2020

Aokromes closed this as completed Oct 13, 2020

vincentbernat mentioned this issue Jan 14, 2021

Hang/freeze of Firefox (from v85 on), Chromium and Electron based apps awesomeWM/awesome#3241

Closed

github-actions bot locked as resolved and limited conversation to collaborators Mar 4, 2021

Linux Telegram app freezes on message #8768

Linux Telegram app freezes on message #8768

Comments

Alex-Blade commented Oct 7, 2020

Steps to reproduce

Expected behaviour

Actual behaviour

Configuration

ilya-fedin commented Oct 7, 2020

krims0n32 commented Oct 7, 2020

ilya-fedin commented Oct 7, 2020

GustavoKatel commented Oct 7, 2020

cyberpunkrocker-zero commented Oct 7, 2020

kierun commented Oct 7, 2020

ilya-fedin commented Oct 7, 2020 • edited

cyberpunkrocker-zero commented Oct 7, 2020

ilya-fedin commented Oct 7, 2020

kierun commented Oct 7, 2020 • edited

kierun commented Oct 7, 2020

GustavoKatel commented Oct 7, 2020

ilya-fedin commented Oct 7, 2020 • edited

GustavoKatel commented Oct 7, 2020

ilya-fedin commented Oct 7, 2020 • edited

ilya-fedin commented Oct 7, 2020

fuzxi commented Oct 8, 2020

ilya-fedin commented Oct 8, 2020

krims0n32 commented Oct 8, 2020

ilya-fedin commented Oct 8, 2020

Alex-Blade commented Oct 8, 2020 • edited

Alex-Blade commented Oct 8, 2020

ilya-fedin commented Oct 9, 2020

krims0n32 commented Oct 10, 2020

Alex-Blade commented Oct 10, 2020 • edited

ilya-fedin commented Oct 11, 2020 • edited

cyberpunkrocker-zero commented Oct 12, 2020

ilya-fedin commented Oct 12, 2020

ilya-fedin commented Oct 12, 2020

Alex-Blade commented Oct 12, 2020

ilya-fedin commented Oct 13, 2020 • edited

Alex-Blade commented Oct 13, 2020

ilya-fedin commented Oct 13, 2020

cyberpunkrocker-zero commented Oct 13, 2020

github-actions bot commented Mar 4, 2021

ilya-fedin commented Oct 7, 2020 •

edited

kierun commented Oct 7, 2020 •

edited

ilya-fedin commented Oct 7, 2020 •

edited

ilya-fedin commented Oct 7, 2020 •

edited

Alex-Blade commented Oct 8, 2020 •

edited

Alex-Blade commented Oct 10, 2020 •

edited

ilya-fedin commented Oct 11, 2020 •

edited

ilya-fedin commented Oct 13, 2020 •

edited