[gentoo-user] Re: Zoom calls make firefox/librewolf crash
On 23/04/10 02:38AM, Efe İzbudak wrote: > Hi everyone, > > So since this weekend whenever I try to join a zoom call, my firefox > crashes and so does my librewolf. I've tried using both > firefox-bin-102.9.0 and firefox-bin-111.0.1 and also > librewolf-bin-110.0_p2. > > This doesn't happen when I disable webgl. > > I'm using dwl-0.4 and I'm on stable. > > Does anyone have any ideas on how to solve this? > For the sake of completeness, if anyone has this issue, downgrade wayland to 1.21-0-r1 to solve it. -- All the best, Efe The funny quote of this email is trivial and left as an exercise. signature.asc Description: PGP signature
Re: [gentoo-user] Re: zoom?
On 1/4/20 10:26 pm, (Nuno Silva) wrote:
On 2020-04-01, William Kenworthy wrote:
On 1/4/20 4:55 pm, Neil Bothwick wrote:
On Wed, 1 Apr 2020 09:12:46 +0800, William Kenworthy wrote:
[blocks B ] media-libs/mesa[-libglvnd(-)]
("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.1)
It looks like you need to emerge mesa with USE="libglvnd".
no, there is something else at play - I have tried adding it to
package.accept_keywords, package.provided etc. but they fail. If I use
--nodeps it wants to overwrite a number of mesa files so I am thinking
its not actually needed.
Any chance it is the libglvnd USE flag that is masked?
Looks like and ebuild/use flag problem (not a bug) in that Mesa is now
providing the dispatch services that libglvnd was providing - once the
Mesa version I have is installed, libglvng wont install as it wants to
overwrite some Mesa files. I am on a zoom conference at the moment :) -
so its working well except desktop share is only partially working so my
previous install method worked.
I'll raise a bug on it when I finish the zoom session.
BillK.
[gentoo-user] Re: zoom?
On 2020-04-01, William Kenworthy wrote:
> On 1/4/20 4:55 pm, Neil Bothwick wrote:
>> On Wed, 1 Apr 2020 09:12:46 +0800, William Kenworthy wrote:
>>
>>> [blocks B ] media-libs/mesa[-libglvnd(-)]
>>> ("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.1)
>> It looks like you need to emerge mesa with USE="libglvnd".
>
> no, there is something else at play - I have tried adding it to
> package.accept_keywords, package.provided etc. but they fail. If I use
> --nodeps it wants to overwrite a number of mesa files so I am thinking
> its not actually needed.
Any chance it is the libglvnd USE flag that is masked?
--
Nuno Silva
Re: [gentoo-user] Re: zoom?
On Fri, 27 Mar 2020 16:21:29 +, Michael wrote: > > Or just edit /etc/hosts ;-) > > > > Although Pihole is my currently preferred approach. > > Interesting ... you use this on your PC, or your edge router/DNS > resolver? On a Raspberry Pi, that way my DNS isn't dependent on other stuff, and comes up fast in the event of a reboot or power cycle. -- Neil Bothwick Why do kamikaze pilots wear helmets? pgpAlfgs_WUNS.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: zoom?
Neil Bothwick wrote: > On Fri, 27 Mar 2020 12:21:24 +0100, Holger Hoffstätte wrote: > >> Someone up for an automated hex editor script to remove this shit? >> Alternatively I guess the time has come to simply hard-block >> facebook.com in DNS. This is easy to do with dnsmasq or dnsdist as local >> proxy/cache/multiplexer. > Or just edit /etc/hosts ;-) > > Although Pihole is my currently preferred approach. > > I have several sites that I block using /etc/hosts. That way no matter what browser profile I'm using, that site is blocked on all of them, adblock, ublock etc or not. I might add, for some sites, they can't detect it is being blocked with those anti-adblock detectors. A few sites will not let you use them if adblock is running. If I disable adblock, the offending site is still blocked. The only downside, it blocks pretty much the entire site. It can block content you want. Adblock and such allows you to block ad directories and such where hosts file doesn't. Each has its own usage I guess. Dale :-) :-)
Re: [gentoo-user] Re: zoom?
On Friday, 27 March 2020 16:18:54 GMT Neil Bothwick wrote: > On Fri, 27 Mar 2020 12:21:24 +0100, Holger Hoffstätte wrote: > > Someone up for an automated hex editor script to remove this shit? > > Alternatively I guess the time has come to simply hard-block > > facebook.com in DNS. This is easy to do with dnsmasq or dnsdist as local > > proxy/cache/multiplexer. > > Or just edit /etc/hosts ;-) > > Although Pihole is my currently preferred approach. Interesting ... you use this on your PC, or your edge router/DNS resolver? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: zoom?
On Fri, 27 Mar 2020 12:21:24 +0100, Holger Hoffstätte wrote: > Someone up for an automated hex editor script to remove this shit? > Alternatively I guess the time has come to simply hard-block > facebook.com in DNS. This is easy to do with dnsmasq or dnsdist as local > proxy/cache/multiplexer. Or just edit /etc/hosts ;-) Although Pihole is my currently preferred approach. -- Neil Bothwick Three kinds of people: those who can count and those who can't. pgpZ03krm1Msm.pgp Description: OpenPGP digital signature
[gentoo-user] Re: zoom?
On 3/27/20 12:36 AM, Michael wrote: More info on the participation Zoom users /enjoy/, whether they like it and have agreed to it, or not: https://www.vice.com/en_us/article/k7e599/zoom-ios-app-sends-data-to-facebook-even-if-you-dont-have-a-facebook-account No need to rely on vague reports from third parties, just inspect the binary: holger>strings zoom | sort | uniq | grep facebook _uri=https://www.facebook.com/connect/login_success.html= @chat.facebook.com facebookLogin feature.login.disable.facebook http://graph.facebook.com/ http://www.facebook.com/xmpp/messages https://dev.zoom.us/facebook/oauth https://dev.zoom.us/facebook/oauth/client?mode=token https://devfacebook.zoom.us https://facebook.zoom.us https://www.facebook.com/ https://www.facebook.com/ZoomInc https://www.facebook.com/logout.php?access_token= https://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Fzoom.us https://www.facebook.com/v3.2/dialog/oauth https://zoom.us/facebook/oauth https://zoom.us/facebook/oauth/client?mode=token nofacebook slt_facebookUrlChanged user_facebook_login_token Someone up for an automated hex editor script to remove this shit? Alternatively I guess the time has come to simply hard-block facebook.com in DNS. This is easy to do with dnsmasq or dnsdist as local proxy/cache/multiplexer. -h
