Debian 上的 Wayland + Gnome + Pulseaudio 下的 WebRTC 屏幕共享被破坏

Debian 上的 Wayland + Gnome + Pulseaudio 下的 WebRTC 屏幕共享被破坏

我无法在 Debian 11 (bullseye) 上在 Brave、Google Chrome 或 Firefox 中运行的任何网络应用程序上进行屏幕共享。
这个WebRTC实验,我可以单击“屏幕共享”并出现对话框,我可以在其中选择一个窗口或整个屏幕。在这两种情况下,单击“共享”都会使 UI 滑回到“Chrome 标签页共享”并且日志显示:

xdg-desktop-por: Unhandled parent window type 
xdg-desktop-por: Failed to associate portal window with parent window 
xdg-desktop-por: Failed to start session: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to start screen cast: Couldn't connect pipewire context
brave-browser.desktop: [7627:7627:0410/165213.470354:ERROR:screencast_portal.cc(365)] Failed to start the screen cast session.
brave-browser.desktop: [7627:7627:0410/165213.470366:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 3

Pipewire 不是我的音频引擎(正如 所确认的$ pactl info),所以我不知道为什么它要尝试使用它,但由于我已经有一些 bullseye-backports 包,我想我会尝试使用来自 backports 的 pipelinewire 进行升级,+ xdg-桌面门户{,-gtk},但仍然没有运气。

chrome://flags/#enable-webrtc-pipewire-capturer当更改为“启用”和/或设置chrome://flags/#ozone-platform-hint为“Wayland”时,我得到相同的结果。以下是我安装的 pipeline-* 包:

gstreamer1.0-pipewire/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
libpipewire-0.3-0/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed]
libpipewire-0.3-common/bullseye-backports,bullseye-backports,now 0.3.65-2~bpo11+1 all [installed,automatic]
libpipewire-0.3-modules/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
pipewire-alsa/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
pipewire-audio-client-libraries/bullseye-backports,bullseye-backports,now 0.3.65-2~bpo11+1 all [installed]
pipewire-bin/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
pipewire-jack/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
pipewire-pulse/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed]
pipewire/bullseye-backports,now 0.3.65-2~bpo11+1 amd64 [installed,automatic]
libwireplumber-0.4-0/bullseye-backports,now 0.4.13-1~bpo11+1 amd64 [installed,automatic]
wireplumber/bullseye-backports,now 0.4.13-1~bpo11+1 amd64 [installed]

对于它的价值,我可以pipewire在终端中开始并尝试屏幕共享,行为会略有变化:我有一个灰色框,其中显示器将镜像在“共享”对话框中,我可以开始共享,但它实际上不会共享任何内容,日志是相同的,但不再出现“无法连接管道上下文”这一行。

相关内容