Telegram Desktop crashes when locking up the screen on Gnome 46, Fedora 40

Impasse52 commented 2 months ago

Steps to reproduce

Start up Telegram Desktop
Lock up the screen
Unlock the screen
Verify that Telegram Desktop crashes

Expected behaviour

Telegram Desktop should stay up and running with no crashes.

Actual behaviour

Telegram Desktop crashes and causes a core dump. The following is found when running journalctl -xe:

Jul 12 07:49:39 fedora systemd-coredump[5085]: [🡕] Process 4646 (telegram-deskto) of user 1000 dumped core.

                                               Stack trace of thread 2:
                                               #0  0x00007f68119f91d4 n/a (/app/lib/libQt6Gui.so.6.7.2 + 0x1f91d4)
                                               #1  0x00007f68109cc734 n/a (/app/lib/libQt6Core.so.6.7.2 + 0x1cc734)
                                               #2  0x00007f68109cc734 n/a (/app/lib/libQt6Core.so.6.7.2 + 0x1cc734)
                                               #3  0x00007f68119bd134 n/a (/app/lib/libQt6Gui.so.6.7.2 + 0x1bd134)
                                               #4  0x00007f680b0e9bc3 n/a (/app/lib/libQt6WaylandClient.so.6.7.2 + 0x80bc3)
                                               #5  0x00007f680b10fe03 n/a (/app/lib/libQt6WaylandClient.so.6.7.2 + 0xa6e03)
                                               #6  0x00007f680e1a0056 n/a (/usr/lib/x86_64-linux-gnu/libffi.so.8.1.4 + 0x9056)
                                               #7  0x0000000000000000 n/a (n/a + 0x0)
                                               ELF object binary architecture: AMD x86-64
░░ Subject: Process 4646 (telegram-deskto) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░ 
░░ Process 4646 (telegram-deskto) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.

Operating system

Fedora 40

Version of Telegram Desktop

5.2.3

Installation source

Flatpak

Crash ID

No response

Logs

No response

ilya-fedin commented 2 months ago

flatpak install --no-auto-pin org.freedesktop.Sdk{,.Debug}//23.08 org.telegram.desktop.Debug
flatpak-coredumpctl org.telegram.desktop

Impasse52 commented 2 months ago

I'm struggling to understand how to use this so let me know if this is correct. I executed your command, I ran Telegram Desktop and I waited for crashes (and respective core dumps) to show up in the flatpak-coredumpctl command.

This is what I got:

^[[B[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/app/bin/telegram-desktop'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fb43cdf91d4 in QPlatformScreen::screen() const () from /app/lib/libQt6Gui.so.6
[Current thread is 1 (Thread 0x7fb4366db2c0 (LWP 2))]

ilya-fedin commented 2 months ago

Your output sadly lacks the backtrace and thus of no help:(

Impasse52 commented 2 months ago

Your output sadly lacks the backtrace and thus of no help:(

Is it supposed to show up? I feel like I'm not understanding your directions so feel free to let me know :/

ilya-fedin commented 2 months ago

I'm not sure either, I don't remember how it's supposed to work... Previous reporters just posted what's needed after I gave them these commands. Maybe it would be easier for you to switch to the static binary with built-in crash reporter? You just have to enable beta version installation in settings, reproduce the crash and you will get a crash id on next launch (don't forget to actually send crash report) which you can post here.

leo-puh commented 1 month ago

Hi, I also suffer from Telegram Desktop crashes, but with Fedora 39 and Gnome 44. Shall I post a crashdump here or open a new issue? I use a normal binary, not a flatpak nor snap package.

github-actions[bot] commented 1 month ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

iammark2 commented 1 month ago

Same issue for me, same verson of Telegram Desktop, 5.2.3

Etherdrake commented 1 month ago

Issue just started for me as well.

AnthraX1 commented 2 weeks ago

same problem.

Impasse52 commented 1 week ago

Problem still persists, and I noticed that it also occurs on other desktop environments such as Plasma 6.