• Bug#1105763: pipewire: Screen sharing using MS Teams does not work any

    From =?utf-8?q?Max_G=C3=B6rner?=@21:1/5 to All on Wed May 14 16:30:01 2025
    Package: pipewire
    Version: 1.4.2-1
    Severity: normal

    Dear Maintainer,

    for some weeks I am unable to use screen sharing in video conferences
    using MS Teams. This applies to Firefox, Chrome and the MS Teams PWA.

    Screen sharing used to work fine for several months before. I am not
    aware of any relevant changes to the system I could have made.

    In order to get some insights I started Google Chrome in a terminal to
    see some output. Below is the output that is produced when I start
    Chrome, visit teams.microsoft.com, start a test call, and try to do
    screen sharing.

    [0514/154506.166900:WARNING:chrome/app/chrome_main_linux.cc:80] Read channel stable from /opt/google/chrome/CHROME_VERSION_EXTRA
    Created TensorFlow Lite XNNPACK delegate for CPU. [359294:359307:0514/154527.366983:ERROR:services/network/p2p/socket_tcp.cc:331] Error when reading from TCP socket: -101
    [359224:359319:0514/154537.991896:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
    [359224:359317:0514/154537.991896:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
    [359224:359318:0514/154537.991906:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
    'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()

    In the application the error message I see is that "Chrome is unable to
    access camera."

    I tried to do screen sharing with Firefox and Jitsi which seemed to
    work. I also tried to start an KDE-X11 session, which did not help. The
    problem exists regardless of whether I use the laptops monitor or an
    external one.

    My system has set the environment variables WAYLAND_DISPLAY to wayland-0
    and XDG_CURRENT_DESKTOP to KDE. The packages xdg-desktop-portal, -gtk
    and -kde are installed.

    I am reporting the bug to pipewire due to the error message above. If
    another package is more suitable, I would appreciate if you could let me
    know, so I could report the bug there.


    -- System Information:
    Debian Release: trixie/sid
    APT prefers testing
    APT policy: (500, 'testing')
    Architecture: amd64 (x86_64)

    Kernel: Linux 6.14.5-bindeb-pkg-oldconfig+ (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    Versions of packages pipewire depends on:
    ii adduser 3.150
    ii init-system-helpers 1.68
    ii libpipewire-0.3-modules 1.4.2-1
    ii pipewire-bin 1.4.2-1

    pipewire recommends no packages.

    pipewire suggests no packages.

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Max =?utf-8?Q?G=C3=B6rner?=@21:1/5 to All on Fri May 16 10:00:01 2025
    I came across some user reports regarding Arch Linux [1], in which people describe experiences very similar to my own. It is said that using Firefox
    Beta resolves the issues.

    I am also able to share my screen using Firefox Beta again. However, the line

    'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()

    still appears when using Firefox Beta. I am not sure if this line indicates a bug anyway, but it does not seem to be the only cause.

    1: https://bbs.archlinux.org/viewtopic.php?id=305299

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)