GNU bug report logs - #53301
Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Marius Bakke <marius <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#53301: closed (Ungoogled-chromium lacks VP8 codec support
 preventing jitsi screensharing)
Date: Mon, 17 Jan 2022 17:37:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 17 Jan 2022 18:35:56 +0100
with message-id <87v8yi6z9f.fsf <at> gnu.org>
and subject line Re: bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing
has caused the debbugs.gnu.org bug report #53301,
regarding Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
53301: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53301
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Jacob Hrbek <kreyren <at> rixotstudio.cz>
To: bug-guix <at> gnu.org
Cc: yasu <at> yasuaki.com
Subject: Ungoogled-chromium lacks VP8 codec support preventing jitsi
 screensharing
Date: Sun, 16 Jan 2022 10:27:23 +0000

[Message part 3 (text/plain, inline)]

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 <at> rixotstudio.cz>

To: 	help-guix <at> 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

[Message part 4 (text/html, inline)]

[2022-01-16_10-59.png (image/png, inline)]

[chromium.tar.gz (application/gzip, attachment)]

[publickey - kreyren@rixotstudio.cz - 1677db82.asc (application/pgp-keys, attachment)]

[signature.asc (application/pgp-signature, attachment)]

[Message part 9 (message/rfc822, inline)]

From: Marius Bakke <marius <at> gnu.org>
To: Jacob Hrbek <kreyren <at> rixotstudio.cz>, 53301-done <at> debbugs.gnu.org
Cc: yasu <at> yasuaki.com
Subject: Re: bug#53301: Ungoogled-chromium lacks VP8 codec support
 preventing jitsi screensharing
Date: Mon, 17 Jan 2022 18:35:56 +0100

[Message part 10 (text/plain, inline)]

Jacob Hrbek <kreyren <at> rixotstudio.cz> skriver:

> 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:

Fixed in f3b73e46df82297ffabaa3b32fc765fa3065cad0.

Thanks for the report and reproducer!

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.