Package Details: zapzap 6.0.1.8-1

Git Clone URL: https://aur.archlinux.org/zapzap.git (read-only, click to copy)
Package Base: zapzap
Description: WhatsApp desktop application written in Pyqt6 + PyQt6-WebEngine
Upstream URL: https://github.com/rafatosta/zapzap
Licenses: GPL3
Submitter: bordam
Maintainer: alllexx88 (AutoUpdateBot)
Last Packager: AutoUpdateBot
Votes: 36
Popularity: 2.88
First Submitted: 2022-09-25 10:47 (UTC)
Last Updated: 2025-03-08 07:56 (UTC)

Pinned Comments

alllexx88 commented on 2024-12-24 08:51 (UTC)

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

alllexx88 commented on 2024-04-06 19:31 (UTC)

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

Latest Comments

1 2 3 4 5 6 Next › Last »

MajorMayer commented on 2025-04-10 21:07 (UTC)

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

MajorMayer commented on 2025-04-08 16:16 (UTC) (edited on 2025-04-08 16:16 (UTC) by MajorMayer)

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 ^^

alllexx88 commented on 2025-04-08 15:56 (UTC)

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.

MajorMayer commented on 2025-04-08 15:36 (UTC)

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?

MajorMayer commented on 2025-04-08 15:24 (UTC)

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.

alllexx88 commented on 2025-04-08 14:29 (UTC)

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.

MajorMayer commented on 2025-04-08 10:45 (UTC)

Here is my system info:

Operating System: Manjaro Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.12.22-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor 1: AMD Radeon RX 6800 Graphics Processor 2: Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B46 System Version: 1.0

As you can see, I am on Manjaro Linux, but it's the unstable branch, so the package versions should be mostly the same as Arch. Also, the user on Github reported that he is using Arch, so I don't think it's Manjaro-specific. I am using the open source AMD drivers (Mesa/ Vulkan-Radeon)

alllexx88 commented on 2025-04-08 10:27 (UTC)

@MajorMayer

Interesting, I also run latest KDE Plasma on Wayland: System Info

And zapzap works fine. Maybe it's the latest Nvidia drivers that I use? What GPU(s) do you have?

MajorMayer commented on 2025-04-08 10:17 (UTC)

As mentioned in the upstream repository, this package has issue on the latest KDE Plasma (Wayland): https://github.com/rafatosta/zapzap/issues/354 I can't find any error messages in the logs, but the windows is that broken, that you cannot use the app anymore.

Lukhas commented on 2025-03-12 20:40 (UTC)

@alllexx88 Sorry for the bother. I had done a full update, but for some reason even after restarting it didn't seem to apply. But as of now, it has started working again because reasons. Regardless, thanks for taking the time to reply.

1 2 3 4 5 6 Next › Last »