Revision history [back]

Stack trace is not useful but i have no idea how i could have more details at one line it is actually crashing inside libroscpp

#0  0x00007ffff7f0a36e in ros::NodeHandle::createTimer(ros::Duration, boost::function<void (ros::TimerEvent const&)> const&, bool, bool) const () from /lib/x86_64-linux-gnu/libroscpp.so.2d
#1  0x0000555555558b97 in main (argc=1, argv=0x7fffffffe1e8) at /home/worker/main.cpp:11

actually, it's very useful, and this most likely already shows the cause: /lib/x86_64-linux-gnu/libroscpp.so.2d.

There are no artefacts from ROS Noetic proper which install into anything else but /opt/ros/noetic.

In other words: the library /lib/x86_64-linux-gnu/libroscpp.so.2d is not part of ROS Noetic.

To install i do

sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'
curl -s https://raw.githubusercontent.com/ros/rosdistro/master/ros.asc | sudo apt-key add -
sudo apt install ros-noetic-ros-base libroscpp-dev

Similar to the above: libroscpp-dev is not part of ROS Noetic (in fact, libroscpp-dev is not really part of any ROS version).

All packages part of ROS Noetic will have the ros-noetic- prefix (like ros-noetic-ros-base).

What's most likely happening is you're mixing ROS Noetic proper with the UpstreamPackages. That won't work reliably, as you've already found out. See also “upstream packages” increasingly becoming a problem on ROS Discourse.

I'd recommend to purge all upstream variants of ROS packages and make sure you have a sane ROS Noetic install.