View Issue Details

IDProjectCategoryView StatusLast Update
0002848ThirdPartyContributionpublic2018-02-20 23:25
ReporterCarlos villavelazquez Assigned Tochris  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Platformubuntu 17.10OSlinuxOS Version17.10
Summary0002848: problems displaying images with paraFoam and paraview
DescriptionI've been trying to use openFoam on ubuntu 17.10 and on ubuntu-gnome 16.04. OpenFoam works very well, however when I open paraFoam and try to visualize the images, nothing happens. It seems to be reading the data but it doesn't show any image. I've been running openFoam and paraview on Ubuntu Mate 16.04 and everything works fine.
TagsNo tags attached.

Activities

Carlos villavelazquez

2018-02-18 12:38

reporter  

wyldckat

2018-02-18 13:12

updater   ~0009328

At first I was going to suggest that you would re-build ParaView with legacy OpenGL support... but I've re-checked the attached image and you're already using that build of ParaView 5.4.0.

We need more information in order to try and deduce what's going on wrong:

 1- Did ParaView give any error messages?

 2- The versions of Ubuntu and respective desktops (Gnome and Mate) that you have tested this on, are they being run in the same machine or in different machines or inside virtual machines?

 3- I'm a bit confused about the desktop software names being used in each installation, so please confirm:

   a. Is Gnome being used in both Ubuntu 17.10 and 16.04 without success?

   b. Or have you used Ubuntu Unity on 17.10?

 4- Which Graphics card or integrated CPU+GPU are you using on each machine?

 5- Which GPU drivers are you using on each Ubuntu installation?

 6- On Ubuntu Gnome, try disabling the animations, as instructed here: https://askubuntu.com/questions/654976/gnome-3-14-how-to-disable-window-effects

 7- If #6 didn't work, check any chance you can test with Gnome 3 Classic mode?


If my guess is correct, the problem is that the normal Gnome 3 (and possibly Unity as well) is taking GPU resources away from ParaView, either due to a bug in the graphics driver or due to something broken in Gnome. Or Gnome is overwriting the rendered 3D image that ParaView has done.

Carlos villavelazquez

2018-02-19 10:07

reporter  

Ubuntu Mate 16.04.png (1,935,899 bytes)

Carlos villavelazquez

2018-02-19 10:10

reporter  

Ubuntu 17.10.png (1,493,770 bytes)

Carlos villavelazquez

2018-02-19 10:16

reporter   ~0009329

Hi. Thanks a lot for the answer.

I've been working on a MacBook Pro with "Parallels" for the virtual machines for around 6 months. I haven't had any problem with OpenFoam or paraFoam on "Ubuntu Mate 16.04". I'm running the virtual machine with the following characteristics: 4 cores, 8192 MB memory, 256 Graphics memory and the graphics card is an AMD Radeon pro 450 openGL engine.

I decided to use "Ubuntu 17.10" following the same characteristics for the "Ubuntu Mate 16.04" on the same computer with Parallels, and with the same openFoam problem. As you can see in the attached image, paraFoam doesn't display any image!! Thanks

wyldckat

2018-02-19 20:32

updater   ~0009334

From your description, all symptoms point to a problem that usually occurs when running most operating systems inside a virtual machine: there is no 3D acceleration or it's not properly supported.

In other words, the virtual machine inside Parallels does not have direct access to the real graphics card, therefore it's not able to provide a proper 3D experience, as required by ParaView.

And even though this ParaView 5.4.0 is built with the old OpenGL support, the Gnome 3 desktop manager (shown in the latest image you provided) breaks the 3D render, because the desktop manager is not letting the 3D information pass through.

Possible solutions:

1- Stay with Ubuntu 16.04, until 18.04 is released. The reason is that Ubuntu 16.04 is a long term release that is supported at least until the end of 2020. Similarly 18.04 will be supported at least until the end of 2022.

2- With either Ubuntu 17.10 or 18.04, you should use one of the less demanding desktop managers: MATE, LXDE or XFCE are the usual choices. With either Ubuntu versions, you can always install another desktop manager. If look online for how to install MATE in Ubuntu 17.10 (without the need to reinstall the whole virtual machine), you should find several instructions.

3- Or try switching to Gnome Classic... you can search online for "Ubuntu 17.10 Gnome Classic" (without the quotes) and you should find several guides.


Please let us know if any of the solutions above work for you.

Carlos villavelazquez

2018-02-20 10:24

reporter   ~0009335

Hello. You were right, I switched ubuntu 17.10 to gnome flashback or classic and paraFoam started to work!!!
Thanks a lot!!

I installed the following packages to change to gnome flashback.
sudo apt-get install gnome-panel gnome-flashback gnome-session-flashback indicator-applet-appmenu

wyldckat

2018-02-20 10:58

updater   ~0009336

Many thanks for your feedback! I'm very glad it worked as expected!

----

@Chris: Although it was already discussed in the past that an FAQ page isn't sustainable, and even though the next generations of ParaView will likely drop support for the old OpenGL, the information above is still useful for people who are using OpenFOAM 5 + ParaView 5.4.0 on Ubuntu within a virtual machine. At least an indication in the pages that detail how to install the packages for Ubuntu:

 - If using Ubuntu within a virtual machine, then in order for ParaView to work properly, please use a low resource desktop manager, such as Gnome 3 Classic, MATE, LDXE, XFCE or similar.

chris

2018-02-20 12:53

manager   ~0009337

@wyldckat: We definitely need to make a note about this with the installation instructions. But we need to offer an efficient solution with precise instructions.

To do this, we need to really understand what is causing the problem. I suspect it is that 17.10 uses the Wayland display server by default instead of Xorg. Wayland doens't seem to work with certain graphics cards so it also could have nothing to do with the Virtual Machine.

