Nixpkgs: zoom-us: Sign In with SSO hangs on "Connecting..."

[rossabaker]

Describe the bug
After entering the domain for Sign In with SSO and clicking "Continue", the zoom window turns white with message "Connecting...", and never finishes. After closing and restarting zoom, the application starts back up as "Connecting..." until the ~/.zoom directory is removed. Sign In with SSO still doesn't work.

To Reproduce
Steps to reproduce the behavior:

1. Run zoom-us
2. Click "Sign in"
3. Click "Sign in with SSO"
4. Enter domain and click "Continue"
5. Observe "Connecting..."
6. Close zoom window.
7. Run zoom-us
8. Observe "Connecting..."
9. Close zoom window.
10. rm -r ~/.zoom
11. Run zoom-us
12. Back to Step 2: Sign In button is available, but won't work.

Expected behavior
After step 4, a browser should launch to complete the single sign in.

Additional context
embeddedBrowserForSSOLogin in ~/.config/zoomus.conf defaults to true. The behavior is unchanged if I set this variable to false and relaunch. xdg-open is never called.

embeddedBrowserForFacebookLogin and embeddedBrowserForGoogleLogin both default to false. When clicked, the Facebook and Google signins invoke xdg-open http://, resulting in an empty browser window. When those variables are set to true, xdg-open is not invoked, and the zoom window closes without presenting a browser. The application remains open and the tray is responsive, but there is no signin. The workaround in #69352 does not work for me.

All three login methods work on Debian Stable.

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 5.3.8, NixOS, 20.03.git.c1966522d7d (Markhor)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.1`
 - channels(root): `""`
 - nixpkgs: `/nix/store/4pir570j86g0byq1pchcgfh845gigihx-nixpkgs`

My nixpkgs is pinned to c1966522d7d5fa54db068140d212cba18731dd98.

[veprbl]

cc @danbst @tadfisher

[danbst]

Confirmed. My best guess is that we should use back the provided Qt libraries (currently we use Nixpkgs Qt).

[danbst]

A bit of progress. Figured out this is because Zoom requires Qt 5.9, but it was removed entirely in https://github.com/NixOS/nixpkgs/pull/73261. The last working remnants of Qt 5.9 are left in nixos-19.09, which can be used to resurrect Zoom:

  # suitable for overlay
  zoom-us-resurrected = let
    oldpkgs = import (fetchTarball "https://github.com/nixos/nixpkgs/archive/release-19.09.tar.gz") {};
    qt59 = oldpkgs.qt59;
    mkLibsForQt5 = oldpkgs.mkLibsForQt5;
    libsForQt59 = recurseIntoAttrs (lib.makeScope qt59.newScope mkLibsForQt5);
  in libsForQt59.callPackage <nixpkgs/pkgs/applications/networking/instant-messengers/zoom-us> { };

I'm pretty sure that fix for https://github.com/NixOS/nixpkgs/issues/74273 is incorrect, because it should rather use Qt 5.9, not latest Qt. @adisbladis I think this is exactly the case when compatibility unexpectedly breaks.

[adisbladis]

@danbst Qt has a stable ABI, any binary linked against a 5.x release is compatible with newer 5.x releases, re-linking Zoom against 5.12 is fine.

[dtzWill]

On Mon, 16 Dec 2019 03:47:37 -0800, adisbladis [e-mail] wrote:

@danbst Qt has a stable ABI, any binary linked against a 5.x release is compatible with newer 5.x releases, re-linking Zoom against 5.12 is fine.

I'm not saying you're wrong,
and I don't know what the explanation is "yet",
but something is going on...

I can confirm that while zoom-us on nixos-unstable
doesn't work w/SSO (this issue) the proposed overlay-esque
produced a zoom-us that does work. (?!)

Here's what I used succcessfully this morning
(for a meeting ending ~10 min ago :D):

{
  # suitable for overlay
  zoom-us-resurrected = let
    oldpkgs = import (fetchTarball channel:nixos-19.09) {};
    qt59 = oldpkgs.qt59;
    mkLibsForQt5 = oldpkgs.mkLibsForQt5;
    libsForQt59 = oldpkgs.recurseIntoAttrs (oldpkgs.lib.makeScope qt59.newScope
mkLibsForQt5);
  in libsForQt59.callPackage
<nixpkgs/pkgs/applications/networking/instant-messengers/zoom-us> { };
}

Which I put in a file zoom.nix and built it with nix build -Lf zoom.nix.
(I think it could be dropped in an overlay folder, but didn't try yet)

My <nixpkgs> is my own tree (eep), actually but is largely master but messier O:).

(given it worked for person posting the snippet, I doubt the differences matter?
but LMK if re-testing would help anything :))

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/73532#issuecomment-566028236Non-text part: text/html

[pbogdan]

Was looking into a different issue today (https://github.com/NixOS/nixpkgs/issues/75903) but FWIW from a quick check I can also confirm what poster above is seeing when comparing latest zoom linked against QT 5.9 libraries from current 19.09 vs zoom from unstable.

[rossabaker]

Trying again, on zoom 3.5.361976.0301 from nixpkgs a2e06fc3423c4be53181b15c28dfbe0bcf67dd73, I can set embeddedBrowserForSSOLogin=false in ~/.config/zoomus.conf and sign in through Chrome. The xdg-open dialog pops up in Chrome, but the Zoom window continues to spin on "Connecting..."

I can then kill zoom, and run xdg-open $ZOOMMTG, where $ZOOMMTG is the zoommtg:// URI from the "Launch Zoom" button in the browser.

xdg-open through the browser works when following calendar invites to join meetings, but not yet on this. But I can successfully sign in now, with those workarounds.

[ConnorNovak]

I had this same issue:

• Ubuntu 16.04
• Latest Zoom .deb file for Ubuntu (as of 2020-04-01)
  When I tried to sign in with SSO, Zoom window would switch to "Connecting" and open a new window with a long random alphanumeric key printed in it, but hang there.
  Solution:
  Set embeddedBrowserForSSOLogin in ~/.config/zoomus.conf to false. Able to log in with SSO.

[felixgolcher]

rossabaker's proposal works for me with zoom 3.5.385850.0413 on ubuntu 19.04. Thank you so much.

[stale[bot]]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.

[kennyballou]

I'm still having this issue with the zoom-us version 5.3.469451.0927 and the work around using xdg-open is not working either.

In the latter case, I receive the following error after my token address: "The specified location is not supported".

I have not tried creating a custom override for zoom, but I may try that later.

[kennyballou]

zoom-us from nixpkgs.unstable (cfed29bfcb28259376713005d176a6f82951014a) seems to work for me.

The option for toggling the embedded browser does not seem to do anything.