From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: 53301@debbugs.gnu.org
Cc: yasu@yasuaki.com
Subject: bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing
Date: Sun, 16 Jan 2022 10:27:23 +0000 [thread overview]
Message-ID: <57e235e0-7709-6093-2224-758179451c63@rixotstudio.cz> (raw)
In-Reply-To: <0281fe35-281c-5137-b28d-6920acc6c614@rixotstudio.cz>
[-- Attachment #1.1.1: Type: text/plain, Size: 3250 bytes --]
See forwarded message
Steps to reproduce:
0. Get ungoogled-chromium
1. Open a call on jitsi e.g. https://jit.si/ILoveKreyren2Much
2. Start a screenshare
3. Join the call from a different browser and expect the screenshare to
malfunction either with tab crashing with "Aw, snap" or the screen share
changing on black screen and chromium printing this to the console:
[18990:23:0116/111829.036853:ERROR:webrtc_video_engine.cc(3446)] Absent
receive stream; ignoring clearing encoded frame sink for ssrc 0
[18990:12:0116/111836.246422:ERROR:video_stream_encoder.cc(1827)] Failed
to encode frame. Error code: -7
[18990:12:0116/111834.601625:ERROR:video_stream_encoder.cc(1149)] Failed
to initialize the encoder associated with codec type: VP8 (1)
I assume that we need to include VP8 codec
-------- Forwarded Message --------
Subject: Re: Jitsi Meet Screen Sharing with Ungoogled-Chromium
Date: Sun, 16 Jan 2022 11:24:28 +0100
From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: help-guix@gnu.org
> Third party not a guix package
Those are not supported by GNU Guix and will be met with hostility,
because how dare you unfree scum!
---
Good thing that i ain't a bad person.. not part of GNU Guix to help! :p
Last time i tried it it worked out-of-the-box for me, i tested it now
again and also works without problem
GNU Guix (374fea0f3bc8035f626cb29e6045130df9ffdaf8) with
ungoogled-chromium-97.0.4692.71-1
Which was tested on the https://meet.jit.si instance.. Provide a
javascript console log which should have an explanation for this
failure.. My current hypothesis is that your chromium doesn't provide a
sufficient/sane TURN server and so jitsi crashes.
See
https://serverfault.com/questions/591837/how-does-chrome-webrtc-select-which-turn-server-to-use-if-multiple-options-are-g
on how to change the turn server.
..and to comply with GNU FSDG i have to tell you that using
non-ungoogled chromium and 3rd party repos is
unethical as it most
likely contains nonfree blobs which limit user freedom and contain
malware as such i am providing content of ~/.config/chromium in
attachment which should make your chromium more libre and i am also
encouraging you to use ungoogled-chromium.
EDIT: I missed the part with screensharing x.x .. on mentioned chromium
it starts printing:
[18990:23:0116/111829.036853:ERROR:webrtc_video_engine.cc(3446)] Absent
receive stream; ignoring clearing encoded frame sink for ssrc 0
[18990:12:0116/111836.246422:ERROR:video_stream_encoder.cc(1827)] Failed
to encode frame. Error code: -7
[18990:12:0116/111834.601625:ERROR:video_stream_encoder.cc(1149)] Failed
to initialize the encoder associated with codec type: VP8 (1)
in the console when i have screenshare and when someone joins and the
screen share changes to a black screen so i believe that this is a bug
due to the lack of sufficient VP8 codec.
On 1/16/22 10:46, Yasuaki Kudo wrote:
> Is there any
one here who uses Jitsi Meet to share screens from Guix? Let me know!
>
> At least in version 90 of chromium (third party, not a guix package), it used to work.
>
> With the current ungoogled-chromium on Guix, the moment someone else connects to the Jitsi session, ungooogled-chromium dies with an 'aw, snap' message.
>
> -Yasu
--
Jacob Hrbek
[-- Attachment #1.1.2.1: Type: text/html, Size: 5851 bytes --]
[-- Attachment #1.1.2.2: 2022-01-16_10-59.png --]
[-- Type: image/png, Size: 85275 bytes --]
[-- Attachment #1.2: chromium.tar.gz --]
[-- Type: application/gzip, Size: 32491 bytes --]
[-- Attachment #1.3: publickey - kreyren@rixotstudio.cz - 1677db82.asc --]
[-- Type: application/pgp-keys, Size: 713 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2022-01-16 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 9:46 Jitsi Meet Screen Sharing with Ungoogled-Chromium Yasuaki Kudo
2022-01-16 10:24 ` Jacob Hrbek
2022-01-16 10:27 ` Jacob Hrbek [this message]
2022-01-16 10:30 ` bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing Jacob Hrbek
2022-01-17 17:35 ` Marius Bakke
2022-01-16 23:34 ` Jitsi Meet Screen Sharing with Ungoogled-Chromium Ricardo Wurmus
2022-01-17 2:34 ` Yasuaki Kudo
2022-01-16 10:34 ` Jacob Hrbek
2022-01-16 10:34 ` Remco
2022-01-16 11:25 ` Sergiu Ivanov
2022-01-16 12:26 ` Jacob Hrbek
2022-01-20 16:55 ` Remco
2022-01-21 15:23 ` Yasuaki Kudo
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=57e235e0-7709-6093-2224-758179451c63@rixotstudio.cz \
--to=kreyren@rixotstudio.cz \
--cc=53301@debbugs.gnu.org \
--cc=yasu@yasuaki.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.