Ubuntu – Screen sharing under wayland

chromiumgoogle-chromescreencastwayland

Has anyone got screensharing working under wayland using pipewire?

As far as I can tell, it should be possible to share the screen from Chrome / Chromium after installing the pipewire package and adding your user to the audio and video groups. Except that Chrom(e|ium) is still using libpipewire0.2 and Groovy only ships with libpipewire0.3.

Bonus points if you've made slack work.

"Switch back to Xorg" is not a viable answer here. Various things (notably pen input) don't work correctly (in my configuration, anyway) in Xorg and are not going to any time soon.

Best Answer

You can install this package manually but you will have to check for updates manually here.

First, download the deb file (assuming you are using the amd64 version of Ubuntu):

wget 'http://mirrors.kernel.org/ubuntu/pool/universe/p/pipewire/libpipewire-0.2-1_0.2.7-1_amd64.deb'

Then, install the package:

sudo apt install ./libpipewire-0.2-1_0.2.7-1_amd64.deb

Since libpipewire0.3 uses a totally different set of files, there should be no conflict.

Again, you will have to manually check for updates. The current version is 0.2.7-1. When you see a newer version, just click on "amd64" under "Architecture" and then you can either click on one of the mirrors to download the file or copy the link and paste it into the terminal to use the wget command to use the same method as above. Just make sure to use the correct filename with the apt command so that you don't install the wrong file (like an older downloaded version).

Finally, there is some additional information on the Archlinux wiki that you may want to check out where they mention that you might have to install xdg-desktop-portal and enable the chromium flag chrome://flags/#enable-webrtc-pipewire-capturer to get it to work.

Related Solutions

Ubuntu – No sound from Chrome, sound works fine in Firefox etc (13.10)

I had the same problem. It ended up being that my system was trying to put Chrome's sound through the HDMI even though the HDMI chord was not plugged in at the time. Presumably, this could happen with any audio output device. The sound settings Ubuntu offers didn't show this nor let me change it for the individual application, but pavucontrol did.

To install pavucontrol from the Terminal:

sudo apt-get install pavucontrol

To open pavucontrol from the Terminal:

pavucontrol

Select the "Playback" menu and make sure that you have it set to Show Applications. Now, start playing something from Google Chrome. It will show up there, and it will show what output device is being used for Google Chrome. Make sure it is set to the output device you are trying to use.

Ubuntu – screen recorder for GNOME with Wayland

Green Recorder claims to support Wayland.

How it works?

It uses the D-Bus API to connect to the built-in screencasting tool in GNOME Shell. It uses this to record video. To record audio, it launches an instance of ffmpeg in the background. After the recording is finished, it merges the two files into the WebM file.

For Xorg, it uses ffmpeg only for both audio and video.

By default, On Wayland only, Green Recorder uses the V8 encoder instead of the default V9 encoder in GNOME Shell because of the CPU & RAM consumption issue with V9. Which - now - should also give you better performance. On Xorg, each format uses its own default encoder.

You can install from "FOSS Project" teams's PPA by running the following commands:

sudo add-apt-repository ppa:fossproject/ppa
sudo apt update
sudo apt install green-recorder

Best Answer

Related Solutions

Ubuntu – No sound from Chrome, sound works fine in Firefox etc (13.10)

Ubuntu – screen recorder for GNOME with Wayland

How it works?

Related Question