[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: firefox-37, where to put



On Thu, 2 Apr 2015 09:24:19 -0400
Gene Heskett <gheskett@wdtv.com> wrote:

> 
> 
> On Thursday 02 April 2015 08:23:32 Petter Adsen wrote:
> > On Thu, 2 Apr 2015 08:08:49 -0400
> >
> > Gene Heskett <gheskett@wdtv.com> wrote:
> > > On Thursday 02 April 2015 05:33:40 Darac Marjal wrote:
> > > > On Thu, Apr 02, 2015 at 05:16:37AM -0400, Gene Heskett wrote:
> > > > > wordwrap off so as not to rip up long lines.
> > > > >
> > > > >
> > > > > Fun & games but not S&G. Network-Manager had the last word
> > > > > when I excised that piece of insanity, the SOB zeroed out the
> > > > > eth0 settings in /etc/network/interfaces.  Bad dog, no
> > > > > biscuit from me.
> > > > >
> > > > > All discovered and I think fixed as I appear to have restored
> > > > > networking now.
> > > > >
> > > > > All triggered by discovering that the reason I was into swap
> > > > > all the time was that for the last 12 days I had been running
> > > > > a 32 bit rtai kernel which is NOT PAE, seems I need to edit
> > > > > the default number in /boot/grub/grub.cnf, it is not pointing
> > > > > at a 64 bit 3.2.0-4amd64 vmlinuz.  That discovery in turn
> > > > > triggered by firefox spitting out a tummy ache on start
> > > > > attempts.
> > > > >
> > > > > I renamed the firefox script in /usr/bin/ which was actually
> > > > > running iceweasel to /usr/bin/firefux, then made a symlink
> > > > > from
> > > > >
> > > > > /home/gene/bin/firefox-37/firefox/firefox
> > > > > from /usr/bin/firefox.
> > > > >
> > > > > So, rebooted to a true 64 bit kernel, but 64 bit firefox
> > > > > refuses to run: gene@coyote:~$ ls -l /usr/bin/firefox
> > > > > lrwxrwxrwx 1 root root 41 Apr  2 04:03 /usr/bin/firefox ->
> > > > > /home/gene/bin/firefox-37/firefox/firefox Which is correct.
> > > > > But First try it like the renamed script does it:
> > > > > gene@coyote:~$ firefox "$@"
> > > > > bash: /usr/bin/firefox: No such file or directory
> > > > > Then try w/o the argument.
> > > > > gene@coyote:~$ firefox
> > > > > bash: /usr/bin/firefox: No such file or directory
> > > > >
> > > > > Its 5am, and I don't seem to have even one eye open
> > > > > simultaineously...
> > > > >
> > > > > The firefox binary itself
> > > > > gene@coyote:~$ ls -l bin/firefox-37/firefox/firefox
> > > > > -rwxr-xr-x 1 gene gene 147776 Mar 26 23:51
> > > > > bin/firefox-37/firefox/firefox
> > > >
> > > > Often, in this situation, it's not the file you're thinking of
> > > > which doesn't exist. When executing a binary file, the kernel
> > > > will return the same error (ENOENT) for all files necessary to
> > > > start the binary. In other words, you can't immediately tell if
> > > > it's the binary which doesn't exist, or the libraries it's
> > > > linked to.
> > > >
> > > > So, as you know the binary exists, run "ldd /usr/bin/firefox" to
> > > > see which libraries it's linked against and see if they all
> > > > exist.
> > >
> > > gene@coyote:~/bin/firefox-37/firefox$ sudo ldd /usr/bin/firefox
> > > [sudo] password for gene:
> > > 	not a dynamic executable
> >
> > Run it on the binary itself, not the symlink.
> >
> > Petter
> 
> And it still claims "not an executable".
> 
> Does using squeeze to unpack a tarball screw things up this bad

No idea, never used it.

Try these:

petter@monster:~/Downloads$ md5sum firefox-37.0.tar.bz2 
765710c0930898ab09084b4f96186bb0  firefox-37.0.tar.bz2

petter@monster:~/Downloads$ tar xfj firefox-37.0.tar.bz2 && cd firefox
petter@monster:~/Downloads/firefox$ file firefox
firefox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.18,
BuildID[sha1]=072ec5d969782a2391d9e60bbb126a541d606836, stripped

petter@monster:~/Downloads/firefox$ md5sum firefox
b94cb23b2c05f08bca64cde6696001c9  firefox

petter@monster:~/Downloads/firefox$ ls -l firefox
-rwxr-xr-x 1 petter petter 147776 mars  27 04:51 firefox

petter@monster:~/Downloads/firefox$ ldd firefox
linux-vdso.so.1 => (0x00007ffcfabd4000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
 (0x00007f281ae50000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
 (0x00007f281ac4c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
 (0x00007f281aa43000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 (0x00007f281a734000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
 (0x00007f281a42c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
 (0x00007f281a215000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
 (0x00007f2819e4b000)
/lib64/ld-linux-x86-64.so.2 (0x00007f281b091000)

And see what you get. Note that this isn't a Debian machine, so you
won't get the same library versions, but they should be similar. If
you have the same version of FF that I dl'ed, then the md5sums should
be identical. Otherwise, something is corrupted.

> And iceweasel has recovered.  No history but prefs are intact ????

Didn't you start this thread by saying you deleted your history? :)

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."

Attachment: pgpAk7lkhhDzf.pgp
Description: OpenPGP digital signature


Reply to: