Re: `ls` shows file, `bash` says "No such file" ???

On Sat, May 3, 2014 at 1:25 PM, Tom Roche <Tom_Roche@pobox.com> wrote:

Tom Roche Fri, 02 May 2014 22:25:34 -0400

>> For background on my problem (and why I very much need to solve it), see
>> http://forums.linuxmint.com/viewtopic.php?f=190&t=166506&p=855700#p855700

I guess I should have read that first.

>> But the essence of the problem appears to be

>> me@it ~ $ /usr/local/share/firefox-3.6.28/firefox-bin
>> bash: /usr/local/share/firefox-3.6.28/firefox-bin: No such file or directory
>> [127]me@it ~ $ lsalh /usr/local/share/firefox-3.6.28/firefox-bin
>> -rwxr-xr-x 1 root staff 44K Mar 6 2012 /usr/local/share/firefox-3.6.28/firefox-bin

Mike Kupfer Fri, 02 May 2014 21:02:48 -0700

> I ran into this issue (with a different binary, on Ubuntu 12.04) a week
> or two ago, and it was in fact the mismatch between 32-bit and 64-bit.
> So try installing the 64-bit FF

Alas, as detailed @ link above, I cannot: I must run a VPN which

- the developer (F5) only supports for linux clients as browser plugins (?!?) for firefox-3.x and firefox-8.x

- my workplace's servers' version of the F5 backend only supports the frontend version that runs on firefox-3.x

and there are no 64-bit builds of firefox-3.x. But it gets worse :-(

Can't get much worse. You're trying to solve security problems by running browser-dependent VPN stuff in seriously out-of-date browsers. (With known vulnerabilities and no support since how long ago?)

Tell your boss to tell the BOsFH at work to straighten up and fix their problems or pay you double OT to fix their problems for them. You've provided enough service OT already.

As detailed @ link above, I have formerly made firefox-3.6.28+F5NAP work on two different debian boxes! Including one virtually identical to the box in question! So this is a *solved* problem ... I just don't know the solution :-(

If you don't know what you did before, it is by definition not a solved problem. Maybe a problem you were once successful in postponing, but not a solved problem. You think there is a solution out there somewhere, but finding it again will be yet another exercise in blind enumeration techniques -- with no guarantee that the universe of currently available libraries and binaries contains a successful path to the solution anymore.

Brute-force solutions are not cheap.

> The error message from bash is... unfortunate, to say the least.

Can we be sure?

Indeed. Where to report this bug?

I'm not convinced it's a bug in debian. We would like things from versions that far apart to be able to pass the name of the library object not found by the linking loader back to the shell, but ....

I guess the first thing I'd suggest is not to use sid, anyway. Tom H mentions something you need to check out about jessie. If you insist on doing the service OT, how about backing up to stable?

--
Joel Rees

Be careful where you see conspiracy.
Look first in your own heart.