Arch Linux User Repository

Please do not flag this package outdated just because there are some library files missing after your archlinux upgraded. You need to simply rebuild this PKGBUILD with latest archlinux. For those people who meet that Qt/xxHash symbols missing, the solution is same.

To people who find that some files failed to pass check:

You may consider removing them and download again. I use updpkgsums after editing PKGBUILD and removing all generated files rm *.log *.pkg.tar.* *.tar.gz, so most of the time you should check if it is your problem. If it is my fault, please leaving a comment so we can investigate further.

Boradorka, you probably have a third-party ffmpeg installed. install normal ffmpeg and try again. I had the same issue

[ 91%] Building CXX object Telegram/CMakeFiles/Telegram.dir/SourceFiles/settings/business/settings_working_hours.cpp.o

{стандартный ввод}: Сообщения ассемблера:

{стандартный ввод}: Внутренняя ошибка (Ошибка сегментирования).

Пожалуйста, сообщите об этой ошибке.

make[2]: *** [Telegram/CMakeFiles/Telegram.dir/build.make:10308: Telegram/CMakeFiles/

Telegram.dir/SourceFiles/settings/business/settings_working_hours.cpp.o] Ошибка 1

make[1]: *** [CMakeFiles/Makefile2:1763: Telegram/CMakeFiles/Telegram.dir/all] Ошибка 2

make: *** [Makefile:136: all] Ошибка 2

@ZhangHua @onestep

I am experiencing a strange issue. After installation and every upgrade, I get:

$ ayugram-desktop 
Aborted (core dumped)

However, after installing telegram-desktop (which also pulls libmng and qt6-imageformats), everything works fine. I initially thought it was a dependency issue, but after uninstalling telegram-desktop and the two additional dependencies, everything continues to work without a core dump. There are no hooks provided by these three packages that could affect the system either.

Edit: ayugram-desktop does not, in fact, continue to function normally -- the stickers aren't loading. Please add qt6-imageformats as a dependency to resolve these issues.

@ZhangHua: thank you very much for your dedication I tried both the bin version on my arconet and the android version, it seems that it is not the latest version on android: the built-in translator lacks the language of the region I live in, the story posting feature is not supported, while the nekoX version on android does not have this problem I will probably still use NekoX as the main client on android and Telegram official on my PC, in parallel with ayugram with the Ghost Mode feature to experience

@oldman33 I checked their tarball, and I found that there is only one executable file /home/gentoo/Downloads/ayugram/ayugram-desktop in it and does not found some libraries like protobuf in ldd's outputs, it must be that they static linked everything possible, include protobuf, so I think you can run this file directly on archlinux. You can run bsdtar -xpf /path/to/ayugram.tar.gz to unpack it and get the executable.

As for the differences between those three packages, you can continue reading contents below:

TL;DR: Channel version and ayugram-desktop-bin are prebuilt versions. This package is built from source.

Detailed explaination: The tarball in channel is built by someone I do not know. ayugram-desktop-bin is repacked from andontie AUR's prebuilt version. Neither of what I can guarantee is safe. ayugram-desktop is completely built by yourself, you download source code and use compiler to get a working executable file. I just provide an automation script to build it. As for it safety, I think it may be better than those versions mentioned before because everything can be audited by yourself. Because channel version and ayugram-desktop-bin are prebuilt version, you do not need a lot of resource to build from source like this package, but prebuilt versions may not be suitable for your distribution. For example, I saw your distribution is ArcoLinux, while aur is designed for ArchLinux, if your distribution cannot follow ArchLinux's upgrades, like protobuf is upgraded after ArchLinux's upgrades for some hours to days, or to even weeks, you may meet that protobuf's so is missing during this period of time. Because prebuilt version links to a newer protobuf on ArchLinux but your distribution has not upgraded it.

If you are curious why I use protobuf as example, that's because protobuf usually changes its so's names when upgrades and breaks a lot of program depends on it, like ayugram-desktop. We have to rebuild those affected programs against upgraded protobuf. Thankfully it does not upgrade too frequent.

@ZhangHua thank, i tried ayugram-desktop-bin and seem it work, although I had to remove DESKTOPINTEGRATION=1 in the shortcut for it to run. i found in ayugram telegram channel build ayugram.tar.gz 87.3Mb, Any Linux build v5.4.1, not for PotnieYaicaOS. don't know how to try to run it on Arch Sorry if I'm asking a basic question, but what's the difference between those 3? The do not rebuild for protobuf upgrades build (from their telegram channel), the ayugram-desktop-bin build, and the build from AUR

@oldman33 Maybe you can check their telegram channel, someone built ayugram for linux and packaged as a tarball. But it seems that they do not rebuild for protobuf upgrades, so I doubt if you can run the prebuilt binary directly on your system. What's more, you can try ayugram-desktop-bin, it is just a repackage script for a prebuilt version of ayugram so you don't need to build ayugram yourself.

@ZhangHua , It seems too much for me, Ayugram on Linux is harder than I thought. Each person has to build for himself

@oldman33 Find makepkg.conf used for building, typically it should be /etc/makepkg.conf, find OPTIONS variable, you will find a lto in it, change it to !lto. This will disable makepkg adding lto flags, but cannot prevent if upstream project add lto flags. This will also change all packages use this makepkg.conf to build, if you just want to disable lto for this package, you can also choose setting options=(!lto) in the PKGBUILD.