Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup Assistant Crashes on Add Robot Poses #2562

Closed
noahbuttner opened this issue Dec 1, 2023 · 3 comments
Closed

Setup Assistant Crashes on Add Robot Poses #2562

noahbuttner opened this issue Dec 1, 2023 · 3 comments
Assignees
Labels
bug Something isn't working MSA stale Inactive issues and PRs are marked as stale and may be closed automatically.

Comments

@noahbuttner
Copy link

Description

I am attempting to use the setup assistant to create a MoveIt package for a custom URDF of our robot. However, it crashes when I go to add Robot Poses. I'm new to MoveIt, so if there's a better place to put this, please let me know.

Your environment

  • ROS Distro: Humble
  • OS Version: e.g. Ubuntu 22.04
  • Source or Binary build? Source
  • If binary, which release version?
  • If source, which branch? humble
  • Which RMW (Fast DDS or Cyclone DDS)? Unsure, is there an easy way to check this?

Steps to reproduce

Tell us how to reproduce this issue. Attempt to provide a working demo, perhaps using Docker.
My URDF is in the gist, and I can provide the meshes if needed.

  • Launch the setup assistant in the above install types
  • Use the provided URDF, and import it
  • generate the collision matrix as default resolution
  • create a base fixed virtual joint as in the tutorials
  • create a planning group with all joints
  • create a pose with KDL, and then move any of the joints in the robot pose generator.

Expected behaviour

Setup assistant does not crash

Actual behaviour

Setup assistant crashes when moving any joint in the robot pose window (see backtrace below).

Backtrace or Console output

bractrace

@noahbuttner noahbuttner added the bug Something isn't working label Dec 1, 2023
Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Jan 22, 2024
@github-actions github-actions bot removed the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Feb 28, 2024
Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Apr 17, 2024
@mikeferguson
Copy link
Contributor

Since this is a source build on humble - it is almost certainly the same issue as #2980 - which appears to be an ABI issue due to differences in installed packages against the source. There's a lot more debugging notes available in the other ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working MSA stale Inactive issues and PRs are marked as stale and may be closed automatically.
Projects
None yet
Development

No branches or pull requests

4 participants