Zoom-us Wayland Screen Sharing Fix?

cgumb · August 8, 2024, 8:51pm

Hi, folks!

I am one of those wretched creatures compelled to use Zoom for work

To add insult to injury, it seems recent versions of Zoom break screen sharing under Wayland.

You can read more about this problem in this nixpkgs GitHub issue.

In the issue thread, it seems gvolpe was able to hack together a solution by downgrading to a specific version of Zoom. This apparently also required overriding this Zoom’s pipewire dependency to an earlier version as well.

His nixconfig is public, but it’s rather complex, with the relevant code spread across multiple files. I’d rather not try to mirror his solution exactly as it would add (what is for me at the moment) unnecessary complexity to my own configuration (plus, my puny brain can’t quite parse all that is going on there).

I’m instead looking for some guidance on how accomplish what gvolpe achieved within a single nix file that can be imported by home-manager. It did not seem appropriate to pollute the GitHub issue with such a request which is why I’m pestering people in this forum

My hope is that, if we come to some solution, this could be a nice drop-in fix for others in the same boat.

Here was my first attempt:

{
  config,
  lib,
  pkgs,
  inputs,
  ...
}: let
  # Last Zoom version with working Wayland screen sharing
  zoomVersion = "6.0.2.4680";

  # This is nixpkgs 24.05 from the flake input which has the required pipewire v1.0.7 for older Zoom
  stablePkgs = inputs.nixpkgs-stable.legacyPackages.${pkgs.system};

  zoom-us-custom = (pkgs.zoom-us.override {pipewire = stablePkgs.pipewire;}).overrideAttrs (oldAttrs: rec {
    version = zoomVersion;
    src = pkgs.fetchurl {
      url = "https://zoom.us/client/${version}/zoom_x86_64.pkg.tar.xz";
      hash = "sha256-027oAblhH8EJWRXKIEs9upNvjsSFkA0wxK1t8m8nwj8=";
    };
  });
in {
  home.packages = [
    zoom-us-custom
  ];

  # Without disabling xwayland, fonts are pixelated and look like 💩
  xdg.configFile."zoomus.conf" = {
    text = ''
      [General]
      xwayland=false
      enableWaylandShare=true
    '';
  };
}

Sadly, this didn’t work as Zoom crashes after signing in.
Commenting out the xdg.configFile section prevents the crashing, but the fonts look like junk under xwayland as the comment says. More importantly, screen sharing still doesn’t work
When I click 'Share Screen" I can then select either “use system desktop capture” or “use system window capture,” but nothing happens after choosing either one.

Any help would be most appreciated.
Thanks, everyone!

aos · August 8, 2024, 9:37pm

Sorry - accidentally deleted last post.

I assume you’re using flakes, judging by the inputs in your code. I got it working by doing this:

Grab the last nixpkgs hash with a working zoom:

inputs.nixpkgs-zoom.url = "github:NixOS/nixpkgs/06031e8a5d9d5293c725a50acf01242193635022";

Since you’re passing in inputs to your home-manager configuration, you can do something simple like so:

{
  config,
  pkgs,
  inputs,
  ...
}:

let
  zoomPkgs = import inputs.nixpkgs-zoom {
    system = "x86_64-linux";
    config.allowUnfree = true;
  };
in
{
  home.packages = with pkgs; [
    zoomPkgs.zoom-us
  ];
}

That should be one minimal way to get it up and running. You can of course do a lot of clean up on it (eg. passing in the zoomPkgs in directly into your home-manager module).

Notably - I didn’t have to make any changes to pipewire.

cgumb · August 8, 2024, 11:17pm

Thanks, aos!

After doing a rebuild/switch with the suggested change I’m afraid screen sharing behaves as before: I’m shown window vs desktop sharing options, but, once selected, nothing happens.
(note too the pixelated fonts as I assume this is defaulting to xwayland. This version of Zoom doesn’t seem to like the xwayland and enableWaylandShare options in the config and cause the home-manager service to fail on rebuild unless removed.)

I’m wondering if I might be missing something necessary in my overall config that you may have defined elsewhere. Perhaps in my compositor (Hyprland) config? Environment variables? As an example, in my hyprland config I have stuff like:

