Arch Linux User Repository

Please don't flag package out-of-date if it stops working due to some dependency's upgrade, e.g., ImportError: libglslang.so.15: cannot open shared object file: No such file or directory. It's AUR and not an Archlinux repository: you just need to rebuild the package.

Since python has recently been upgraded to 3.13, you need to rebuild the package if you installed it last before the upgrade, e.g., with yay (thanks @marco.righi) you can:

yay -S zapzap --rebuildtree  --noconfirm  --rebuild --sudoloop

This PKGBUILD uses a pacman feature to compute checksums in CVS packages, which requires pacman>=6.1.0. If you're coming from Manjaro or an other Arch-based distro with pacman<6.1.0, you need to pass --skipchecksums to makepkg, if building manually, or, if installing with yay, add --mflags --skipchecksums, e.g.:

yay -S --mflags --skipchecksums zapzap

Package now installs again. Thanks. However it still doesn't start.

❯ zapzap
XDG_SESSION_TYPE: wayland
[983401:983401:0723/134952.724648:ERROR:/build/qt6-webengine/src/qtwebengine/src/core/net/system_network_context_manager.cpp:325] Cannot use V8 Proxy resolver in single process mode.
[983401:983401:0723/134952.724761:ERROR:/build/qt6-webengine/src/qtwebengine/src/core/net/system_network_context_manager.cpp:325] Cannot use V8 Proxy resolver in single process mode.
Single mode supports only single profile.
zsh: abort (core dumped)  zapzap

edit: got past this via deleting the ~/.config/ZapZap/ZapZap.conf now it also starts, but it throws into my face a popup with "What's new on WhatsApp Web" and doesn't go away. popup is unclosable from X on top right corner. It's just staying there and impossible to remove.

edit2: apparently it popped up another window to totally random off desk side monitor with initial settings... when completing this, was able to close the "what's new popup". program usable now. ...

Cause: the 7.0 tag was moved upstream after this package was published, so the pinned b2sum no longer matches the git source.

Timeline (UTC)

• 2026-07-18 09:13 AUR package published, sum taken from commit 1a3e5e0b
• 2026-07-18 14:37 upstream re-tagged 7.0 onto commit 2e063b0e

Correct b2sum for the current tag

d6d21655509a7bba48ae3f0e5781b3d464e2fd2c6c82606fe2f2c158326ed593f60ef7c3df7e447571e95e2e33f47cbb6dd91dab84d141288c349b2fa99e78c1

Impact: the diff between the two commits is only share/metainfo/com.rtosta.zapzap.appdata.xml plus 7 renamed screenshots. No Python code changed, so the resulting package is the same either way.

The tag has been stable for two days. Builds fine here with the sum above.

It is impossible to install zapzap:

Validating source files with b2sums...
   zapzap ... FAILED
   com.rtosta.zapzap.nogpu.desktop ... Verified
==> ERROR: One or more files failed validation!
-> Error while downloading source files: /home/prof/.cache/yay/zapzap
   context: exit status 1

Zapzap b2sum error?

@italoghost Please read the previous comments.

Hi! The latest update is not working. The b2sums for the source code is wrong:

==> Validando source arquivos com b2sums...
    zapzap ... FALHOU
    com.rtosta.zapzap.nogpu.desktop ... Passou

@zapotah: Just clone the repo, and update the checksums. This is exactly what a package maintainer would do so I guess it would be even safer if you do it yourself...?

makepkg -g >> PKGBUILD
sed -Ei 's/^(pkgrel=)1/\12/' PKGBUILD # bump the release number
makepkg

Error when downloading... zapzap 7.0-1 AUR package failed its checksum check

The git source's real checksum (d6d216...) doesn't match what the PKGBUILD pins (b484c6...).

==> Making package: zapzap 7.0-1 (Sun 19 Jul 2026 08:05:51 AM +08)
==> Retrieving sources...
  -> Updating zapzap git repo...
  -> Found com.rtosta.zapzap.nogpu.desktop
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    zapzap ... FAILED
    com.rtosta.zapzap.nogpu.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/mrjxtr/.cache/yay/zapzap 
    context: exit status 1 


:: (1/1) Parsing SRCINFO: zapzap
==> Making package: zapzap 7.0-1 (Sun 19 Jul 2026 08:05:52 AM +08)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating zapzap git repo...
  -> Found com.rtosta.zapzap.nogpu.desktop
==> Validating source files with b2sums...
    zapzap ... FAILED
    com.rtosta.zapzap.nogpu.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: zapzap-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
zapzap - exit status 1

@Nikolai508 There is nothing i can do besides skip checksum verifications which i am unwilling to do for AUR package considering recent developments. Hopefully the package maintainer fixes the package sooner rather than later.

@zapotah It looks like 7.0 was re-released and so the files are now different.

As a workaround for now, update the b2sums or SKIP.