Revision history [back]

The error you're seeing here is "no such file or directory", and it's reasonably clear that the immediate file in question exists.

If these programs also fail to run when you execute them directly ( cd to bin, ./drrobot_player ), then there are a number of other things that could be causing this:

Your node is a python or shell script with a bad #! line at the beginning, or no #! line at all.
Your node is a broken symlink - it exists, but the thing it's supposed to point to doesn't.
Your node is compiled for a different architecture - perhaps it's a 32-bit binary on a 64-bit machine, and you don't have the 32-bit compatibility libraries installed.
Your node is actually a launch file

The error you're seeing here is "no such file or directory", and it's reasonably clear that the immediate file in question exists.

If these programs also fail to run when you execute them directly ( cd to bin, ./drrobot_player ), then there are a number of other things that could be causing this:

Your node is a python or shell script with a bad #! line at the beginning, or no #! line at all.
Your node is a broken symlink - it exists, but the thing it's supposed to point to doesn't.
Your node is compiled for a different architecture - perhaps it's a 32-bit binary on a 64-bit machine, and you don't have the 32-bit compatibility libraries installed.
Your node is actually a launch file

I took a deeper look into this. It turns out that the drrobot package maintainers were foolish enough to check 32-bit binaries into their repository: https://github.com/gitdrrobot/drrobot_jaguar4x4_player/tree/master/bin . You can probably convince them to run if you install the ia32-libs package.