Sharing in Wayland Works Only The First Time | Community
Skip to main content
C
Newcomer
Comara
Newcomer
September 22, 2025
Question

Sharing in Wayland Works Only The First Time

  • September 22, 2025
  • 8 replies
  • 89 views

Currently using Arch Linux with Wayland.  With the latest zoom installed (6.6.0), using pipewire for sharing.  The first time I try to share a screen or window, it works fine.  If I stop sharing and try to share again, it only shares a completely black window or screen.  

Immediately after I stop sharing the first time, I get the following messages in ~/.zoom/logs/zoom_stdout_stderr.log

*** pw_stream_set_active called from wrong context, check thread and locking: Operation not permitted
*** impl_ext_end_proxy called from wrong context, check thread and locking: Operation not permitted
'this->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:62 do_unlock()

I cannot figure out if this is a zoom problem or a pipewire problem.

Everything works fine in X11.

    8 replies

    T
    Newcomer
    tkalfaoglu
    Newcomer
    October 9, 2025

    It's a zoom problem - if you quit zoom and restart, it works again. Once. 

    U
    Newcomer
    uarizona_casey
    Newcomer
    October 22, 2025

    I have the same issue, having to close zoom/re-join a meeting should not be necessary to screen share again.

    C
    Newcomer
    ComaraAuthor
    Newcomer
    October 22, 2025

    One way to fix this particular problem is to edit ~/.config/zoomus.conf and change the line xwayland=true to false.

    This will cause several other issues including one where it will crash zoom if you try to stop a cloud recording.

    What I've done now instead to make life better and not have to use X11 is to switch to using the Zoom browser app only.  I'm using the plugin Xoom Redirector in chrome so that whenever I click on my zoom meetings it launches in the browser instead of the local app.  This is a good fix until Zoom can figure out the issues with their Linux client.

      M
      Newcomer
      mikus
      Newcomer
      October 24, 2025

      I'm running into this problem on Arch as well, though restarting Zoom doesn't fix the issue. The only reliable way I've found is to kill zoom, xdg-* processes, and pipewire. Others report gutting pipewire for pulseaudio fixed things, so pipewire+xdg-portal seem to be mostly the issue here as this affects teams the same way, but Arch+KDE doesn't let me remove pipewire for depenencies anymore.

        R
        Newcomer
        ralmond
        Newcomer
        November 3, 2025

        I'm getting very similar results in Pop_OS 22.04 using either Cosmic or Gnome/Wayland as my desktop.

        Zoom 6.6.0 and Pipewire 1.4.2-1pop1~1750269419~24.04~e495013.

         

        I can turn screen sharing on and off in OBS, so I'm guessing its a zoom issue.

        W
        Newcomer
        wskel
        Newcomer
        November 11, 2025

        I'm able to share in Chrome only. Firefox doesn't work due to https://community.zoom.com/t5/Zoom-Meetings/Can-t-share-my-screen-on-firefox/m-p/99766.

         

        Google Meet works in both browsers, as does Slack (Flatpak).

         

        Zoom 6.6.6.5306
        openSUSE Tumbleweed 20251109
        6.17.7-1-default
        kwin 6.5.2
        pipewire
        Compiled with libpipewire 1.5.81
        Linked with libpipewire 1.5.81

        R
        Newcomer
        rnmaiven
        Newcomer
        December 3, 2025

        Same story on Fedora 43 (GNOME 49) and CachyOS with GNOME shell, where X11 doesn't exist. I also have the same problem on Fedora 42, no matter what settings I choose (or config I edit in zoomus.conf). Auto, Pipewire, XWayland, doesn't seem to matter. First screen share works fine, subsequent screen shares either result in a black screen, or crash the app, or crash GNOME shell entirely.

         

        Version 6.6.11 (6052)

        Using the official .rpm download on Fedora and the pacman package on Arch. The unofficial Flatpak doesn't work any better.

         

         

        R
        Newcomer
        rnmaiven
        Newcomer
        December 4, 2025

        Some more info from the log output (on startup and then after the second screen share fails):

        Linux Client Version is 6.6.11 (6052) QSG_RENDER_LOOP is XDG_CURRENT_DESKTOP = GNOME; DESKTOP_SESSION = gnome; XDG_SESSION_TYPE = wayland [xdg-desktop-portal info]: xdg-desktop-portal: xdg-desktop-portal 1.20.3 find 'xdg-desktop-portal-gnome' can not find 'xdg-desktop-portal-kde' command find 'xdg-desktop-portal-gtk' can not find 'xdg-desktop-portal-hyprland' command can not find 'xdg-desktop-portal-lxqt' command can not find 'xdg-desktop-portal-wlr' command can not find 'xdg-desktop-portal-xapp' command [portal info] : gnome-keyring.portal gnome.portal gtk.portal kwallet.portal [pipewire info] : pipewire Compiled with libpipewire 1.4.9 Linked with libpipewire 1.4.9 Graphics Card Info:: 01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1) 10:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c6) .... QOpenGLFramebufferObject: Framebuffer incomplete attachment. QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment. qt.scenegraph.general: Using sg animation driver qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms qt.scenegraph.general: opengl texture atlas dimensions: 512x512 QCoreApplication::postEvent: Unexpected null receiver *** pw_stream_set_active called from wrong context, check thread and locking: Operation not permitted *** impl_ext_end_proxy called from wrong context, check thread and locking: Operation not permitted 'this->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:62 do_unlock() .... [17295:17295:1204/105518.483435:ERROR:services/on_device_model/ml/gpu_blocklist.cc:120] Unable to get gpu adapter [16062:16062:1204/105518.483589:ERROR:services/on_device_model/public/cpp/service_client.cc:36] Unexpected on_device_model service disconnect: The device's GPU is not supported.

         Happy to provide the full output privately if Zoom support wants to reach out.

        Z
        Newcomer
        zacharye
        Newcomer
        December 26, 2025

        Same issue. The screen sharing seems to only start working again by completely rebooting Zoom.

        Tested on both the Flatpak and AUR versions
        Zoom Version 6.7.0

        Terms & ConditionsAccessibility statement
        Copyright © Zoom Communications, Inc. All rights reserved.