Zoom client starts up but shows no text on wayland

[jpretori]

I just updated the snap, and when I try to start the application it doesn't seem to render any text at all.

I can guess my way through the interface until I get to some error message, which of course I can't read.

I made a gif video so you can see what I'm talking about.

[ogra1]

can you attach the full output of snap version and your:

~/snap/zoom-client/current/.zoom/logs/zoom-terminal.log

... after you have captured that file and attached it here you can:

sudo snap revert zoom-client

to go back to the last working version ... funnily the last update was supposed to fix all font issues ... seems like it did exactly the opposite for you 😞

[jpretori]

Here you go:

snap version

snapd   2.45
series  16
ubuntu  18.04
kernel  5.3.0-53-generic

zoom-terminal.log

Thanks for the help! Unfortunately trying to revert gets me this: error: cannot revert "zoom-client": no revision to revert to

It's no biggie, I'll just use it on my Android for the time being.

[ogra1]

this looks actually wayland related ... does it work if you switch to an Xorg session ?

[jpretori]

Hi there, Yip switching to Xorg makes it work just fine. Regards, - Johan Pretorius

…

On Thu, Jun 4, 2020 at 10:13 AM Oliver Grawert ***@***.***> wrote: this looks actually wayland related ... does it work if you switch to an Xorg session ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3RGV5R4J4AA7QIIMHBQU3RU5JSBANCNFSM4NQNBW4A> .

[fooishbar]

Wayland doesn't render fonts. The fonts are rendered client-side by Qt (in fact the same as X11 too). If Qt isn't rendering any fonts then that's a bug in the application or the toolkit.

[ogra1]

Thanks Daniel ! I'll invest some time on the weekend to look into the various wayland issues again (currently the snap simply uses WAYLAND_DISABLE=true to force XWayland which indeed isn't ideal but was a quick fix to make it start on wayland at all without having to dig into missing libs :) )

[fooishbar]

FWIW it might be worth looking at the Flatpak, which works fine for me in a Wayland session.

[ogra1]

is the flatpak actually using the upstream deb ? i thought that was just a wrapper for the web client ...

[fooishbar]

It uses the tarball from zoom.us, and seems like it explicitly forces X11. There's a bunch of discussion in the issues and PRs on the Flathub repo about enabling Wayland support, which seem like they'll require an update for Zoom itself.

[FastAlien]

I had similar problem on X11, but I've found solution. Copy one selected type of fonts from /usr/share/fonts to ~/.local/share/fonts and update the font cache. For example on Ubuntu you can execute following commands:

mkdir -p ~/.local/share/fonts/
cp /usr/share/fonts/truetype/liberation/LiberationSans-* ~/.local/share/fonts/
fc-cache -rvf 

[brainwane]

@RandomVoid Thank you -- I had this same problem, where no text was showing up, and then I tried the commands you suggested on Debian buster (10) and they worked so that Zoom was able to display text in the interface.