On 04/02/2015 at 01:29 PM, Gene Heskett wrote: > On Thursday 02 April 2015 09:34:36 Petter Adsen wrote: > >> On Thu, 2 Apr 2015 09:24:19 -0400 >> petter@monster:~/Downloads/firefox$ ls -l firefox >> -rwxr-xr-x 1 petter petter 147776 mars 27 04:51 firefox > -rwxr-xr-x 1 gene gene 147776 Mar 26 23: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) > > whereas here: > gene@coyote:~/bin/firefox-37/firefox$ ldd firefox > not a dynamic executable > I also tried a sudo ldd firefox and got exactly the same response. > > Now, is not ldd itself an executable? > gene@coyote:~/bin/firefox-37/firefox$ ldd /usr/bin/ldd > not a dynamic executable > WTH???? $ file /usr/bin/ldd /usr/bin/ldd: Bourne-Again shell script, ASCII text executable If you want to test ldd, try it on /bin/true or suchlike - or at least check with file first, to make sure that what you're testing it on is actually a binary file. >> 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? >> :) > > Yes, but all it had been able to do after the re-install was start 2 > copies, spinning its wheels with 1 of my phenoms cores pegged out > and north of 150C for temps. And it was just cleaned & regreased > with Artic Silver in Oct 2014. One of my annual rites. My guess is that it was parsing (and partly choking on) some part of your user profile, and that the reason it "came back" is that it managed to finish that process. Normally that shouldn't require nearly that long or nearly that much system load, but in some cases it may be possible. If you want to guarantee avoiding that entirely, the only way to do it that I know of is to remove the entire Firefox profile (~/.mozilla/firefox/profiledirname) and start from scratch. That would remove all of your preferences and extensions (as well as your history, et cetera), however, so it's a considerably more drastic move - and not one I'd consider for myself, without _extensive_ research into possible alternatives. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature