VOOZH about

URL: https://aur.archlinux.org/packages/zapzap

⇱ AUR (en) - zapzap


Arch Linux User Repository

Search Criteria

Package Details: zapzap 6.5.2.1-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: 68
Popularity: 2.43
First Submitted: 2022-09-25 10:47 (UTC)
Last Updated: 2026-06-17 12:09 (UTC)

Required by (0)

Sources (2)

Pinned Comments

alllexx88 commented on 2025-10-16 15:59 (UTC)

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.

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 .. 9 Next › Last »

Technetium1 commented on 2026-06-10 21:09 (UTC)

@alllexx88 Thank you very much, that fixes it!

alllexx88 commented on 2026-06-10 14:57 (UTC)

@marco.righi I also have a hybrid Intel+Nvidia graphics, and don't experience the same issue. However, I did add ZapZapNoGpu launcher, for cases like yours. Thanks.

@Technetium1 Done. Please verify.

Technetium1 commented on 2026-06-10 14:13 (UTC) (edited on 2026-06-10 14:26 (UTC) by Technetium1)

Please use double quotes for source. It causes shfmt's parser to fail.

marco.righi commented on 2026-06-09 08:28 (UTC) (edited on 2026-06-09 08:30 (UTC) by marco.righi)

Hi,

I am seeing a reproducible issue with the AUR package zapzap on EndeavourOS / Arch Linux on a hybrid Intel + NVIDIA laptop.

Normal startup may fail with a segmentation fault or WhatsApp Web may initially show:

You are not connected to the Internet.

The network is working correctly:

https://web.whatsapp.com HTTP status: 200
https://www.google.com HTTP status: 200
web.whatsapp.com:443: OK
web.whatsapp.com:5222: OK

System:

OS: Manjaro Linux
Kernel: 7.0.10-1-MANJARO
Session: x11
Desktop: XFCE
zapzap executable: /usr/bin/zapzap

Package versions:

zapzap: 6.5.1-1
python-pyqt6: 6.11.0-2
python-pyqt6-webengine: 6.11.0-1
qt6-base: 6.11.1-1
qt6-webengine: 6.11.1-1
nvidia-utils: 595.71.05-2
nvidia-dkms: 595.71.05-1
nvidia-open-dkms: 
mesa: 1:26.1.1-2
vulkan-icd-loader: 1.4.350.0-1
fontconfig: 2:2.17.1-1
xdg-desktop-portal: 1.20.4-1
xdg-desktop-portal-gtk: 1.15.3-1
networkmanager: 1.56.1-1

Graphics:

 Graphics:
 Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Dell driver: i915
 v: kernel arch: Gen-9.5 ports: active: DP-2,DP-3,eDP-1 empty: DP-1
 bus-ID: 00:02.0 chip-ID: 8086:9bc4
 Device-2: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q] vendor: Dell
 driver: nvidia v: 595.71.05 arch: Turing pcie: speed: 2.5 GT/s lanes: 8
 bus-ID: 01:00.0 chip-ID: 10de:1fb8
 Device-3: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
 speed: 480 Mb/s lanes: 1 bus-ID: 1-11:7 chip-ID: 0bda:5510
 Display: x11 server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
 compositor: xfwm4 v: 4.20.0 driver: X: loaded: modesetting,nvidia
 alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :0.0
 screens: 1
 Screen-1: 0 s-res: 3840x2280
 Monitor-1: DP-2 pos: middle-l model: Asus VE247 res: 1920x1080 hz: 60
 dpi: 92 diag: 609mm (24")
 Monitor-2: DP-3 pos: top-right model: AOC 27B3HM res: 1920x1080 hz: 60
 dpi: 82 diag: 686mm (27")
 Monitor-3: eDP-1 pos: bottom-r model: Sharp 0x14d0 res: 3840x2400 hz: 60
 dpi: 290 diag: 396mm (15.6")
 API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 1 drv: nvidia-drm
 device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia surfaceless:
 drv: nvidia x11: drv: iris inactive: wayland
 API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 26.1.1-arch1.2
 glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
 device-ID: 8086:9bc4
 Info: Tools: api: eglinfo,glxinfo de: kscreen-console, kscreen-doctor,
 xfce4-display-settings gpu: gputop, intel_gpu_top, lsgpu,
 nvidia-settings, nvidia-smi x11: xprop,xrandr

NVIDIA:

Quadro T2000 with Max-Q Design, 595.71.05

Observed messages include:

XDG_SESSION_TYPE: x11
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Segmentation fault (core dumped)

With GPU/Vulkan disabled, the segmentation fault disappears, although ZapZap may still print some initial offline messages before connecting:

GPUInfo not initialized on GpuInfoUpdate
Fontconfig error: Cannot load default config file: No such file: (null)
You are not connected to the Internet.

Working workaround:

env -u http_proxy -u https_proxy -u HTTP_PROXY -u HTTPS_PROXY -u all_proxy -u ALL_PROXY -u FONTCONFIG_FILE -u FONTCONFIG_PATH QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu --disable-gpu-compositing --disable-vulkan --disable-features=Vulkan,VulkanFromANGLE --no-proxy-server" zapzap

Hypothesis: this looks like an interaction between ZapZap, PyQt6-WebEngine / QtWebEngine, embedded Chromium, NVIDIA/Vulkan/GBM initialization, and hybrid Intel + NVIDIA graphics.

Could this workaround be documented, or could an optional zapzap-nogpu launcher be provided for affected systems?

Thanks.

costancho commented on 2026-06-08 15:29 (UTC)

The app sends notifications whenever it wants. I had to switch to WhatsApp Web

vncvx commented on 2026-05-13 13:49 (UTC)

Not working:

Compile: po/pl.po -> locale/pl/LC_MESSAGES/zapzap.mo msgfmt -o locale/pl/LC_MESSAGES/zapzap.mo po/pl.po po/pl.po:751: duplicate message definition... po/pl.po:471: ...this is the location of the first definition /usr/bin/msgfmt: found 1 fatal error error: command '/usr/bin/msgfmt' failed with exit code 1

retoon commented on 2026-04-04 10:29 (UTC)

Seems broken on Wayland. Getting stack trace with Qt errors eg. libQt6WaylandClient.

jesusfl commented on 2026-04-02 19:08 (UTC)

I'm getting the following error:

Error injecting WebRTC shield: [Errno 2] No such file or directory: '/usr/lib/python3.14/site-packages/zapzap/webengine/webrtc_shield.js'

and there's an issue on the repository that may be related to needing to rebuild

https://github.com/rafatosta/zapzap/issues/651

I've already run

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

but it didn't solve the problem.

airwavesextreme commented on 2026-04-01 12:28 (UTC)

After the newest update the package does not work for me anymore. When installing through yay, I get the following errors: "GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium. QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")". The AUR package wasn't rebuilt for Python 3.14.

kionez commented on 2026-03-30 07:37 (UTC)

I have the same "killed by SIGSEGV" issue on my laptop with hybrid graphic and wayland. I discover that running zapzap with prime-run it works fine, I don't have time to investigate, hope it helps (otherwise ignore me :) )

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

aurweb v6.3.4

Report issues here.

Copyright © 2004-2026 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.