Tdesktop: error while loading shared libraries: libatomic.so

[xhdix]

Steps to reproduce

1. Open Telegram

Actual behaviour

$ /home/username/.local/share/Telegram/Telegram -- %u
/home/username/.local/share/Telegram/Telegram: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Configuration

Operating system: Fedora 32

Version of Telegram Desktop: (IDK! Install beta is enabled) updated in: 2020/07/24

Installation source (Linux Only) the official website

Used theme: Default: Night mode

[xvitaly]

Fedora 32

You can install packaged version from RPM Fusion repository or use Flatpak.

[andreyorst]

Fedora 32

You can install packaged version from RPM Fusion repository or use Flatpak.

not a solution for this particular problem. Perhaps static build missing this library?

@xhdix dnf install libatomic fixed the issue for me

[xhdix]

You can install packaged version from RPM Fusion repository or use Flatpak.

I don't want to use them.

Perhaps static build missing this library?

Definitely

@xhdix dnf install libatomic fixed the issue for me

Yes,thanks! But it's a good opportunity to stop using Telegram for a few days. :P

[xvitaly]

I don't want to use them.

Why? Packaged version built from official sources on Fedora build infrastructure and linked against system-wide libraries.

Flatpak version built from the same sources too and is the semi-official.

[andreyorst]

Flatpak version built from the same sources too and is the semi-official.

Telegram officially shipped as a binary, and this binary seem to miss a dependency it needs to work. On official site, there is no installation guide, that mentiones any additional dependencies needed to be installde, so this is clearly an error in binary build. If it was shipped as a package, it would be packaging issue, that would be addressed to package maintainers, but currently we have a problem of unsatisfied dependency, that breaks working application by update, which is a huge issue. Suggesting unofficial installation methods is not a solution, so please stop fooling around. If user does not want to use flatpak it is his business, and since there's no official flatpak build please do not suggest it in the official bug tracker. If you do not know how to deal with this issue, please ping someone who does, otherwise explicitly mark your suggestions as workaround, and not a problem solution to avoid confusion. Thanks.

[xvitaly]

Telegram officially shipped as a binary, and this binary seem to miss a dependency it needs to work.

Yes, it built against very outdated static libraries from Ubuntu 14.04 LTS and there is no way to track dependencies for out-of-repositories static binaries.

Dnf will automatically resolve and install all the needed dependencies, but only for applications from repositories or well-packaged single RPMs.

Suggesting unofficial installation methods is not a solution, so please stop fooling around.

For GNU/Linux users the official installation method for opensource applications is its repository.

I'm Fedora and RPM Fusion maintainer btw.

since there's no official flatpak build

Flathub is the official installation source for Telegram Desktop.

[andreyorst]

I'm Fedora and RPM Fusion maintainer btw.

Cool!

[john-preston]

@andreyorst This was a bug in configuration scripts, it will be fixed in the next version in couple of days. Thank you for your report!

[ilya-fedin]

and since there's no official flatpak build please do not suggest it in the official bug tracker

[andreyorst]

and since there's no official flatpak build please do not suggest it in the official bug tracker

Then this is a separate issue of an official webpage not providing all official ways to instal telegram, that perhaps as well should be addressed

[Aokromes]

try on 2.2.0

[xhdix]

@Aokromes , Thanks! It's fixed. But I had to log in again! However, there was no such problem for another account with a different workdir.