Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #195577 > unrolled thread

Problem with Firefox Quantum v-650.0

Started by"Stephen P. Molnar" <s.molnar@sbcglobal.net>
First post2018-05-10 17:10 +0200
Last post2018-05-10 21:40 +0200
Articles 7 — 5 participants

Back to article view | Back to linux.debian.user


Contents

  Problem with Firefox Quantum v-650.0 "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-05-10 17:10 +0200
    Re: Problem with Firefox Quantum v-650.0 Greg Wooledge <wooledg@eeg.ccf.org> - 2018-05-10 17:20 +0200
      Re: Problem with Firefox Quantum v-650.0 "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-05-10 19:10 +0200
        Re: Problem with Firefox Quantum v-650.0 Patrick Bartek <nemommxiv@gmail.com> - 2018-05-11 05:00 +0200
          Re: Problem with Firefox Quantum v-650.0 Dan Ritter <dsr@randomstring.org> - 2018-05-11 17:10 +0200
            Re: Problem with Firefox Quantum v-650.0 Patrick Bartek <nemommxiv@gmail.com> - 2018-05-11 17:40 +0200
    Re: Problem with Firefox Quantum v-650.0 Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-10 21:40 +0200

#195577 — Problem with Firefox Quantum v-650.0

From"Stephen P. Molnar" <s.molnar@sbcglobal.net>
Date2018-05-10 17:10 +0200
SubjectProblem with Firefox Quantum v-650.0
Message-ID<vNVmG-1O3-15@gated-at.bofh.it>
I've encountered a strange problem with the latest release of Firefox 
Quantum v-60.0.

Up to this point the previous versions, the 59.x.x, series had been very 
happily residing in /opt/firefox.  I uncompressed the downlo9aded file 
as a user and thee copied the firefox directory tree as root

I did the upgrade exactly the same way, but now when I try opening 
firefox I get:

comp@AbNormal:/opt/firefox$ ./firefox
XPCOMGlueLoad error for file /opt/firefox/libnspr4.so:
/opt/firefox/libnspr4.so: cannot open shared object file: No such file 
or directory
Couldn't load XPCOM.

What I find really puzzling is that I can run the new version in my user 
directory tree without any problems.

What is going on here?

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [next] | [standalone]


#195581

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2018-05-10 17:20 +0200
Message-ID<vNVwm-1Rq-23@gated-at.bofh.it>
In reply to#195577
On Thu, May 10, 2018 at 11:07:43AM -0400, Stephen P. Molnar wrote:
> I've encountered a strange problem with the latest release of Firefox
> Quantum v-60.0.
> 
> Up to this point the previous versions, the 59.x.x, series had been very
> happily residing in /opt/firefox.  I uncompressed the downlo9aded file as a
> user and thee copied the firefox directory tree as root
> 
> I did the upgrade exactly the same way, but now when I try opening firefox I
> get:
> 
> comp@AbNormal:/opt/firefox$ ./firefox
> XPCOMGlueLoad error for file /opt/firefox/libnspr4.so:
> /opt/firefox/libnspr4.so: cannot open shared object file: No such file or
> directory
> Couldn't load XPCOM.
> 
> What I find really puzzling is that I can run the new version in my user
> directory tree without any problems.
> 
> What is going on here?

My first guess: you forgot to wipe out the old version before you unpacked
the new version into the same target directory.  So now you've got a mix
of files from two different versions, and something gets confused.

[toc] | [prev] | [next] | [standalone]


#195586

