Package Details: ayugram-desktop 5.16.4-5

Git Clone URL: https://aur.archlinux.org/ayugram-desktop.git (read-only, click to copy)
Package Base: ayugram-desktop
Description: Desktop Telegram client with good customization and Ghost mode.
Upstream URL: https://github.com/AyuGram/AyuGramDesktop
Keywords: anti-recall ayugram telegram
Licenses: GPL-3.0-or-later WITH OpenSSL-exception
Submitter: ZhangHua
Maintainer: ZhangHua
Last Packager: ZhangHua
Votes: 17
Popularity: 0.83
First Submitted: 2023-11-06 01:05 (UTC)
Last Updated: 2025-10-11 12:03 (UTC)

Required by (0)

Sources (40)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

toitenminh commented on 2025-10-18 02:07 (UTC) (edited on 2025-10-18 02:09 (UTC) by toitenminh)

Crash after click a random chat if using Fcitx5. there is a temporary workaround available: modify the application's desktop file (unset QT_IM_MODULE and DBusActivatable=false).

Exec=env -u QT_IM_MODULE DESKTOPINTEGRATION=1 AyuGram -- %u
DBusActivatable=false

The issue has been permanently addressed in commit https://github.com/AyuGram/lib_ui/commit/3e254ffe1bc1fce081d56fbf8c2c9d7f1218bd3d

ZhangHua commented on 2025-10-13 08:57 (UTC)

I am using i7 8750H with 16GB ram and 16GB swap, that seems to be nearly enough, although my pc freezes for seconds during building. I am building in a chroot environment and do not set any parallel jobs, so Ninja will use all of my 12 logical cores to build.

Xbz commented on 2025-10-13 08:53 (UTC)

this package uses too much resources to build, everytime I try to install this my computer freezes, I am using i7 8700k with a gtx1080 and 16gb ram, it should be eneough to be able to build it but you are not doing parallel build jobs dont you?

ZhangHua commented on 2025-10-12 09:12 (UTC)

@petRUShka I think it is because you got a broken file. For me, the checksum is correct:

$ curl -L https://github.com/telegramdesktop/tdesktop/commit/28d19a99.patch | sha256sum
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2103  100  2103    0     0    459      0  0:00:04  0:00:04 --:--:--   622
e3aabdf4942f1e22819dffe4eb481ca0d7e32cfbed9443120c2d29f3abf07971  -

You may consider removing it and let makepkg download again.

petRUShka commented on 2025-10-12 08:15 (UTC)

Right now there is a problem with validity checks:

==> Validating source files with sha256sums...
    AyuGram-v5.16.4.tar.gz ... Passed
    ...
    28d19a99.patch ... FAILED
    ...
==> ERROR: One or more files did not pass the validity check!
 -> error making: ayugram-desktop-exit status 1

ZhangHua commented on 2025-10-12 02:00 (UTC)

@vann I cannot reproduce on my device. So that may because your IP is blocked by gitlab.com. You may have to download this file in browser and place it next to PKGBUILD, or use a VPN to overcome this.

vann commented on 2025-10-11 23:19 (UTC)

With both makepkg -si and paru

curl: (22) The requested URL returned error: 403
==> ERROR: Failure while downloading https://gitlab.com/mnauw/cppgir/-/archive/33ee935b39efd03bb7ab8f62ad02f7f2cd018dc8/cppgir-33ee935b39efd03bb7ab8f62ad02f7f2cd018dc8.tar.gz
    Aborting...
error: failed to download sources for 'ayugram-desktop-5.16.4-5':

ZhangHua commented on 2025-09-30 01:26 (UTC)

@arkadym Most of the time it depends on the parallel build jobs. As ayugram uses Ninja as backend of cmake, it uses all of your cpu logic cores by default. Maybe you can set CMAKE_BUILD_PARALLEL_LEVEL environment variable to limit that: https://cmake.org/cmake/help/latest/envvar/CMAKE_BUILD_PARALLEL_LEVEL.html

As for me, I use 16GB ram and 16GB swap with 12 cpu cores, it does use a lot of resource, but can still success.

arkadym commented on 2025-09-29 14:12 (UTC)

@ZhangHua i think question more on why it required more than 32Gb of ram to build ? I can confirm with my desktop, it requires to enable swap 16+GB to make ayugram to build. That is on arch linux, same time it can successully build on my laptop with monjaro with 32GB of ram and no swap, what it depends on ?

ZhangHua commented on 2025-09-29 13:26 (UTC)

@nyunyun You can call makepkg with --log parameter, which let makepkg generates build log for diagnosing or archiving.