telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.32k stars 5.23k forks source link

Random crashed under KDE (Fedora & openSUSE) #28426

Closed ezhan closed 1 month ago

ezhan commented 1 month ago

Steps to reproduce

Using Linux (Fedora 40, openSUSE Tumbleweed, both with KDE) time to time for a half a year. And always see Telegram just closing and having to restart it.

  1. Use Telegram
  2. At some moment it just closes
  3. No crash dialog whatsoever
  4. Have to restart manually

I do not see this setting in Telegram's settings: "You have to enable beta versions installation in Settings -> Advanced for the reporter to appear."

Expected behaviour

It continue working as usual

Actual behaviour

At some moment it just closes

Operating system

Linux

Version of Telegram Desktop

5.5.5

Installation source

Flatpak

Crash ID

No response

Logs

No response

ilya-fedin commented 1 month ago

The reporting options are available only when using static binary. I'm not exactly sure how you can get the required infromation (crash trace) with flatpak so you may need to contact someone who is familiar with flatpak to get it. Those commands should probably help:

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

But not each bug reporter provided the backtrace after this suggestion for some reason.

ezhan commented 1 month ago

Installed the given flatpak. Run the flatpak-coredumpctl org.telegram.desktop

Got:

$ flatpak-coredumpctl org.telegram.desktop

The program 'flatpak-coredumpctl' can be found in the following package:
  * flatpak-devel [ path: /usr/bin/flatpak-coredumpctl, repository: repo-oss ]

Try installing with:
    sudo zypper install flatpak-devel

Installed this as well. And run:

$ flatpak-coredumpctl org.telegram.desktop
Traceback (most recent call last):
  File "/usr/bin/flatpak-coredumpctl", line 83, in <module>
    coredumper.run()
  File "/usr/bin/flatpak-coredumpctl", line 44, in run
    subprocess.check_call(["coredumpctl", "dump"] + shlex.split(self.coredumpctl_matches),
  File "/usr/lib64/python3.11/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['coredumpctl', 'dump']' returned non-zero exit status 1.

Now I have to wait for the crash and then $ flatpak-coredumpctl org.telegram.desktop should give some useful data? How should I put here? I'm not a programmer...

ilya-fedin commented 1 month ago

Now I have to wait for the crash and then $ flatpak-coredumpctl org.telegram.desktop should give some useful data?

I'm not sure. Additional steps will likely be required.

How should I put here? I'm not a programmer...

I recommend to just throw out flatpak and use the static binary with automatic crash reporting feature in that case.

ezhan commented 1 month ago

Всё оказалось напрасно... :)

OK, installed Telegram 5.4.1 from Tumbleweed repo via KDE Discover. But I still do not see any "enable beta versions installation in Settings -> Advanced for the reporter to appear."

ilya-fedin commented 1 month ago

OK, installed Telegram 5.4.1 from Tumbleweed repo via KDE Discover.

I told to install the static binary (which is distributed on desktop.telegram.org), not from some repo...

ezhan commented 1 month ago

OK, installed. Found the beta toggle. Now waiting for crash.

ezhan commented 1 month ago

Seems that the build from desktop.telegram.org works fine, no crashes for many days. The problem is with the flatpak version, that unexpected closes...

ilya-fedin commented 1 month ago

Well, so either just use the binary or get a backtrace from the flatpak version somehow. Sadly I can't help you with the error you got for flatpak-coredumpctl so you have to resolve it on your own first.

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.