From"Stephen P. Molnar" <s.molnar@sbcglobal.net>
Date2018-05-10 19:10 +0200
Message-ID<vNXeO-2W6-5@gated-at.bofh.it>
In reply to#195581
On 05/10/2018 11:13 AM, Greg Wooledge wrote:
> On Thu, May 10, 2018 at 11:07:43AM -0400, Stephen P. Molnar wrote:
>> I've encountered a strange problem with the latest release of Firefox
>> Quantum v-60.0.
>>
>> Up to this point the previous versions, the 59.x.x, series had been very
>> happily residing in /opt/firefox.  I uncompressed the downlo9aded file as a
>> user and thee copied the firefox directory tree as root
>>
>> I did the upgrade exactly the same way, but now when I try opening firefox I
>> get:
>>
>> comp@AbNormal:/opt/firefox$ ./firefox
>> XPCOMGlueLoad error for file /opt/firefox/libnspr4.so:
>> /opt/firefox/libnspr4.so: cannot open shared object file: No such file or
>> directory
>> Couldn't load XPCOM.
>>
>> What I find really puzzling is that I can run the new version in my user
>> directory tree without any problems.
>>
>> What is going on here?
> My first guess: you forgot to wipe out the old version before you unpacked
> the new version into the same target directory.  So now you've got a mix
> of files from two different versions, and something gets confused.
>
>
Actually not.  I renamed the v-59.x.x in /opt and copied the version 
directly from the user subdirectory in wi=hich I unzipped the download.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]


#195591

FromPatrick Bartek <nemommxiv@gmail.com>
Date2018-05-11 05:00 +0200
Message-ID<vO6rL-Uf-3@gated-at.bofh.it>
In reply to#195586
On Thu, 10 May 2018 13:00:27 -0400 "Stephen P. Molnar"
<s.molnar@sbcglobal.net> wrote:

> 
> On 05/10/2018 11:13 AM, Greg Wooledge wrote:
> > On Thu, May 10, 2018 at 11:07:43AM -0400, Stephen P. Molnar wrote:
> >> I've encountered a strange problem with the latest release of
> >> Firefox Quantum v-60.0.
> >>
> >> Up to this point the previous versions, the 59.x.x, series had
> >> been very happily residing in /opt/firefox.  I uncompressed the
> >> downlo9aded file as a user and thee copied the firefox directory
> >> tree as root
> >>
> >> I did the upgrade exactly the same way, but now when I try opening
> >> firefox I get:
> >>
> >> comp@AbNormal:/opt/firefox$ ./firefox

That should be firefox not /firefox.

> >> XPCOMGlueLoad error for file /opt/firefox/libnspr4.so:
> >> /opt/firefox/libnspr4.so: cannot open shared object file: No such
> >> file or directory
> >> Couldn't load XPCOM.
> >>
> >> What I find really puzzling is that I can run the new version in
> >> my user directory tree without any problems.
> >>
> >> What is going on here?
> > My first guess: you forgot to wipe out the old version before you
> > unpacked the new version into the same target directory.  So now
> > you've got a mix of files from two different versions, and
> > something gets confused.
> >
> >
> Actually not.  I renamed the v-59.x.x in /opt and copied the version 
> directly from the user subdirectory in wi=hich I unzipped the
> download.

FWIW, why don't you create a .desktop file -- firefox.desktop -- then
you don't have to start firefox from the command line.  Here's mine:

[Desktop Entry]
Name=firefox
Comment= Internet Browser
Exec=/opt/firefox/firefox
Icon=/opt/firefox/browser/icons/mozicon128.png
Type=Application
Terminal=false
StartupNotify=false
Categories=Application;Internet;

Put it in /usr/share/applications/  and restart your desktop.  The
system should create a menu item and icon.

B

[toc] | [prev] | [next] | [standalone]


#195610

FromDan Ritter <dsr@randomstring.org>
Date2018-05-11 17:10 +0200
Message-ID<vOhQd-KM-1@gated-at.bofh.it>
In reply to#195591
On Thu, May 10, 2018 at 07:55:24PM -0700, Patrick Bartek wrote:
> On Thu, 10 May 2018 13:00:27 -0400 "Stephen P. Molnar"
> <s.molnar@sbcglobal.net> wrote:
> 
> > 
> > On 05/10/2018 11:13 AM, Greg Wooledge wrote:
> > > On Thu, May 10, 2018 at 11:07:43AM -0400, Stephen P. Molnar wrote:
> > >> I've encountered a strange problem with the latest release of
> > >> Firefox Quantum v-60.0.
> > >>
> > >> Up to this point the previous versions, the 59.x.x, series had
> > >> been very happily residing in /opt/firefox.  I uncompressed the
> > >> downlo9aded file as a user and thee copied the firefox directory
> > >> tree as root
> > >>
> > >> I did the upgrade exactly the same way, but now when I try opening
> > >> firefox I get:
> > >>
> > >> comp@AbNormal:/opt/firefox$ ./firefox
> 
> That should be firefox not /firefox.

