Introducing the new Zoom Community Champion Program where we recognize our most engaged community members for their contributions.Learn more and join
Everything you need to work together, all in one place.Explore Zoom One's Collaboration Tools
Innovative video solutions for every meeting space.
Solutions to host impactful virtual and hybrid experiences.
An omnichannel cloud solution optimized for video.
Zoom solutions elevate collaboration across vertical use cases.Discover Zoom Industry Solutions
Enabling exciting new ways to teach, learn, and connect globally
Transforming client engagement and employee experiences
Improving collaboration between agencies, ministries and constituents
Connecting care, collaboration, and medical innovation
Real-time communication, anywhere in the world
Bridging the in-store and online experiences
Expert support and services for all your design, strategy, implementation, event, and hardware needs.
An open platform that allows developers to build Zoom apps and integrations.
Explore over 1,500 apps in Zoom App Marketplace
Documentation for building on Zoom's platform using APIs, Webhooks, and SDKs
Resources that help developers evaluate & build with our solutions
Post your questions and get help from our developer community
Zoom Partners bring Zoom's communications platform to market through alliance, sales, and service partnerships.
Discover new ways to use Zoom solutions to power your modern workforce.
Access expert-led tutorials on Zoom products and features.
Network with other Zoom users, and share your own product and industry insights.
Get documentation on deploying, managing, and using the Zoom platform.
I am on debian testing and when I try to share my screen I get the message:
"Can not start share, we only support Wayland on GNOME with Ubuntu 17 and above, Fedora 25 and above, Debian 9 and above, ......" "If your OS is not on the list, please use x11 instead".
I am on testing which is forward from Debian 11, so it should be supported. I am using gnome/wayland. It sounds like it might just not be recognizing the version number?
I have confirmed this is the issue. I added a line to /etc/os-release :
This is reflected in `lsb_release`:
$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux bookworm/sid Release: 12 Codename: bookworm
Now that screen goes away, but I do not have the option to share a full screen, only a selected portion of the screen.
For more context, Zoom incorrectly implemented their screensharing on modern gnu+linux distributions which use Wayland. Zoom did not introduce Wayland support until March 1, 2020 version 3.5.361976.0301. This was broken upon release because they did not use the correct API (gdbus-org.freedesktop.portal.ScreenCast) which has been available since early 2018: https://github.com/flatpak/xdg-desktop-portal/releases/tag/0.10. This resulted in issues for multi-monitor setups, problems with HiDPI screens, unusable performance, and other glitches from the beginning, and now it is broken completely.
Many users are switching to affordable, reliable, backed-by-open-source options like https://8x8.vc, powered by Jitsi (plus, they didn't lie to their users about end-to-end encryption and get sued). The screenshot API exists only for the system to take screenshots (of course). It is very inefficient for video but what's worse is it is also completely insecure because in order for it to be publicly enabled, applications have full access to record your entire screen without explicit permission.
The correct API was designed for video, and gives the user control over sharing specific windows/apps or the entire screen, so no app gets to spy on your screen without your permission. So when Zoom created their implementation they used the wrong API, and for the almost two years since then Zoom still didn't update, ignored the users with issues, did not monitor for deprecating APIs, and did not test upcoming gnu+linux distributions like Fedora to see that the API they use was incorrect, long been deprecated, and imminently disabled. This left many users and developers to do the testing and investigation for them, but still took nine months to be recognized. Finally, they are working on this now, so we will see how long the fix takes.