Problem with gazebo

Hi,
trying to load the environment into Gazebo, I can see it as seen in the attached image. No error occurs but the display is incorrect: the environment appears very small.

user:~$ cd ros2_ws
user:~/ros2_ws$ source install/setup.bash
user:~/ros2_ws$ ros2 launch amrj16_gazebo start_world.launch.py
[INFO] [launch]: All log files can be found below /home/user/.ros/log/2025-01-29-09-34-29-496262-1_xterm-3574
[INFO] [launch]: Default logging verbosity is set to INFO
GAZEBO MODELS PATH==/usr/share/gazebo-11/models:/usr/share/gazebo-11/models:/usr/share/gazebo-9/models:/usr/share/gazebo/models_robox:/home/user/ros2_ws/install/amrj16_description/share:/home/user/ros2_ws/install/amrj16_gazebo/share/amrj16_gazebo/models
GAZEBO PLUGINS PATH==/usr/lib/x86_64-linux-gnu/gazebo-11/plugins:/usr/lib/x86_64-linux-gnu/gazebo-11/plugins::/home/user/ros2_ws/install/amrj16_description/lib
[INFO] [gzserver-1]: process started with pid [3689]
[INFO] [gzclient -2]: process started with pid [3691]
[gzclient -2] ++ ls /usr/bin/gzclient-11.12.0
[gzclient -2] + gzclient_path=/usr/bin/gzclient-11.12.0
[gzclient -2] + DISPLAY=:2
[gzclient -2] + /usr/bin/gzclient-11.12.0
[gzserver-1] Warning [parser.cc:833] XML Attribute[version] in element[sdf] not defined in SDF, ignoring.
[gzserver-1] Warning [parser.cc:833] XML Attribute[version] in element[sdf] not defined in SDF, ignoring.
[gzserver-1] Warning [parser.cc:833] XML Attribute[version] in element[sdf] not defined in SDF, ignoring.

Hi @saxosun ,

This issue seems to be something related to the browser extensions interfering with the rosject environment, especially with the Gazebo or RViz containers.

The well known extension that causes this issue, so far, has been identified to be Quillbot.
If you have that browser extension by any chance, disable that and reload your webpage. That should fix it.
If you do not have that extension installed, try disabling any other extension(s) in your browser one by one until you have the rosject Gazebo container load without this issue.

Please let me / us know which extension caused you this issue, in case you were able to figure out the browser extension that caused you this issue, so this issue can be fixed.

If everything fails, try switching over to a chromium based browser like Google Chrome, Opera, chromium, etc.

Regards,
Girish

Hi @girishkumar.kannan,
I have not the extension you have mentioned. I have switched in Google Chrome and It works. I use Firefox currently and this is the first time that it happens without extension.
Thank you
Salvatore

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.