reason:
Because VNC is used to remotely control the lower computer, rviz is a graphics plug-in developed based on OpenGL. Theoretical screen parameters (the tis’ screen) need to be used. Using VNC will lead to incorrect screen parameter values, resulting in rviz errors.
resolvent:
1) Connect the display in the lower computer, and then turn on rviz on the PC enabled with VNC to temporarily solve the problem.
2) Use SSH instead of VNC to control the lower computer remotely. Pay attention to closing the VNC process running in the background, otherwise the core dump problem will occur when running rviz. In addition, due to the impact of network speed, there may be a stuck problem.
Read More:
- Rviz global status is displayed as the problem resolution of error
- When installing ROS: bash / opt / ROS / kinetic/ setup.bash : there is no file or directory
- Running realsense ROS reports an error, USB cam overflow, hardware error
- Solution to the problem that the camera can’t display when ROS running
- Resolution of problems with rviz global status displayed as error
- ROS package ROS_ astra_ Camera cannot open RGB lens
- ROS cannot download ROS melody joint state publisher GUI reference
- Solve the problem of error running xxxapplication command line is too long when compiling and running IntelliJ idea
- Idea running error running ‘application’: solution to command line is too long
- Solution to “error code is 0x4001” when Intel SGX is running
- When the spring MVC project is running on idea, an error is reported when the controller is a null pointer
- When SSM + Maven project is running, it is prompted that org.springframework.web.servlet.dispatcherserservlet cannot be found
- bash: /opt/ros/kinetic/ setup.bash : there is no file or directory
- Error running ‘Tomcat 9‘: Address localhost:1099 is already in use
- Start rqt_ Graph, prompt / opt / ROS / melody / share / PR2_ motor_ diagnostic_ Under tool plugin.xml There is something wrong with the file
- After the vs2013 + OpenGL environment is set up, there is an error in running the first program
- WSL start QT error qt.qpa.xcb : could not connect to display :0.0
- Idea for Mac setting JVM running parameters to solve running stuck problem
- SRS is started normally and there is no screen for streaming. Look at the SRS log and report an error SRS is already running
- This error may also indicate that the docker daemon is not running.