Arch Linux User Repository

@Rhinoceros - I finally got screen sharing to work under KDE with Wayland. Looks like I'm using the same versions as you:

• Zoom 6.2.10
• pipewire 1.2.6

I followed the Screen share section on the Zoom wiki page:

https://wiki.archlinux.org/title/Zoom_Meetings

The only thing I didn't need to do was set XDG_CURRENT_DESKTOP=gnome. I followed the other steps, and now I can choose my desktop/window to share. Prior to following the wiki I couldn't stop screen sharing without the hanging issue, which I was experiencing prior to 6.2.10.

I've got the same issue as @neuronestanco and google hasn't been forthcoming.

Running GNOME / Wayland, attempting to open any of the in-call menus (e.g. "View" or the caret "^" menus beside the mic/camera icons) only works occasionally. Sometimes the menu appears to open but then quickly disappears entirely, other times the menu will be visible with no text. Usually if I click enough times I can get a functional menu to appear.

The only hint I have here is the following in the Zoom log, and I have no idea if it's normal:

QBasicTimer::start: Timers cannot have negative timeouts

To the maintainer and people who are running wayland and have an Nvidia graphics card the current version (5.14.10-1) is broken. The solution I had was to downgrade to zoom-5.14.7-1. For reference look at:

https://community.zoom.com/t5/Meetings/Unable-to-start-zoom-on-linux-with-quot-pacmd-command-not-found/m-p/61892

https://community.zoom.com/t5/Meetings/Linux-Regarding-Nvidia-Xwayland-Wayland/m-p/72922

Please, there is a problem with the "view" window on the top left; it is necessary to click many times before the choice menu for the type of visualization appears

#!/bin/bash
#script to check for upstream update and update/install it if required.
currentV=$(pacman -Q -i zoom | grep Version | cut -d':' -f2 | cut -d' ' -f2)
echo "current version is: $currentV"
downV=$(curl -s 'https://zoom.us/support/download' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0' -H 'Accept: text/html' -H 'Accept-Language: en-US,en;q=0.5' | pcregrep --om-separator=. -o1 -o2 "([0-9\.]*)\s\(([0-9]*)\)" | head -1)
downV="${downV}-1"
echo "latest  version is: $downV"

if [[ "$currentV" = "$downV" ]] ; then
    notify-send "no update available for zoom $currentV -- $downV"
else
  echo installing the latest version $downV
    notify-send "updating zoom to $downV"
    curl -L "https://zoom.us/client/latest/zoom_x86_64.pkg.tar.xz" -o ~/Downloads/zoom_x86_64.pkg.tar.xz
    sudo pacman -U ~/Downloads/zoom_x86_64.pkg.tar.xz
fi

still zoom 5.14.7-1 won't start and even that sudo chmod 4755 /opt/zoom/cef/chrome-sandbox does not help - still same libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) error :(

FYI, re: my "floating meeting controls" question a while back, apparently they've moved that setting ("Always show meeting controls") to the "General" section of settings (see https://community.zoom.com/t5/Meetings/UNABLE-TO-SHOW-HIDE-MEETING-CONTROLS/m-p/13252) and have enabled it by default in recent releases. It was easy enough to turn off, now that I know where the setting is.

Interesting is, that flatpak version of same Zoom v5.14.2 is working on same laptop (without tweaking SUID permissions, etc) but not AUR version. Here are installed packages via flatpak:

flatpak list
Name                          Application ID                                       Version             Branch              Installation
Freedesktop Platform          org.freedesktop.Platform                             22.08.9             22.08               system
Mesa                          org.freedesktop.Platform.GL.default                  22.3.5              22.08               system
Mesa (Extra)                  org.freedesktop.Platform.GL.default                  22.3.5              22.08-extra         system
nvidia-530-41-03              org.freedesktop.Platform.GL.nvidia-530-41-03                             1.4                 system
Intel                         org.freedesktop.Platform.VAAPI.Intel                                     22.08               system
openh264                      org.freedesktop.Platform.openh264                    2.1.0               2.2.0               system
Breeze GTK theme              org.gtk.Gtk3theme.Breeze                             5.27.3              3.22                system
Zoom                          us.zoom.Zoom                                         5.14.2.2046         stable              system

@DukeHarris - no, qt6-wayland does not help as my error message is:

Client: Breakpad is using Single Client Mode! client fd = -1
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

Mentioned ~/.zoom/logs/zoom_stdout_stderr.log didn't contain any Qt-related issues Besides, I have already qt6-wayland package installed. Still same error and Zoom won't start. Also I have nVidia GPU. Computers without nVidia GPU there will that chrome-sandbox SUID trick help but not with nvidia GPU.

@zeroconf I had the same issues you're describing and managed to fix them by installing qt6-wayland

Zoom would also simply not start for me and I found this in ~/.zoom/logs/zoom_stdout_stderr.log:

qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

This brought me to https://wiki.archlinux.org/title/Wayland#Qt which mentions installing qt5-wayland or qt6-wayland for Wayland support in Qt.

I hope this helps

Still having issues with v5.14.2-1 in same laptop, where initially reported. My installation permissions and issues are written here. The previous test was done in desktop PC, where I somehow succeeded to run Zoom 5.14.0 - possibly because there is no nVidia GPU but only integrated Intel one (Intel HD Graphics 530). Currently using flatpak version (which is still v5.13.11.1288) as a quick workaround on that laptop with dual GPU (Intel, nVidia but nVidia is in use). Thank you for clean build tutorial but for now didn't have enough time to hack. Found similar issue on zoom community forum but disabling sandbox (zoom --disable-gpu-sandbox) didn't help either, even SUID were or were not applied to /opt/zoom/cef/chrome-sandbox. Also I removed ~/.zoom/ folder before each attempt to start zoom. Direct link to my post in Zoom forum with more detailed information about my hardware on different PCs. Also counterpart post in nVidia forum.