View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004057 | OpenFOAM | Bug | public | 2024-02-23 14:14 | 2024-03-26 01:34 |
| Reporter | Ulrich | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | Ubuntu | OS Version | 22.04 LTS |
| Product Version | 11 | ||||
| Summary | 0004057: ParaFoam does not start | ||||
| Description | The Ubuntu Linux is installed on WSL 2, Windows 10 OpenFOAM 11 is installed according to the following instruction: https://openfoam.org/download/windows/ When launching paraFoam in OpenFOAM 11 environment in the pitzDailySteady test case no window opens but the following message appears: qt.qpa.xcb: could not connect to display 172.24.192.1:0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. I tried to change DISPLAY to "export DISPLAY=:0" but then a segmentation fault with the attached error message occours. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Today I installed the standard paraview with: sudo apt-get update sudo apt-get -y install paraview With DISPLAY=:0 it opens without problems. But with DISPLAY=172.24.192.1:0 as set by echo "export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0" >> ${HOME}/.bashrc it again gives the following message: qt.qpa.xcb: could not connect to display 172.24.192.1:0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted Setting display back to DISPLAY=:0 and loading openfoam environment with source /opt/openfoam11/etc/bashrc then starting paraview again gives the segmentation fault documented in the attached paraFoam.zip. I've got the impression that something with the openfoam environment does not fit in my system. |
|
|
Setting ParaView_GL=system or ParaView_GL="" fixes this on my install (OpenFOAM-11 in Ubuntu 22.04 on WSL2 Windows 11 23H2). Seems to be due to an older fix due to a rendering bug in ParaView. The variable itself is defined in etc/config.sh/paraview (https://github.com/OpenFOAM/OpenFOAM-11/blob/71b07bb46985607e3b78e9404e8b5129989de411/etc/config.sh/paraview#L69). Installing Mesa drivers (mesa-va-drivers) did not help. |
