Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zoom-us support notice for wayland screensharing - no longer can screenshare. #322970

Open
bashfulrobot opened this issue Jun 27, 2024 · 4 comments

Comments

@bashfulrobot
Copy link

Describe the bug

I recently updated to the latest zoom-us version, and when I try to screen share, I get a support notice stating:

Zoom Workplace
Can not start share, we only support Wayland on GNOME with Ubuntu 17 and above, Fedora 25 and above, Debian 9 and
above, CentOS 8 and above, OpenSUSE Leap 15 and above, Oracle Linux 8 and above, RHEL 8 and above, Mageia 7 and
above,Rocky 8 and above, Arch Linux, AnterGos, Manjaro. If your 0S is not on the list, please use x11 instead.

Steps To Reproduce

Steps to reproduce the behavior:

  1. install latest
  2. join meeting
  3. try to share screen

Expected behavior

A clear and concise description of what you expected to happen.

Be able to share my screen

Screenshots

If applicable, add screenshots to help explain your problem.

Screenshot from 2024-06-27 10-03-49

Additional context

I have noticed that the app crashes when notes are opened, and the sidebar just spins saying it is loading. I can work around that, and may install again to open separate tickets.

Notify maintainers

@danbst @tadfisher

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.6, NixOS, 24.11 (Vicuna), 24.11.20240624.2893f56`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.18.3`
 - nixpkgs: `/nix/store/bi5zxc0v5g6ylygdwyqzh280sccg3ykb-source`
@eclairevoyant
Copy link
Member

It's closed source software; what do you believe can be done here?

@bashfulrobot
Copy link
Author

I am reporting it for visibility. And I have seen other packages marked as broken - which might be an option.

@eclairevoyant
Copy link
Member

eclairevoyant commented Jun 28, 2024

Well it's not broken, nor can it be patched. At most someone might find a way to spoof the check using /etc/os-release or such, but that's not really part of the package itself.

@bashfulrobot
Copy link
Author

Okay, well, what I mean by "broken" is that "there is not full functionality with this package" (through no fault of the packagers or the packaging). I fully understand there is nothing to be done other than (if the packagers decide it is a good idea) to indicate limited functionality.

Simply visibility, as others may come here looking for a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants