Intermittent Failure Running Example

[Rud Merriam]

I get an intermittent failure to run. I maybe the same as reported by @dan77062 but not 100% sure so creating a separate issue. I'd guess 1 out of 3 times I get this error. Sometimes it is once or twice in a row but then I'll get a few runs without an error.

Turned on verbose to try to get more information.

[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 192.168.1.12
[INFO] [1551646884.816133, 0.000000]: Loading model XML from ros parameter sensors_description
[INFO] [1551646884.818566, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[INFO] [1551646884.842413, 0.000000]: Loading model XML from ros parameter robot_description
[INFO] [1551646884.848156, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  154 (DRI2)
  Minor opcode of failed request:  3 (DRI2CreateDrawable)
  Resource id in failed request:  0x5000002
  Serial number of failed request:  35
  Current serial number in output stream:  37
[INFO] [1551646884.949517, 0.000000]: Loading model XML from ros parameter robot_description
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  154 (DRI2)
  Minor opcode of failed request:  3 (DRI2CreateDrawable)
  Resource id in failed request:  0x5200002
  Serial number of failed request:  35
  Current serial number in output stream:  37
[INFO] [1551646884.956349, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
Aborted (core dumped)
================================================================================REQUIRED process [gazebo-2] has died!
process has died [pid 19799, exit code 134, cmd /opt/ros/melodic/lib/gazebo_ros/gzserver -u --verbose -e ode /tmp/ariac/gear.world __name:=gazebo __log:=/home/rmerriam/.ros/log/7f931828-3df7-11e9-b574-40167e229df0/gazebo-2.log].
log file: /home/rmerriam/.ros/log/7f931828-3df7-11e9-b574-40167e229df0/gazebo-2*.log
Initiating shutdown!
================================================================================
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
[gazebo_unpauser-18] killing on exit
[ariac/arm1/arm_controller_spawner-17] killing on exit
Traceback (most recent call last):
  File "/opt/ros/melodic/lib/osrf_gear/gazebo_unpauser.py", line 30, in <module>
    rospy.wait_for_service('/gazebo/unpause_physics')
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 161, in wait_for_service
    time.sleep(0.3)

[Shane Loretz]

1/3 is very frequent. I haven't seen this one on my machine.

Would you mind posting the output of this command?

apt list --installed | grep -e ignition -e sdformat -e gazebo

[Rud Merriam]

I' m away from the desktop system for awhile. Will post when I'm there.

[Rud Merriam]

gazebo9/unknown,now 9.7.0-1~bionic amd64 [installed,automatic] gazebo9-common/unknown,unknown,now 9.7.0-1~bionic all [installed,automatic] gazebo9-plugin-base/unknown,now 9.7.0-1~bionic amd64 [installed,automatic] libgazebo9/unknown,now 9.7.0-1~bionic amd64 [installed,automatic] libgazebo9-dev/unknown,now 9.7.0-1~bionic amd64 [installed,automatic] libignition-cmake-dev/unknown,now 0.6.1-1~bionic amd64 [installed,automatic] libignition-common/unknown,now 1.1.1-1~bionic amd64 [installed,automatic] libignition-common-dev/unknown,now 1.1.1-1~bionic amd64 [installed,automatic] libignition-fuel-tools-dev/unknown,unknown,now 1.2.0-1~bionic all [installed] libignition-fuel-tools1-1/unknown,now 1.2.0-1~bionic amd64 [installed,automatic] libignition-fuel-tools1-dev/unknown,now 1.2.0-1~bionic amd64 [installed,automatic] libignition-math4/bionic,now 4.0.0+dfsg1-4 amd64 [installed,automatic] libignition-math4-dev/bionic,now 4.0.0+dfsg1-4 amd64 [installed,automatic] libignition-msgs/bionic,now 1.0.0+dfsg1-5 amd64 [installed,automatic] libignition-msgs-dev/bionic,now 1.0.0+dfsg1-5 amd64 [installed,automatic] libignition-transport4/bionic,now 4.0.0+dfsg-4 amd64 [installed,automatic] libignition-transport4-dev/bionic,now 4.0.0+dfsg-4 amd64 [installed,automatic] libsdformat6/unknown,now 6.2.0-1~bionic amd64 [installed,automatic] libsdformat6-dev/unknown,now 6.2.0-1~bionic amd64 [installed,automatic] ros-melodic-gazebo-dev/bionic,now 2.8.4-0bionic.20180706.234303 amd64 [installed,automatic] ros-melodic-gazebo-msgs/bionic,now 2.8.4-0bionic.20181112.202939 amd64 [installed,automatic] ros-melodic-gazebo-plugins/bionic,now 2.8.4-0bionic.20181117.185301 amd64 [installed,automatic] ros-melodic-gazebo-ros/bionic,now 2.8.4-0bionic.20181117.190127 amd64 [installed,automatic] ros-melodic-gazebo-ros-control/bionic,now 2.8.4-0bionic.20190221.010412 amd64 [installed,automatic] ros-melodic-gazebo-ros-pkgs/bionic,now 2.8.4-0bionic.20181117.193954 amd64 [installed,automatic] sdformat-sdf/unknown,unknown,now 8.0.0~pre4-1~bionic all [installed,automatic]

[Rud Merriam]

I'm going to mark it resolved since I'm not seeing it happen. Suspect it may be related to the NVDIA drivers that cause some other issues.