No, Stephen changed to a particular directory and wants to make
sure that the firefox executable in this directory is run.

./firefox is correct.

firefox by itself would search the PATH, and no proper PATH
includes ".", although his might include "/opt/firefox".

-dsr-

[toc] | [prev] | [next] | [standalone]


#195617

FromPatrick Bartek <nemommxiv@gmail.com>
Date2018-05-11 17:40 +0200
Message-ID<vOijf-U9-9@gated-at.bofh.it>
In reply to#195610
On Fri, 11 May 2018 11:06:54 -0400 Dan Ritter <dsr@randomstring.org>
wrote:

> On Thu, May 10, 2018 at 07:55:24PM -0700, Patrick Bartek wrote:
> > On Thu, 10 May 2018 13:00:27 -0400 "Stephen P. Molnar"
> > <s.molnar@sbcglobal.net> wrote:
> > 
> > > 
> > > On 05/10/2018 11:13 AM, Greg Wooledge wrote:
> > > > On Thu, May 10, 2018 at 11:07:43AM -0400, Stephen P. Molnar
> > > > wrote:
> > > >> I've encountered a strange problem with the latest release of
> > > >> Firefox Quantum v-60.0.
> > > >>
> > > >> Up to this point the previous versions, the 59.x.x, series had
> > > >> been very happily residing in /opt/firefox.  I uncompressed the
> > > >> downlo9aded file as a user and thee copied the firefox
> > > >> directory tree as root
> > > >>
> > > >> I did the upgrade exactly the same way, but now when I try
> > > >> opening firefox I get:
> > > >>
> > > >> comp@AbNormal:/opt/firefox$ ./firefox
> > 
> > That should be firefox not /firefox.
> 
> No, Stephen changed to a particular directory and wants to make
> sure that the firefox executable in this directory is run.
> 
> ./firefox is correct.
> 
> firefox by itself would search the PATH, and no proper PATH
> includes ".", although his might include "/opt/firefox".

Sorry. I didn't see the "dot" before the slash.  I use a texted based
email client, and the "dot" is very small, only one pixel.   Just
missed it.  With the "dot," of course, the line is correct.

B

[toc] | [prev] | [next] | [standalone]


#195588

FromAbdullah Ramazanoğlu <ar018@yahoo.com>
Date2018-05-10 21:40 +0200
Message-ID<vNZzX-4lS-7@gated-at.bofh.it>
In reply to#195577
On Thu, 10 May 2018 11:07:43 -0400 Stephen P. Molnar said:

[--8<--]

> comp@AbNormal:/opt/firefox$ ./firefox
> XPCOMGlueLoad error for file /opt/firefox/libnspr4.so:
> /opt/firefox/libnspr4.so: cannot open shared object file: No such file 
> or directory
> Couldn't load XPCOM.
> 
> What I find really puzzling is that I can run the new version in my user 
> directory tree without any problems.

Just a raw guess. NSPR address might be be taken from somewhere in current
directory, failing that from a config setting in your home directory. In /opt
directory there may be a pointer (conf file, symlink, etc.) to
"/opt/firefox/libnspr4.so" as NSPR address.

When you run firefox from within /opt, then this address is found in the
current directory, which fails. When you run firefox from anywhere else (not
just your home dir) then no pointer is found in the current directory, so your
default config setting for NSPR in your home takes precedence, which succeeds.

I would have tested this by running firefox from a completely different
(not /opt, not /home/user) directory. If it runs, then maybe this hypothesis
has a chance.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web