Re: a browser that runs?

[steve%prd.co.uk@localhost (Steve Blinkhorn)]

ld.so.conf doesn't help.

It's unlikely to be 1-bit coirruption since the same problem occurs on
three separate machines, all running stock X11 as supplied from the
distro.

Do I read the error message right in that it is libXext.so.7 that can't
find the _XGetRequest symbol, so only programs that call a routine in
libXext.so.7 will have a problem?

BTW, how does NetBSD identify the system browser, and how do I change
that?

--
Steve Blinkhorn <steve%prd.co.uk@localhost>

You wrote:
> 
> Martin Husemann <martin%duskware.de@localhost> writes:
> 
> > On Wed, Apr 10, 2019 at 12:18:38PM +0000, Steve Blinkhorn wrote:
> >> [...]
> >> /usr/X11R7/lib/libXext.so.7: Undefined PLT symbol "_XGetRequest" (symnum = 99)
> >> (this is from firefox60) or some such.   For LibreOffice I resorted to
> >> using the Linux version.
> >
> > How are you building them? That symbol is in /usr/X11R7/lib/libX11.so,
> > and it is hard to imagine you would be able to run any X app w/o that.
> 
> I've had weird situations like this before, where it turned out that the
> application and/or its dependencies managed to get hold of some, but not
> all, of the required shared libraries.  I seem to recall an intermediate
> library not having been linked with the right options...?  Throwing in
> the towel, and just configuring /etc/ld.so.conf, has helped me out of a
> few such situations.  (Hmm.  I'm actually pretty sure the last case I
> had of this was with Libreoffice, on NetBSD/aarch64-current, just a few
> weeks ago.  I couldn't bear the thought of experimenting with changes to
> its pgksrc setup, because of the long build time.)
> 
> So maybe try creating an /etc/ld.so.conf with the lines "/usr/pkg/lib"
> and "/usr/X11R7/lib" in them, and see if that helps.  If it does, that
> would be an interesting data point in itself.
> 
> ...and then there's the time my home workstation was exhibiting similar
> symptoms, and I was all "come on, already - that library is already
> loaded and in use, by lots of applications!", until I figured out that
> the loaded and running instance of the shared library had a 1-bit memory
> corruption (I was stupidly using non-ECC RAM at the time) in such a way
> that already running clients were fine, but new ones couldn't start.
> 
> -tih
> -- 
> Most people who graduate with CS degrees don't understand the significance
> of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay
>