all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Jacob Hrbek <kreyren@rixotstudio.cz>, 53301-done@debbugs.gnu.org
Cc: yasu@yasuaki.com
Subject: bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing
Date: Mon, 17 Jan 2022 18:35:56 +0100	[thread overview]
Message-ID: <87v8yi6z9f.fsf@gnu.org> (raw)
In-Reply-To: <57e235e0-7709-6093-2224-758179451c63@rixotstudio.cz>

[-- Attachment #1: Type: text/plain, Size: 496 bytes --]

Jacob Hrbek <kreyren@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!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2022-01-17 17:37 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   ` bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing Jacob Hrbek
2022-01-16 10:30     ` Jacob Hrbek
2022-01-17 17:35     ` Marius Bakke [this message]
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=87v8yi6z9f.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=53301-done@debbugs.gnu.org \
    --cc=kreyren@rixotstudio.cz \
    --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.