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.

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

Not building manually (have never done it), using package manager to install packages. If we really need abandon package manager and start building manually - this renders package management useless. Tried:

yay --cleanmenu --rebuild -S zoom
rm -fr .zoom/
zoom

... still nothing - Zoom won't start.

@cjm In general it is a good idea to build in a clean environment (preferably a chroot). Cleaning up the environment however is not the job of the PKGBUILD.

@gdower Thank you! Deleting pkg/ and src/ before building the package finally fixed my undefined symbol error. (It seems to me the PKGBUILD should do that if necessary.)

Seems like the "hide floating meeting controls" option is missing and has been disabled in zoom-5.14.0. Anyone know if there's any way to re-enable that? Maybe in a config file? It's a nuisance to have the meeting controls hiding a big chunk of my screen share.

Even current 5.14.0-1 won't start. When trying to start from CLI, no output - just won't start. Once the system tray icon shortly appears but less than second disappears and that's all. When removed ~/.zoom/ folder temporarily to another location and tried to start Zoom again from CLI with clean settings, then I got lots of output and most relevant part:

Client: Breakpad is using Single Client Mode! client fd = -1
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
.....
Linux Client Version is 5.14.0 (1720)
QSG_RENDER_LOOP is 
XDG_CURRENT_DESKTOP = KDE;   GDMSESSION = ;   XDG_SESSION_TYPE = x11
Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2)
Zoom package arch is 64bit, runing OS arch is x86_64, snap package 0
AppIconMgr::systemDesktopName log Desktop Name: plasma 
zoom was exited due to a handled signal: 11 
ZoomLauncher exit.