If the display server is the issue, it appears that you can switch to Xorg at the login screen:
https://itsfoss.com/switch-xorg-wayland/

... and you wouldn't need to install flashback/classic/vanilla.

If this is not the issue, can we simplify instructions? For example, the following site:
https://www.omgubuntu.co.uk/2017/10/install-vanilla-gnome-shell-ubuntu-17-10

... seems to advocate just:
sudo apt install gnome-session

That claims to install "Vanilla" Gnome, @Carlos used "Flashback" which I believe is "Classic". What's the difference between "Vanilla" and "Flashback/Classic"?

Anyway, this may not be necessary. If it is Wayland, it is a 17.10 issue, which will go away in 18.04 LTS because Ubuntu are reverting back to Xorg.

wyldckat

2018-02-20 15:06

updater  

Session_options.PNG (181,496 bytes)   
Session_options.PNG (181,496 bytes)   

wyldckat

2018-02-20 15:06

updater   ~0009338

@ Carlos villavelazquez: Please try logging in by using the "Ubuntu on Xorg" option, shown in the attached image "Session_options.PNG", to check if it can also solve the problem, or if it also has the same problem with not showing the 3D images.

----

@Chris: I'm unable to reproduce the problem, but I can say with 100% certainty that "gnome-session" is not the same as the classic/flashback.
The vanilla version is the standard Gnome 3 configuration, while the one that Ubuntu 17.10 uses is its own configuration that relies on Gnome 3.

The term "Classic" or "Flashback" is allegedly the same, although it has changed names between the two a few times over the years, if I remember correctly. The idea is that this mode will use an interface functionally similar to Gnome 2, but using Gnome 3.

I've attached the image "Session_options.PNG", which allows us to see the various desktop manager options available for logging in Ubuntu 17.10, after installing both the flashback and the vanilla versions of Gnome.
Note: These options only appear after rebooting, it's not enough to simply logout after installing.

Carlos villavelazquez

2018-02-20 20:49

reporter   ~0009339

Dear Chris and Bruno... I'll try to explain the problem and how we solved it... see the file ChrisQuestions2.pdf

Thanks a lot
ChrisQuestions2.pdf (244,243 bytes)

wyldckat

2018-02-20 22:02

updater   ~0009340

Dear Carlos, many thanks for the detailed explanation and screenshots of how the virtual machine within Parallels was configured! As well as the indication that Virtualbox wasn't very stable on your machine.

May I ask you to make another small test? I've looked up what the "Enabling Vertical Synchronization" option does in Parallels in the 'Graphics' section and the following page states: http://download.parallels.com/desktop/v10/docs/ko_KR/Parallels%20Desktop%20User%27s%20Guide/33143.htm

    Sometimes in games and 3D applications, a newly rendered frame may overlap a previously rendered one and then screen tearing happens.

If possible, my request is that you try to turn off this option "Enabling Vertical Synchronization" (although it's meant to solve the problem they explain in the manual), then use the "Ubuntu on Xorg" desktop manager, to check if ParaView still has the same problems with the 3D rendering. It probably won't solve the issue, but I just want to confirm this detail.

chris

2018-02-20 22:15

manager   ~0009341

Thanks for the feedback Carlos.

I think we need to make a note on the installation pages as @wyldckat originally suggested, along the lines of "If ParaView shows a blank screen with Ubuntu on a VM, try Gnome Classic/Flashback".

In summary, for the record:
- This is a macOS VM issue.
- The macOS built in "Parallels" VM doesn't work with the Ubuntu 17.10 desktop, but works with the Gnome Classic/Flashback.
- VirtualBox works with Ubuntu 17.10 desktop with Xorg (Wayland is unreliable), but lacks some features like shared folders, spanish keyboard.

chris

2018-02-20 23:23

manager   ~0009342

Added item 2 at:
https://openfoam.org/download/5-0-ubuntu/#installation-problems

chris

2018-02-20 23:25

manager   ~0009343

Thanks Carlos. Thanks @wyldckat. Please reopen if there's additional information that comes to light.

Issue History

Date Modified Username Field Change
2018-02-18 12:38 Carlos villavelazquez New Issue
2018-02-18 12:38 Carlos villavelazquez File Added: Screen Shot 2018-02-18 at 1.34.16 PM.png
2018-02-18 13:12 wyldckat Note Added: 0009328
2018-02-19 10:07 Carlos villavelazquez File Added: Ubuntu Mate 16.04.png
2018-02-19 10:10 Carlos villavelazquez File Added: Ubuntu 17.10.png
2018-02-19 10:16 Carlos villavelazquez Note Added: 0009329
2018-02-19 20:32 wyldckat Note Added: 0009334
2018-02-20 10:24 Carlos villavelazquez Note Added: 0009335
2018-02-20 10:58 wyldckat Note Added: 0009336
2018-02-20 10:58 wyldckat Assigned To => chris
2018-02-20 10:58 wyldckat Status new => assigned
2018-02-20 10:58 wyldckat Priority high => normal
2018-02-20 12:53 chris Note Added: 0009337
2018-02-20 15:06 wyldckat File Added: Session_options.PNG
2018-02-20 15:06 wyldckat Note Added: 0009338
2018-02-20 20:49 Carlos villavelazquez File Added: ChrisQuestions2.pdf
2018-02-20 20:49 Carlos villavelazquez Note Added: 0009339
2018-02-20 22:02 wyldckat Note Added: 0009340
2018-02-20 22:15 chris Note Added: 0009341
2018-02-20 23:23 chris Note Added: 0009342
2018-02-20 23:25 chris Status assigned => closed
2018-02-20 23:25 chris Resolution open => fixed
2018-02-20 23:25 chris Note Added: 0009343