You are not logged in.
I've set my environment variable for QT to use Wayland, but I can't run the Zoom app (only one I've tried). I use Sway as my Wayland compositor.
I did as it says in the Wiki about QT
Environment variable set:
QT_QPA_PLATFORM=wayland-egl
Installed qt-wayland:
qt5-wayland 5.14.1-1
When I try to start Zoom, it says it can't find wayland-egl (which I thought is what is in the qt-wayland package):
chris@me $ zoom
ZoomLauncher started.
Zoom not exist at current directory - /home/chris
Zoom path is: /opt/zoom
cmd line:
CreateReportChannel bp_server_fd=4
$HOME = /home/chris
export SSB_HOME=/home/chris/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; export BREAKPAD_CLIENT_FD=3; /opt/zoom/zoom ""
zoom started.
Client: Breakpad is using Client-Server Mode! client fd = 3
This application failed to start because it could not find or load the Qt platform plugin "wayland-egl"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Reinstalling the application may fix this problem.
ZoomLauncher: new dump generated from pid 14561, path: /home/chris/.zoom/logs/a9c32d80-b313-4986-7d15b19c-d7f2fcc2.dmp
$HOME = /home/chris
sh: line 1: 14561 Aborted (core dumped) /opt/zoom/zoom ""
success to create child process,status is 34304.
zoom exited normally.
Something went wrong while running zoom,exit code is 134.
ZoomLauncher exit.
I have tried to re-install zoom, but it doesn't help. Also, it does work when I start it with X, using QT_QPA_PLATFORM=xcb - however, I do want to run it under wayland.
Packages and versions that might be of interest:
qt5-wayland 5.14.1-1
sway 1:1.4-8
wayland 1.18.0-1
wayland-protocols 1.20-1
zoom 3.5.361976.0301-1
Last edited by ChrisK (2020-03-22 12:21:30)
Offline
Maybe zoom has its own copy of QT without built-in wayland support?
Last edited by progandy (2020-03-22 12:28:16)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Maybe zoom has its own copy of QT without built-in wayland support?
Seems to be the case for the most popular Zoom PKGBUILD on the AUR, which depends on X: https://aur.archlinux.org/packages/zoom/
Maybe you could try the officlal Arch package from https://zoom.us/download
Offline
The zoom launcher sets LD_LIBRARY_PATH to /opt/zoom and uses its own library.
I've tried directly calling the library with
QT_QPA_PLAYFORM=wayland /opt/zoom/zoom
which should use the system version of qt. But I get nothing on the screen. Seems to connect to the wayland socket, but nothing displayed.
Offline
I have the same issue. I tried with the official client (as opposed to the one from AUR) and I get the bug regardless.
I remember that Zoom used to work at some point, even on Sway (~1 year ago).
Since Zoom mentions Archlinux in their official download page, I assume that they "officially" support it. Should we contact them to let them know about this?
EDIT:
You can temporarily fix this issue by making Zoom think that you are NOT using a wayland compositor... Just run Zoom (from AUR) using that command:
QT_QPA_PLATFORM= zoom
EDIT 2:
It is because
libqwayland-egl.so
is not present in
/opt/zoom/platforms/
I checked the archive from https://zoom.us/download (for ALL distros) and none of them include the library. I suspect there is an issue with the way Zoom is packaging their software. I tried to copy it manually but it did not work either, probably a version mismatch since my Arch has qt 5.14 libs and Zoom relies on 5.9.
EDIT 3:
I managed to get Zoom to "run" by copying the missing libs from https://mirror.centos.org/centos/7/os/x … x86_64.rpm (yikes... if you want to replicate this you have to copy both libqwayland-egl.so and libQt5WaylandC*.so to /opt/zoom/platforms and /opt/zoom/, finally a quick chown and you are good to go). Zoom does not crash and the icon appears in the tray area in Waybar, however there is no way to get a window, something is still wrong...
Last edited by charlesgervais (2020-04-20 20:21:16)
Offline
FWIW, I am running wlroots-git and sway-git, and I still see this both with Zoom, and with Ripcord, which is also using QT5. I think it's a QT5 problem.
Offline
As mentioned both of these are proprietary programs built with potentially outdated (or trimmed down builds of) Qt5 double check with an actual repo built qt5 program
Last edited by V1del (2020-05-18 21:24:40)
Offline