Ask Your Question

I get an error in runtime_manager.launch

asked 2020-04-11 02:01:13 -0600

dandelion1124 gravatar image

updated 2020-04-11 23:43:34 -0600

Required information:

  • Operating system and version:
    • Ubuntu 18.04
  • Autoware installation type:
    • From source
  • Autoware version or commit hash
  • ROS distribution and version:
    • ROS Melodic
  • ROS installation type:
    • From binaries

Description of the bug

$ roslaunch runtime_manager runtime_manager.launch

In this time, the following error message was displayed in Terminal.
Is this a bug?

bash: ./../../../setup.bash: No such file or directory

There is this operation in runtime_manager/scripts/run.

edit retag flag offensive close merge delete


@dandelion1124 Please provide some screenshots.

omkard gravatar image omkard  ( 2020-04-11 14:29:41 -0600 )edit

@omkard Thank you for your reply. I shared screenshot.

dandelion1124 gravatar image dandelion1124  ( 2020-04-11 23:56:30 -0600 )edit

I will see if I have same the issue @dandelion1124 and let you know.

omkard gravatar image omkard  ( 2020-04-12 16:33:20 -0600 )edit

Hi @dandelion1124 ,

I am getting the same error too. But, I don't have trouble due to that.

image description

omkard gravatar image omkard  ( 2020-04-13 09:31:11 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2020-04-15 23:12:18 -0600

Josh Whitley gravatar image

It is a bug (because the file is not in the correct location) but, fortunately, one that does not affect operation of the Autoware Runtime Manager. That line in the script is meant to source your workspace but, depending upon how you built your workspace, the location of the setup.bash file will be different. However, it isn't really needed so it failing has no negative consequences.

edit flag offensive delete link more


However, it isn't really needed so it failing has no negative consequences.

Thank you for your reply. Should I remove source ./../../../setup.bash from runtime_manager/scripts/run?

dandelion1124 gravatar image dandelion1124  ( 2020-04-18 09:04:47 -0600 )edit

The problem with using this method to try to source the workspace is that it is relying on the location of the installed runtime manager folder to be static. However, depending on how you build or configure your workspace, this may not be true. That being said, the majority of users will either:

  1. Source their workspace as part of their ~/.bashrc file; or
  2. Source their workspace before running runtime_manager.

So, there are two "fixes" for this:

  1. Remove it.
  2. Assume that most people built their workspace using the from-source instructions and replace it with source ./../../../../setup.bash (one more level than the current one).

I'm fine with either but please make a pull request to change this in the official repository.

Josh Whitley gravatar image Josh Whitley  ( 2020-04-20 15:52:26 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2020-04-10 23:20:29 -0600

Seen: 280 times

Last updated: Apr 15 '20