My first shot at it allows me to enable pipewire support in chrome://flags, but makes the browser crash when actually trying to share a window in a WebRTC application (e.g. meet.jit.si). I'm seeing the following messages on stderr with verbose logging:
[71968:71968:0426/182013.480562:INFO:base_capturer_pipewire.cc(914)] Created proxy for the screen cast portal. [71968:71968:0426/182013.480603:INFO:base_capturer_pipewire.cc(952)] Screen cast session requested. [71968:71968:0426/182013.500256:INFO:base_capturer_pipewire.cc(977)] Initializing the screen cast session. [71968:71968:0426/182013.500274:INFO:base_capturer_pipewire.cc(992)] Subscribing to the screen cast session. [71968:71968:0426/182013.500648:INFO:base_capturer_pipewire.cc(1007)] Received response for the screen cast session subscription. [71968:71968:0426/182013.500685:INFO:base_capturer_pipewire.cc(1047)] Requesting sources from the screen cast session. [71968:71968:0426/182013.501519:INFO:base_capturer_pipewire.cc(1073)] Sources requested from the screen cast session. [71968:71968:0426/182013.501530:INFO:base_capturer_pipewire.cc(1088)] Subscribed to sources signal. [71968:71968:0426/182013.501759:INFO:base_capturer_pipewire.cc(1103)] Received sources signal from session. [71968:71968:0426/182013.501780:INFO:base_capturer_pipewire.cc(1133)] Starting the screen cast session. [71968:71968:0426/182013.502497:INFO:base_capturer_pipewire.cc(1160)] Initializing the start of the screen cast session. [71968:71968:0426/182013.502507:INFO:base_capturer_pipewire.cc(1176)] Subscribed to the start signal. … [71968:71968:0426/182020.558054:INFO:base_capturer_pipewire.cc(1191)] Start signal received. [71968:71968:0426/182020.558108:INFO:base_capturer_pipewire.cc(1236)] Opening the PipeWire remote. [E][pipewire.c:343 add_interface()] can't get Spa:Pointer:Interface:Log interface -2 [E][pipewire.c:343 add_interface()] can't get Spa:Pointer:Interface:CPU interface -2 [E][loop.c:85 pw_loop_new()] loop 0x55c5b2b74ee0: can't make support.system handle: No such file or directory … Erreur de segmentation (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: In Progress Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
