From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: chromium: enable WebRTC screen sharing via PipeWire
Date: Sun, 13 Dec 2020 22:42:54 +0100 [thread overview]
Message-ID: <20201213214254.R_Kc2WhJwa66bGYmjsHIv1aLVLeasYhMnH8Opqwovj4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26144@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
There's a closed pull request on the void-packages repository
chromium: enable WebRTC screen sharing via PipeWire
https://github.com/void-linux/void-packages/pull/26144
Description:
[ci skip]
- [x] libpipewire0.2
- [x] patch chromium's template
- [ ] test for all supported archs:
- [x] x86_64 - works for Chromium 87: https://github.com/void-linux/void-packages/pull/26144#issuecomment-731759815 & 86: https://youtu.be/AgyxEC7SfGk
- [ ] i686 - works for Chromium 86: https://youtu.be/j0MY9C1CwV4
- [x] x86_64-musl - works for Chromium 87: https://youtu.be/ZJorRl_7Sh4
There are minor issues though:
* you have to kill `xdg-desktop-portal*` processes sometimes, probably caused by some sort of race condition;
* also you may need to start/restart screensharing for it to work.
✔️ https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing
✔️ https://zoom.us (in-browser version)
✔️ https://discord.com (in-browser version)
Currently I'm investigating these stability issues with `pipewire`. It seems that `pipewire` is trying to use `rtkit` to make audio/video processing run in real time. Unfortunately, it fails to do so:
```
2020-11-16T03:49:59.73350 daemon.err: Nov 16 03:49:59 rtkit-daemon[3165]: Failed to make ourselves RT: Function not implemented
2020-11-16T03:49:59.73602 daemon.warn: Nov 16 03:49:59 rtkit-daemon[3165]: Warning: failed to read scheduler policy: Function not implemented
2020-11-16T03:49:59.73620 daemon.debug: Nov 16 03:49:59 rtkit-daemon[3165]: Supervising 0 threads of 0 processes of 1 users.
2020-11-16T03:49:59.73645 daemon.debug: Nov 16 03:49:59 rtkit-daemon[3165]: Supervising 0 threads of 0 processes of 1 users.
2020-11-16T03:49:59.74118 daemon.err: Nov 16 03:49:59 rtkit-daemon[3165]: Failed to make ourselves RT: Function not implemented
```
After a bit of searching, I've found these bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1229700
https://bugs.gentoo.org/show_bug.cgi?id=569546
I've built `linux5.9` for `x86_64` with `CONFIG_RT_GROUP_SCHED` disabled.
For some strange reason, nothing changed, the error persists. Luckily, screen sharing works without `rtkit`.
I guess that those rare issues with screen sharing, which were described above, may be caused by `rtkit` not working.
prev parent reply other threads:[~2020-12-13 21:42 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 3:49 [PR PATCH] chromium: enable Logarithmus
2020-11-05 4:25 ` [PR PATCH] [Updated] chromium: enable WebRTC screen sharing via PipeWire Logarithmus
2020-11-05 4:25 ` Logarithmus
2020-11-05 4:38 ` Logarithmus
2020-11-11 1:43 ` Logarithmus
2020-11-11 2:13 ` Logarithmus
2020-11-11 3:02 ` Logarithmus
2020-11-13 20:33 ` Logarithmus
2020-11-15 7:50 ` Logarithmus
2020-11-15 22:06 ` Logarithmus
2020-11-16 1:08 ` Logarithmus
2020-11-16 4:00 ` Logarithmus
2020-11-16 4:44 ` Logarithmus
2020-11-16 14:12 ` Logarithmus
2020-11-16 14:15 ` Logarithmus
2020-11-17 14:53 ` Logarithmus
2020-11-18 4:16 ` Logarithmus
2020-11-18 4:20 ` Logarithmus
2020-11-19 5:41 ` [PR PATCH] [Updated] " Logarithmus
2020-11-19 20:40 ` [PR PATCH] [Updated] [ci skip] chromium: update to 87.0.4280.66 & " Logarithmus
2020-11-19 21:54 ` Logarithmus
2020-11-20 1:02 ` [PR PATCH] [Updated] chromium: " Logarithmus
2020-11-20 21:26 ` Logarithmus
2020-11-21 0:59 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21 1:00 ` Logarithmus
2020-11-21 1:03 ` ericonr
2020-11-21 1:15 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21 1:35 ` Logarithmus
2020-11-21 1:46 ` Logarithmus
2020-11-21 1:53 ` Logarithmus
2020-11-21 1:54 ` Logarithmus
2020-11-21 1:54 ` Logarithmus
2020-11-21 1:57 ` Logarithmus
2020-11-21 1:57 ` Logarithmus
2020-11-21 1:57 ` Logarithmus
2020-11-21 1:59 ` Logarithmus
2020-11-21 2:00 ` ericonr
2020-11-21 2:08 ` Logarithmus
2020-11-21 2:08 ` Logarithmus
2020-11-21 2:08 ` Logarithmus
2020-11-21 2:10 ` Logarithmus
2020-11-21 2:28 ` [PR PATCH] [Updated] " Logarithmus
2020-11-21 2:29 ` Logarithmus
2020-11-21 11:17 ` ifreund
2020-11-21 11:44 ` Logarithmus
2020-11-21 11:44 ` Logarithmus
2020-11-21 12:33 ` ifreund
2020-11-21 12:34 ` ifreund
2020-11-21 13:21 ` Logarithmus
2020-11-21 13:22 ` Logarithmus
2020-11-21 13:23 ` Logarithmus
2020-11-21 19:04 ` ifreund
2020-11-22 14:52 ` ifreund
2020-12-03 7:10 ` [PR PATCH] [Updated] " Logarithmus
2020-12-13 21:42 ` Logarithmus
2020-12-13 21:42 ` Logarithmus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201213214254.R_Kc2WhJwa66bGYmjsHIv1aLVLeasYhMnH8Opqwovj4@z \
--to=logarithmus@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).