@alllexx88 Thank you very much, that fixes it!

@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.

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

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.

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

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

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

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.

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.

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 :) )