Zoom client does not load in Ubuntu 20.10 beta (Groovy Gorilla) under Wayland
Closed this issue · 8 comments
Switched to Wayland on my newly (minimally) installed system (as of yesterday). Installed zoom client (snap version) run fine under X but not under Wayland. I have attached the logs.
zoom_stdout_stderr.log
zoom-terminal.log
this is the issue ...
Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules"
Fontconfig warning: "/etc/fonts/fonts.conf", line 6: unknown element "its:translateRule"
Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'translate'
Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'selector'
Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'xmlns:its'
Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'version'
Fontconfig warning: "/etc/fonts/fonts.conf", line 9: unknown element "description"
you might be able to work around it by re-generating the font cache like:
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
fc-cache -r
Did that ran ran Zoom and and no go. Tried launching it in the terminal and got this error
mram@Inspiron-3451:$ zoom-client
xrdb: Connection refused
xrdb: Can't open display ':0'
mram@Inspiron-3451:$
yeah, i'm pretty sure wayland denies running X11 apps from the terminal
looks like
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897224
is related ... quoting from there:
On groovy Xwayland has parameters "-extension SECURITY", while focal does not.
so this needs to be fixed in snapd (or mutter/gnome-shell), not much the zoom snap can do about
Thanks marked a effecting me.
Doesn't work on Fedora 33 too.
➜ ~ zoom-client
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
xrdb: Connection refused
xrdb: Can't open display ':2'
well, canonical/snapd#9530 got merged 3 days ago, the fix should be in the edge channel of snapd already for people using the snapd snap, i guess the next fedora rpm build of snapd will have it too.
i believe this has long been fixed via the above snapd commit ... please re-open in case it unexpectedly still occurs