Arch Linux User Repository

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

@ImFenyx It's hard to tell what exactly is wrong, but if this command gives you an error (I assume it should):

python -c 'from PyQt6.QtWebEngineCore import QWebEngineDownloadRequest'

It's an issue with your python-pyqt6-webengine not with this package.

According to libtree /usr/lib/python3.13/site-packages/PyQt6/QtWebEngineCore.abi3.so, libtheora is linked by libavcodec, so you may check if there's something wrong with it.

@alllexx88 I tried the same command with paru, but it didn't work. I don't think I've mixed extra with extra-testing, I had applied testing in pacman.conf and since weeks I've used paru -Syu, it's never been a problem

@ImFenyx things like this happen to AUR packages that are built from sources. Specifically, when a library the package was built against has a major update that changes the soname (like libtheora upgrade in extra-testing 1.1.1->1.2.0 has /usr/lib/libtheora{enc,dec}.so.2 instead of /usr/lib/libtheora{enc,dec}.so.1), the AUR package has to be rebuilt against the new version. Usually it's not an issue, since mostly these upgrades don't break source compatibility, but you have to do it manually, e.g., with zapzap when using yay:

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

UPD: OTOH, you get an error when importing from PyQt6.QtWebEngineCore, which is part of python-pyqt6-webengine from extra. Could it be you somehow mixed testing packages and stable ones?

There was a problem when running after a full system update.

Traceback (most recent call last):
  File "/usr/bin/zapzap", line 5, in <module>
    from zapzap.__main__ import main
  File "/usr/lib/python3.13/site-packages/zapzap/__main__.py", line 9, in <module>
    from zapzap.controllers.MainWindow import MainWindow
  File "/usr/lib/python3.13/site-packages/zapzap/controllers/MainWindow.py", line 5, in <module>
    from zapzap.controllers.Settings import Settings
  File "/usr/lib/python3.13/site-packages/zapzap/controllers/Settings.py", line 2, in <module>
    from zapzap.controllers.PageGeneral import PageGeneral
  File "/usr/lib/python3.13/site-packages/zapzap/controllers/PageGeneral.py", line 5, in <module>
    from zapzap.services.DownloadManager import DownloadManager
  File "/usr/lib/python3.13/site-packages/zapzap/services/DownloadManager.py", line 1, in <module>
    from PyQt6.QtWebEngineCore import QWebEngineDownloadRequest
ImportError: libtheoraenc.so.1: cannot open shared object file: No such file or directory

The flatpak version is working, but for some reason aur isn't.

edit: I tested another package and it was giving me a similar problem related to libtheoraenc.so.1.

In this case I fixed it (at least temporarily) by making a symbolic link to the same lib with a different name

sudo ln -s /usr/lib/libtheoraenc.so.2 /usr/lib/libtheoraenc.so.1
sudo ln -s /usr/lib/libtheoradec.so.2 /usr/lib/libtheoradec.so.1

Setting "QMLSCENE_DEVICE=softwarecontext" or "MESA_LOADER_DRIVER_OVERRIDE=zink" is a workaround for this issue.

Jep that's the first thing that I tried, and unfortunately the window is still glitching. I also tried disabling the hardware acceleration in the settings, which didn't change anything, and tried to disable Wayland, which notably changed the way the glitches look but nothing else ^^

Have you tried from terminal:

QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu --disable-gpu-compositing" zapzap

Just to make sure it doesn't work. Since I don't see overriding this env variable anywhere in zapzap code.

Unfortunately, the workaround proposed in the forum is not working with ZapZap, even if you set the environment variable (QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu --disable-gpu-compositing") globally for the login shell.
Any idea how this could be passed correctly to ZapZap?

Seems to be a current issue with Qt WebEngine: https://bugreports.qt.io/browse/QTBUG-135786
Also reported in the KDE forums: https://discuss.kde.org/t/some-of-my-kde-apps-arent-working-properly/32522/11

Let's hope this gets fixed quickly.

Looking at the GitHub issue report, and your system info, looks like you're both using AMD GPUs. So maybe this issue is Radeon-specific. I've no experience with them, perhaps there's something useful at https://wiki.archlinux.org/title/AMDGPU page, but I don't see anything obvious.