start roscore fails - " cannot launch node of type [rosout/rosout]: can't locate node [rosout] in package [rosout]"

asked 2018-11-02 12:19:08 -0600

omer gravatar image

updated 2018-11-03 09:19:38 -0600

gvdhoorn gravatar image

hi,

Following https://answers.ros.org/question/3073...

We Tried coping the /opt/ros/kinetic v 1.12.13 from 1 pc (where our application works) directly to another. this worked for one computer, but not for another one. all are runing ubuntu 16.04 , same architecture ( x 64) but not exactly the same computer.

so now, on one computer roscore fails to start with the "cannot launch node of type [rosout/rosout]: can't locate node [rosout] in package [rosout]" error. before we switched the /opt/ros/kinetic to the 1.12.13 version, this computer was runinng version 1.12.14 ( ros core 1.12.14 managed to start).

another problem with the computer now is that "/opt/ros/kinetic/setup.bash" does not set all ros env variables. ( at first when running roscore with the copied /opt/ros/kinetic 1.12.13 i got various missing environment variables errors like rosditro=<unknown> , so i manually set their values not using the kinetic/setup.bash, but i do get the "cannot launch node of type [rosout/rosout]: can't locate node [rosout] in package [rosout]".

i tried running my own version of /opt/ros/kinetic/setup.bash , where output is not sent to /dev/null, but this generated an empty file, no additional error information.

please help, Omer.


Edit: Hello,

[please take into account that i'm a newbe to ros]

building from sounds possible, but : 1. i've read the installation from source instructions it seems to me that following them will install the latest version of kinetic ( which is not what i need).

  1. i've also read rosinstall_generator's documentation , i didn't find a means/parameter to point it to a specific version.

  2. i've found a list of published/available ros source versions on github the version I need (1.12.13) is not listed there ( only goes up to 1.12.8) . ( using one of the available version's may work , but it also may introduce other errorrs, and at the very least will require significant retesting of our application)

thanks, Omer.

edit retag flag offensive close merge delete

Comments

I really would not recommend copying the kinetic install between computers like this! You'll probably cause chaos with missing dependencies and incorrect versions of packages. There's a very good reason to use apt-get.

PeteBlackerThe3rd gravatar image PeteBlackerThe3rd  ( 2018-11-02 12:45:31 -0600 )edit

It may not be your preferred solution, but can you clarify why building things from sources is not an option?

Building a base set of ROS pkgs is not really that big of a deal and on a recent machine should take no more than 30 minutes.

gvdhoorn gravatar image gvdhoorn  ( 2018-11-02 13:26:49 -0600 )edit

Hello,

[please take into account that i'm a newbe to ros]

building from sounds possible, but : 1. i've read the installation from source instructions it seems to me that following them will install the latest version of kinetic ( which is not what i need)

omer gravatar image omer  ( 2018-11-03 03:16:19 -0600 )edit
1

To avoid the risk of an X Y problem, could you tell us exactly what you're problem is and why you need this specific version of ROS? Building you system to work with the standard ROS API and latest version is recommend if it's possible.

PeteBlackerThe3rd gravatar image PeteBlackerThe3rd  ( 2018-11-03 06:04:13 -0600 )edit

sure, here's a link to a post on the original problem.

omer gravatar image omer  ( 2018-11-03 06:20:51 -0600 )edit

+1 @PeteBlackerThe3rd: I should have already asked what the rationale for wanting to do this was in #q307384.

This is a massive xy-problem.

@omer: you should have posted the link to that librealsense issue as part of #q307384.

gvdhoorn gravatar image gvdhoorn  ( 2018-11-03 09:22:24 -0600 )edit

@omer: forget I suggested building an older version of ROS. You'll want to fix your librealsense issue, not revert to older versions of ROS.

gvdhoorn gravatar image gvdhoorn  ( 2018-11-03 09:26:31 -0600 )edit

Agreed, this is a bug in librealsense. Trying to find a working version of this or fixing this bug is the way forward. Personally we've had a lot of trouble with the Intel drivers, having to try several versions of them before getting one that works.

PeteBlackerThe3rd gravatar image PeteBlackerThe3rd  ( 2018-11-03 15:57:01 -0600 )edit