....
  home = {
    packages = with pkgs; [
      hyprpicker
      wdisplays
      wev
      wl-clipboard-rs
      lockscreen
      screenshot
      volume
      xdg-desktop-portal-hyprland
    ];

    sessionVariables = {
      MOZ_ENABLE_WAYLAND = 1;
      QT_WAYLAND_DISABLE_WINDOWDECORATION = 1;
      WLR_NO_HARDWARE_CURSORS = 1;
      CLUTTER_BACKEND = "wayland";
      XDG_SESSION_TYPE = "wayland";
      XDG_CURRENT_DESKTOP = "Hyprland";
      XDG_SESSION_DESKTOP = "Hyprland";
      WLR_BACKEND = "gl"; # No GPU :'(
      QT_QPA_PLATFORM = "wayland";
      GDK_BACKEND = "wayland";
      NIXOS_OZONE_WL = 1;
      ELECTRON_OZONE_PLATFORM_HINT = "auto";
    };
  };

  xdg.portal = {
    enable = true;
    extraPortals = with pkgs; [
      xdg-desktop-portal-hyprland
    ];
    config.common.default = "*";
  };

  wayland.windowManager.hyprland = {
    enable = true;
    systemd.enable = true; # TODO

    settings = {
      exec-once = [
        "swww-daemon"
        "swww img ~/.local/share/bg/wallpaper.jpg"
        "nm-applet --indicator"
        "waybar"
        "dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP"
        "systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP"
      ];
...

Granted, many of those things are done out of ‘superstition’ as I’ve thrown things together based on various forum posts, github repos, and the command of my AI overlords.

Also, If it matters, I can confirm that the pipewire, pipeware-pulse, and xdg-desktop-portal-hyprland services are running.

I do appreciate the help and I’m sure hammering this out will be useful to other drones like me whose jobs require them to use unfree malware Zoom

aos · August 9, 2024, 4:29am

I’m also running Hyprland. I do also have xdg-desktop-portal-gtk under extraPortals, but I’m not sure that’s needed. My config looks pretty similar to yours, here is the userland part: nix-config/modules/nixos/userland.nix at 627765622f6e57af944de4b926bfc22dac61518d · aos/nix-config · GitHub

Maybe the only difference is that my Hyprland is the nixosModule, vs. yours being the home-manager module. But I don’t think that should make a big difference.

It seems like your issue is the pop-up window selector for what to share doesn’t come up at all.

gvolpe · August 16, 2024, 3:15pm

I wouldn’t mind a ping, happy to help

Your first attempt looks good to me, I’ve only got two suggestions:

Make sure the stablePkgs instance is pinned to the exact revision I have, to at least discard this difference.
Remove the zoomus.conf settings, let the zoom client modify that file as it pleases, and you can also edit it manually to fix those pixel issues.

A few more relevant things I have on that file that are not committed to the repo:

enableWaylandShare=false
xwayland=true

Hope that helps! I’ve been using it without issues on Hyprland since that downgrade, hopefully the Zoom folks get their s**t together and fix the client on Wayland once and for all

existensil · September 3, 2024, 5:09pm

Gnome user here. Just wanted to confirm that following some of the steps above and using nix-versions I was able to bring back screen sharing using the following config details. I didn’t need any zoomus.conf entries.

{ config, pkgs, ... }:
let
  pinnedZoomPkgs = import (builtins.fetchTarball {
      url = "https://github.com/NixOS/nixpkgs/archive/0c19708cf035f50d28eb4b2b8e7a79d4dc52f6bb.tar.gz";
      sha256 = "0ngw2shvl24swam5pzhcs9hvbwrgzsbcdlhpvzqc7nfk8lc28sp3";
  }) {
    system = "x86_64-linux";
    config.allowUnfree = true;
  };

  pinnedZoom = pinnedZoomPkgs.zoom-us;
in
{
  environment.systemPackages = [ pinnedZoom ];
}

freelock · December 1, 2024, 2:03am

Hi,

I have a ticket with Zoom trying to resolve this. The latest from their engineering team:

Can you find this shared library libpipewire.so and add its path to the environment variable LD_LIBRARY_PATH to see if it works? We use this lib to find related components and dependencies. The Engineer believes it should work when it is added to that path.

… I’ve done some modifications to the zoom derivation, and I do have pipewire added as a lib. However, in the pipewire derivation, I’m finding a libpipewire-0.3.so, but not a libpipewire.so. I’m wondering if I can add that to the Pipewire derivation somehow?

Here’s what I see in the lib added to Zoom’s LD_LIBRARY_PATH:

❯ ls /nix/store/mhp5jkwqgyz0s7klvpl23x3axgvn6msm-pipewire-1.2.6/lib -la
total 1208
dr-xr-xr-x  1 root root     232 Dec 31  1969 .
dr-xr-xr-x  1 root root      22 Dec 31  1969 ..
dr-xr-xr-x  1 root root     128 Dec 31  1969 alsa-lib
dr-xr-xr-x  1 root root      34 Dec 31  1969 gstreamer-1.0
lrwxrwxrwx 12 root root      20 Dec 31  1969 libpipewire-0.3.so -> libpipewire-0.3.so.0
lrwxrwxrwx  3 root root      27 Dec 31  1969 libpipewire-0.3.so.0 -> libpipewire-0.3.so.0.1206.0
-r-xr-xr-x  2 root root 1228520 Dec 31  1969 libpipewire-0.3.so.0.1206.0
dr-xr-xr-x  1 root root    3138 Dec 31  1969 pipewire-0.3
dr-xr-xr-x  1 root root     234 Dec 31  1969 spa-0.2
dr-xr-xr-x  1 root root      20 Dec 31  1969 systemd
dr-xr-xr-x  1 root root      14 Dec 31  1969 udev

… I tried just adding a symlink there but of course it’s a read-only file system, so that didn’t work.

Should I tell Zoom to look for libpipewire-0.3.so instead, or is there a quick way to add this to nixpkgs to patch it locally?

I’m still getting up to speed on Nix – I am using a local clone of nixpkgs and building it with nix-build -A zoom-us after playing around with different things in the zoom.drv…

freelock · December 1, 2024, 2:10am

P.S. For those who need it to work today, we’ve simply pulled in the nixpkgs-stable version of the zoom-us package, which still has Zoom 6.0.2, where screensharing still works fine with Wayland. I guess now we might need to change that to 24.05…