-
Notifications
You must be signed in to change notification settings - Fork 54
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
'GDK_IS_DISPLAY (display)' failed and Windows Subsystem for Linux. #101
Comments
Thanks @lcpt. For me errors still are there:
|
I've modified
Maybe this works. |
Thanks @lcpt . It removes those errors, but some new errors, maybe new issue needed:
and more similar errors. thanks. |
That's strange. It's always the same error, but it has nothing to do with the matplotlib issue. In my computer, it works perfectly fine ... It's quite strange. Have you changed anything else? |
Hi! @lcpt I just run again the verification tests, and it almost was Ok in everything. I only had some errors with gmsh: Thanks :) |
Different versions of GMSH create slightly different meshes with different number of nodes. This is probably the cause of this error (the mesh is perfectly fine, but XC expects a different number of nodes). Could you open a new issue for this problem?, in the interim I'll take a look on how to solve it. |
@ebrahimraeyat if the problem with the name of GeomSection objects persists, I think it's better to open a new issue. |
Thanks @lcpt. I decided to compile xc again and if errors still exist, I will open new issue about it. Thank you so much. |
I think this will probably fix the problem. I'll close this issue. You can open a new one as needed. |
@mihdicaballero has found this bug running the XC verification tests on a WSL machine running Ubuntu 20.04. The results he obtained are here.
Some tests complain about the connection to the XServer:
Unable to init server: Could not connect: Connection refused
and then they show the following messagegdk_cursor_new_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
. The test itself works as expected and returns OK.Apparently, the problem is related with the use of Matplotlib module. I've removed or commented out the lines that import this module because it's not needed unless you're debugging the code.
I've no access to an WSL machine, so I can't check if that solution works. @ebrahimraeyat, @mihdicaballero could you pull the modified verification tests and check if this workaround works?
The text was updated successfully, but these errors were encountered: