From: Gary Johnson <lambdatronic@disroot.org>
To: phodina <phodina@protonmail.com>
Cc: g@xelera.eu, help-guix@gnu.org
Subject: Re: Screen sharing ungoogled-chromium
Date: Wed, 04 May 2022 09:53:11 -0400 [thread overview]
Message-ID: <877d71qu4f.fsf@disroot.org> (raw)
In-Reply-To: <rOh4DrA4KoG0BLFTXD1IeDi_eh4LBMOKee2OiDafIgEhSeQSDlHtWUhGAJcoOaAFRr7zXbPXbBLq_FD-Dr5Ts4W_4zYJcZX1gXDJFvfZLKo=@protonmail.com>
phodina via <help-guix@gnu.org> writes:
> Jitsi works in chromium and I'm able to share screen.
>
> But I'm trying to switch to Guix as my work laptop but in order to do that the Teams screen share would have to work.
>
> Anyway it's proprietary garbage so if there isn't anybody who got it working let's just close the discussion.
As just one more data point, I use Guix as my work laptop and connect to
my video conferencing meetings through ungoogled-chromium. In my
experience, I can share my screen successfully in Jitsi and Zoom
meetings only. I can attend Google Meet meetings and see other people's
screens but cannot share my own. Microsoft Teams just crashes and burns
when I try to connect.
Fortunately (?) my company mostly uses Zoom for scheduled meetings, and
I can use Jitsi for my personal meetings, so this works out fine for me
at this time.
Best of luck,
Gary
--
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Why is HTML email a security nightmare? See https://useplaintext.email/
Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
prev parent reply other threads:[~2022-05-04 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 5:52 Screen sharing ungoogled-chromium phodina via
2022-04-28 17:41 ` Giovanni Biscuolo
2022-05-01 4:24 ` phodina via
2022-05-01 23:43 ` Maxim Cournoyer
2022-05-02 0:06 ` Yasuaki Kudo
2022-05-02 8:45 ` Reza Housseini
2022-05-02 19:05 ` Alexey Abramov
2022-05-04 13:53 ` Gary Johnson [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d71qu4f.fsf@disroot.org \
--to=lambdatronic@disroot.org \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).