Re: Re: Re: git: 5ee4d6fde813 - main - www/firefox: update to 123.0 (rc3)

On Thu, Feb 29, 2024 at 09:16:19AM +0100, Baptiste Daroussin wrote:
> On Thu, Feb 29, 2024 at 08:11:13AM +0100, Emmanuel Vadot wrote:
> > On Thu, 29 Feb 2024 00:01:07 +0100
> > Christoph Moench-Tegeder <cmt@burggraben.net> wrote:
> > 
> > > ## Emmanuel Vadot (manu@bidouilliste.com):
> > > 
> > > > > >  This update is broken on wayland.
> > > > > Congratulations to our first wayland user?
> > > >  Clearly not.
> > > 
> > > It has been weeks since 123 landed, and this could be the first
> > > report of brokeness. So statistically it's likely we don't have that
> > > many wayland users or we don't have general breakage. 
> > 
> >  It's been 17 days and the packages for latest have been rebuilt on the
> > 24th, people don't upgrade every week on current. Also since it's
> > broken on quarterly all users of releng branch using it won't see this
> > problem.
> > 
> > > On the other hand, there has been rather large upheaval during the
> > > man transition; and what base system, clang and rust are
> > > we talking about here? (I have no clue, there's just quite
> > > a bunch of variables here).
> > 
> >  A rollback to 122 "fixes" the issue so it's unlikekly that it's
> > another factor.
> > 
> > > >  Are you saying that you don't care that it's broken for all our
> > > > wayland users and that you will not do a thing about this ?
> > > 
> > > This is not a matter of "care". I don't have a wayland environment
> > > (never had); all I have is some hardware in urgent need of
> > > replacement (it's crapping out under me) with a slightly stale
> > > base system because I've hadn't no time to anything on both
> > > fronts. Remember, this is just a hobby operation over here.
> > 
> >  I think that it would be good that you setup a quick wayland env, the
> > handbook is pretty good on how to do this and we want wayland to be a
> > first class citizen on FreeBSD (it's already is tbh, most drmc
> > developers on FreeBSD use wayland only already).
> > 
> > > So now what. Is this broken on your system only or in the general
> > > case on released FreeBSD versions (which ones?). 
> > 
> >  It's broken on all my desktop running main-3733d82c4deb, it's also
> > broken for bapt@ who is the one made me aware of this issue in the
> > first place.
> > 
> > > Any idea what the fds are connected to (a basic firefox has ~150 fd when it's
> > > up and running).
> > 
> >  No idea no, if you have any tips to debug such large program I'm happy
> > to dig more.
> > 
> > > Regards,
> > > Christoph
> > > 
> > > -- 
> > > Spare Space
> > 
> 
> For the record the issue is the new wayland-proxy code, it works fine when
> disabled via  MOZ_DISABLE_WAYLAND_PROXY=1
> 
> I am digging why it is not working

wayland-proxy code is buggy, I am discussing with upstream.
> 

Another regression in firefox 123: disabiling media.ffvpx.enabled does not work
anymore, if disabled, then it cannot read music anymore form multimedia/lms or
other music streamer.

Bapt