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

rviz disappeared using moveit #11436

Closed
1 of 2 tasks
Lucaswaung opened this issue Apr 8, 2024 · 1 comment
Closed
1 of 2 tasks

rviz disappeared using moveit #11436

Lucaswaung opened this issue Apr 8, 2024 · 1 comment

Comments

@Lucaswaung
Copy link

Windows Version

Microsoft Windows [版本 10.0.19045.4170]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

when I run
roslaunch xarm7_moveit_config xarm7_moveit_gazebo.launch
rviz is running but there is nothing show in it.
image

another issue occurred when I run
roslaunch xarm7_moveit_config realMove_exec.launch robot_ip:=<my_ip_address> [velocity_control:=false] [report_type:=normal]
there is what happened, the program looped :
[INFO] [1712581059.659724, 0.000000]: Waiting for /clock to be available...
[INFO] [1712581059.660795, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller

I've tried export LIBGL_ALWAYS_SOFTWARE=1 to prohibit GPU
Additionally, roslaunch xarm_description xarm7_rviz_display.launch will show the rviz UI.

Expected Behavior

I should see the whole rivz UI

Actual Behavior

rviz is running but there is nothing show in it.
image

[INFO] [1712581059.659724, 0.000000]: Waiting for /clock to be available...
[INFO] [1712581059.660795, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller

Diagnostic Logs

No response

Copy link

github-actions bot commented Apr 8, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant