GNU bug report logs -
#53301
Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53301 in the body.
You can then email your comments to 53301 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#53301
; Package
guix
.
(Sun, 16 Jan 2022 10:28:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jacob Hrbek <kreyren <at> rixotstudio.cz>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 16 Jan 2022 10:28:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (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 2 (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)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53301
; Package
guix
.
(Sun, 16 Jan 2022 10:33:01 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Created wiki entry about the issue
https://guix.miraheze.org/wiki/Packages/Chromium
On 1/16/22 11:27, Jacob Hrbek wrote:
>
> 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 Me
ssage --------
> 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 anyone 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
--
Jacob Hrbek
[Message part 2 (text/html, inline)]
[2022-01-16_10-59.png (image/png, inline)]
[publickey - kreyren@rixotstudio.cz - 1677db82.asc (application/pgp-keys, attachment)]
[signature.asc (application/pgp-signature, attachment)]
Reply sent
to
Marius Bakke <marius <at> gnu.org>
:
You have taken responsibility.
(Mon, 17 Jan 2022 17:37:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jacob Hrbek <kreyren <at> rixotstudio.cz>
:
bug acknowledged by developer.
(Mon, 17 Jan 2022 17:37:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 53301-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (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)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 15 Feb 2022 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 64 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.