From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: help-guix@gnu.org
Subject: Re: Jitsi Meet Screen Sharing with Ungoogled-Chromium
Date: Sun, 16 Jan 2022 12:26:49 +0000 [thread overview]
Message-ID: <06637848-9847-f31e-aa14-02064170dc79@rixotstudio.cz> (raw)
In-Reply-To: <874k63c42l.fsf@colimite.fr>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
> A friend of mine runs a Jitsi instance on a private server, and we
sometimes have this issue because the Jitsi instance breaks for some
weird reason, and not because of the browser. -- Sergiu
From my experience and assisting maintenance of jitsi it's very stable
in terms of production runtime so i would say that your friend
misconfigured the deployment.
Also i think that it's very clear that the screen share fails due to the
lack of VP8 codec support based on provided terminal output.
On 1/16/22 12:25, Sergiu Ivanov wrote:
> A friend of mine runs a Jitsi instance on a private server, and we
> sometimes have this issue because the Jitsi instance breaks for some
> weird reason, and not because of the browser.
--
Jacob Hrbek
[-- Attachment #1.2: 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 13:01 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
2022-01-16 11:25 ` Sergiu Ivanov
2022-01-16 12:26 ` Jacob Hrbek [this message]
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=06637848-9847-f31e-aa14-02064170dc79@rixotstudio.cz \
--to=kreyren@rixotstudio.cz \
--cc=help-guix@gnu.org \
/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.