Telegram Desktop unable to launch on Raspberry Pi 5 about tdesktop HOT 11 CLOSED

request support for your device at https://github.com/jemalloc/jemalloc with default build configuration

from tdesktop.

@ilya-fedin they have no intention of changing the default as of now
redirecting the issue back to you.

from tdesktop.

@theofficialgman tdesktop doesn't have the intention either, especially since amd64 is the only officially supported architecture. arm64 flatpak exists only because flathub builders build it automatically (the same for snap).

from tdesktop.

@ilya-fedin aarch64 is an officially supported architecture. Refer to the official verified flatpak https://flathub.org/apps/org.telegram.desktop

Let's get this issue with telegramdesktop fixed.

from tdesktop.

@theofficialgman i'm not sure what you wanted to proof by this link, arm64 is not officially supported by tdesktop. You can build it, flathub can build it but it's not guaranteed to work.

from tdesktop.

Don't get me wrong, I'm not against if someone would PR a solution that will let tdesktop work on rpi5 while not making tdesktop less optimized for other architectures and ideally other machines (that work right now) on the same architecture. Yet, I have no personal interest in this issue to work on it and arm64 is not an officially supported architecture to deserve an open issue about that.

Moreover, I guess having lesser page size is even more important on arms than on amd64, as such hardware usually has limited RAM size.

from tdesktop.

@ilya-fedin flathub builds are official and supported (see verified tag at https://flathub.org/apps/org.telegram.desktop). Aarch64 is enabled in flathub builds https://github.com/flathub/org.telegram.desktop

Thus aarch64 is supported. Not sure why this concept is so difficult for you.

from tdesktop.

@theofficialgman only amd64 build is official. arm64 build is present only because builders build it, as I mentioned earlier.

from tdesktop.

And, well, flatpak and snap builds are more like semi-official, as they use API key created by a third party person.

from tdesktop.

I see. I'll contact flathub and have the verified badge removal as it's not official.

from tdesktop.

Not sure why this concept is so difficult for you.

The problem is you're using third party projects (flathub) as the source of truth. If you will look this repository, you won't find any sign that ARM is supported. The official build instructions are amd64-only and previous issues about ARM support were closed as there doesn't seem to be any need in Linux ARM support from Telegram PoV and the community doesn't seem to have enough interest to help with code for ARM support (implementing a cross-compilation script to build official binaries for ARM on amd64 hardware).

from tdesktop.