Protocol Buffer error in Arch-Linux ROS Noetic

[kanishkanarch]

Dear Tim,
I encountered the following error while trying to install the repo in my Arch-Linux system having a working ROS Noetic install.

error.txt

I am unable to solve this error, kindly help.

[TimDupontPXL]

Hi @Kanishk598 ,

After inspecting your error.txt file, it looks like there might be multiple issues:

1. The first sign of a possible problem: it tries to find the apt-get command on line 60, but you're using an Arch system.

2. The error itself occurs in the Gazebo 11 header files, not in the "ardrone_gazebo" package.

From your error.txt, line 67:

/usr/include/gazebo-11/gazebo/msgs/poses_stamped.pb.h:17:2: error: #error This file was generated by an older version of protoc which is

The error seems to be due to the version of the "protoc" library. Apparently, your Arch system has a newer version. You could look into downgrading the library or fixing the Gazebo header file(s), ...
But, I'm afraid that might be a downward spiral towards a possible dependency hell.

We do provide a Docker container called ROSNoeticDocker, which includes the ardrone_gazebo package and all the correct libraries.

I hope the Docker container could be a solution for you!

[kanishkanarch]

Hi @TimDupontPXL,
Thank you for such a quick response.
The container got built successfully but the Gazebo client is not starting up when I'm trying to launch Turtlebot in an empty world:

And even more errors with ARDrone:

error.txt

Please help.

[TimDupontPXL]

Hello @kanishkanarch ,

Unfortunately, the command you executed isn't shown in the screenshot. Also, the
Aborted (core dumped) error worries me quite a bit.

Yesterday, I added an extra command: start_turtlebot3_gazebo_empty_world. That
should start a TurtleBot3 in an empty Gazebo world. It's a simple Bash script,
located in the ~/bin directory of the container. This directory is included
in the $PATH environment variable. Therefore, you can execute the
start_turtlebot3_gazebo_empty_world from any directory.

The errors with the ardrone_gazebo package might be because a Gazebo process
was still running in the background, after your TurtleBot3 "mishap". Gazebo 11
isn't the most stable piece of software in the world. The container contains
two commands to help and kill processes that are still lingering in the
background:

• killall_gazebo to kill all Gazebo processes
• killall_ros to kill all ROS processes

It's advised to execute those two commands when ROS and/or Gazebo are acting up.
You could also stop the container and start a new one, but these commands make
it easier. Especially when your adding/installing extra software after starting.

I also added a start_single_ardrone_gazebo command. The name is self-explanatory.
Besides that, there's the start_pxl_drones_week_glasshouse command which will
start two AR.Drones in a glasshouse. It's a small assignment for an international
course at my uni.

I hope the above will set you up for success!