Virtual Machine not launching Gazebo
I am using the beta version of ROS as well as Ubuntu 16.04. When attempting to launch gazebo I get the following error:
mroscoe@ubuntu:~$ gazebo
VMware: vmw_ioctl_command error Invalid argument.
I have checked online and cannot find a solution and was hoping someone here may have run into it and knows how to work around it.
Results from running GLXGEARS:
mroscoe@ubuntu:~$ glxgears
6223 frames in 5.0 seconds = 1244.564 FPS
4971 frames in 5.0 seconds = 993.205 FPS
6041 frames in 5.0 seconds = 1208.158 FPS
5833 frames in 5.0 seconds = 1166.566 FPS
5299 frames in 5.0 seconds = 1059.721 FPS
Can you run `glxgears`?
Yes it runs with no issues (I attached the output to the question itself).
the same issue: $ gazebo VMware: vmw_ioctl_command error Invalid argument
Clean/Fresh Ubuntu 16.04 and ROS Kinetic Kame install in VMware Fusion Professional Version 8.1.1 (3771013): Gazebo crashes with the same error message. "VMware: vmw_ioctl_command error Invalid argument."
Can you try running `gzserver --verbose`? And then `gzclient --verbose`?
I have the same problem. I tried running glxgears and it worked. I also tried running 'gzserver --verbose' and then gzclient. gzserver --verbose ran perfectly but when i tried to ran gzclient --verbose i got this message: Aborted (core dumped) , and it crashed. Anybody knows how to fix the problems so that I can run gazebo?
Run gzclient in gbd, and post the backtrace.
Thnx for replying: I ran gzclien in gbd an this are my results: ( I give you the last 6 lines if this is OK?) VMware: vmw_ioctl_command error Invalid argument. [New Thread 0x7fff97fff700 (LWP 3792)] Thread 1 "gzclient" received signal SIGABRT, Aborted. 0x00007ffff647d418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
Hey. Please did you find a fix yet?
I've gotten then same error using gazebo (from ROS kinetic repos) on 16.04 in VMWare workstation 12.1.1. My host machine is a linux laptop with both nvidia and intel graphics. Interesting, I only see the problem when i have nvidia-prime set to the nvidia graphics.