all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Remco <me@rwv.io>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: help-guix@gnu.org
Subject: Re: Jitsi Meet Screen Sharing with Ungoogled-Chromium
Date: Sun, 16 Jan 2022 11:34:40 +0100	[thread overview]
Message-ID: <87sfto3r5r.fsf@rwv.io> (raw)
In-Reply-To: <7C9AC542-80D1-483C-9699-953FAB496F78@yasuaki.com>

2022/01/16 18:46, Yasuaki Kudo:

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

It (starting/joining a jitsi meeting and sharing a screen/window/tab)
works for me with ungooogled-chromium version 92 from guix.  Newer
versions unfortunately don't which is probably related to this issue:

  https://issues.guix.gnu.org/50773

The last guix commit I've found with a working ungooogled-chromium is:

  08660f7c8880e30aecc05cd6302d2ccd715913e9

You can use guix timemachine to run it (see issue for an example).

R.



  parent reply	other threads:[~2022-01-16 10:35 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
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 [this message]
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=87sfto3r5r.fsf@rwv.io \
    --to=me@rwv.io \
    --cc=help-guix@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.