Husarion-rplidar snaps fails and remains inactive

1

Hi,

I have a rosbot-xl with the autonomy configuration (with the slamtech rplidar s3, and oak-d-pro camera). I was able to set it up some months back and everything was running fine. But recently i noticed that the husarion-rplidar snap keeps failing and remains inactive. When i tried to start it in interative mode, i get this error:

husarion@husarion:/var/snap/rosbot/common$ sudo husarion-rplidar
Found serial port: /dev/ttyUSB0
Specified serial port exists: /dev/ttyUSB0
Running with options: channel_type:=serial serial_port:=/dev/ttyUSB0 serial_baudrate:=1000000 frame_id:=laser inverted:=false angle_compensate:=true scan_mode:=DenseBoost
[INFO] [launch]: All log files can be found below /root/snap/husarion-rplidar/39/ros/log/2026-06-11-11-01-00-635788-husarion-184802
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [rplidar_node-1]: process started with pid [184804]
[rplidar_node-1] /snap/husarion-rplidar/39/opt/ros/snap/lib/rplidar_ros/rplidar_node: symbol lookup error: /snap/husarion-rplidar/39/opt/ros/underlay_ws/opt/ros/jazzy/lib/libfastrtps.so.2.14: undefined symbol: _ZN8eprosima7fastcdr3Cdr9serializeERKh
[ERROR] [rplidar_node-1]: process has died [pid 184804, exit code 127, cmd ‘/snap/husarion-rplidar/39/opt/ros/snap/lib/rplidar_ros/rplidar_node --ros-args -r __node:=rplidar_node -r __ns:=/ --params-file /tmp/launch_params_ucqxx9ef -r /tf:=/tf -r /tf_static:=/tf_static’].

I would appreaciate your assistance.Thank you

2

Hi @Kenneth_Egwu,

Please try this:

# Revert ros-jazzy-ros-base dependency
sudo snap revert ros-jazzy-ros-base
sudo snap refresh --hold ros-jazzy-ros-base

This is most likely caused by a recent update to the ros-jazzy-ros-base snap dependency. I’ll try to remember to let you know when the issue is resolved on the main distribution channel.

Let me know if it helped.

3

Hi @RafalGorecki

Thank you this suggestion fixed the issue I was having.

Quick question: Do you know if this issue has been resolved now?