-
Notifications
You must be signed in to change notification settings - Fork 159
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
Error to load the Qt platform plugin "xcb" #327
Comments
This might be because you are running on a cluster machine without a display (monitor) connected to it. You can either set
|
Hi Chengshu, thank you very much for your suggestion. I tried setting headless=True in the line as you suggested, and it worked perfectly fine when running the code in headless mode. However, I also tried to run the code on my laptop without headless mode and faced another error in the following:
That is why I unset the $DISPLAY variable. Could you please advise me on how to solve this issue if I want to run the code not in headless mode? Thank you for your time and support. |
Same here. I ran the docker command
I can confirm that the |
(for running on a local machine with a monitor attached) |
To whom it may concern,
I have encountered some issues while trying to run the demo test for iGibson. I was able to successfully install iGibson and load it in ipython without any problems. However, when I tried to run the demo test using the command
python -m igibson.examples.environments.env_nonint_example
, I received the following error message:I have also installed the latest version of Qt (QMake version 3.1 and Qt version 5.12.8 in /usr/lib/x86_64-linux-gnu), so I don't think the issue is related to the Qt installation.
Additionally, I tried to test the iGibson installation by following the instructions to run
pytest --ignore disabled --ignore benchmark
, but I received the following error message:I would appreciate any assistance in resolving these issues so that I can continue working with iGibson. Thank you for your time and attention.
The text was updated successfully, but these errors were encountered: