Arch Linux User Repository

@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.

Some ~/.config/zoomus.conf updates:

• SSO Login: I don't have qt5-webengine installed, and the ebeddedBrowserForSSOLogin line doesn't exist in my config zoomus.conf. SSO login works just fine (issues with Firefox containers aside).
• Audio: I am using Pipewire via pipewire-pulse. system.audio.type defaulted to alsa for me (or I changed it without realizing it). I probably could have installed pipewire-alsa and fixed my issues, but I set system.autio.type=pulse (a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.

If anyone finds documentation on ~/.config/zoomus.conf, please let us know.

#!/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.

zeroconf: glad you got it working too, and good callout on the new version - hopefully this manual setuid business won't be necessary much longer.

i recommend https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot for more information on clean chroot building - there are helper scripts in the devtools package, or if you prefer you can set up the chroots manually and build from them.

@ItsQuote - yes, sounds like that was the issue.

initially:

stat -c '%A %a %U %G %n' /opt/zoom/cef/chrome-sandbox 
-rwxr-xr-x 755 root root /opt/zoom/cef/chrome-sandbox

then adding SUID

sudo chmod 4755 /opt/zoom/cef/chrome-sandbox

then checking:

stat -c '%A %a %U %G %n' /opt/zoom/cef/chrome-sandbox 
-rwsr-xr-x 4755 root root /opt/zoom/cef/chrome-sandbox

... and Zoom is working again. Even didn't need to wipe ~/.zoom/ folder.

I understand, that this is probably Zoom own issue. For now is already version 5.14.2 (2046) out and currently already flagged as out of date. Perhaps new version has that permission issue fixed already. If anyone has reported that issue to Zoom. That's a good question, how such reporting is possible to Zoom. At least from Zoom website didn't find a way to report a bug (or any other issue) for free to Zoom. Looks like paid support allows to do that...

If any useful tutorial exist for clean building, it might be helpful.

zeroconf: yay is not your package manager, pacman is. pacman is not responsible for building packages, that's what makepkg and its friends are for. it would be more accurate to state this is a problem with Zoom, since the "build" very simply repackages upstream's archive. neither pacman nor makepkg have much say in how the binaries are produced in this case.

that being said: i too have been running into issues with Zoom dumping core as soon as it started, which seemed to be related to the bundled libcef.so. building in a clean chroot and wiping out ~/.zoom/ finally produced console output that indicated /opt/zoom/cef/chrome-sandbox was not setuid, and after "sudo chmod 4755 /opt/zoom/cef/chrome-sandbox" it began loading normally. is there anything in your omitted console output or your journal that might indicate a similar problem?