unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: phodina via <help-guix@gnu.org>
Subject: Re: Screen sharing ungoogled-chromium
Date: Mon, 2 May 2022 09:06:50 +0900	[thread overview]
Message-ID: <914C4745-BB60-4E2A-BB05-C53175606BD9@yasuaki.com> (raw)
In-Reply-To: <87sfpsrf86.fsf@gmail.com>

I do use Guix (with questionable modules added) as my primary computer at home and I tell you only half of the applications are sharable including chromium and emacs.   Many other applications are not.  But then again I use wayland so I can't tell easily which is causing what problems...   -Yasu

> On May 2, 2022, at 08:43, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> 
> Hello,
> 
> 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.
> 
> If it's anything like the Google Meet proprietary SaaS, it may requires
> Google-specific WebRTC extensions not yet part of the standard (dubbed
> "Hangout Services Extension" and disabled in ungoogled-chromium).  I
> remember reading this interesting related discussion about the "Hangout
> Services Extension" [0].  I'm not sure it's related, but who knows!
> 
> [0]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886358
> 
> HTH,
> 
> Maxim
> 


  reply	other threads:[~2022-05-02  0:07 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 [this message]
2022-05-02  8:45     ` Reza Housseini
2022-05-02 19:05     ` Alexey Abramov
2022-05-04 13:53     ` Gary Johnson

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=914C4745-BB60-4E2A-BB05-C53175606BD9@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=help-guix@gnu.org \
    --cc=maxim.cournoyer@gmail.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).