How to remove OUTPUT MSG dialog box

I am running paraview on wsl ubuntu. I am trying to close the dialog box of output msgs but just to fail. ‘X’ button does not work nor does clear no anything. Why is it so? How to resolve it?

1 Like

Strange. Seems like some kind of event might not be getting through? Can you try docking it in the window and then closing it? You might also be able to turn it off via either the View or Window menu (I can’t remember which off-hand).

Same type of problem here while using WSL. In my case, the message below is also displayed in the terminal.

Has anyone found a solution? This is super annoying.

(  32.069s) [paraview        ]  
vtkTextureObject.cxx:1025   ERR| 
vtkTextureObject (0x562e7b04b720): Attempt to use a texture buffer exceeding your hardware's limits. 
This can happen when trying to color by cell data with a large dataset.
Hardware limit is 65536 values while 71240 was requested.

I see a similar message about texture buffers and I also have issues with the window not wanting to stay in front, and not wanting to accept mouse events. I haven’t found a solution yet, except to move the window to the lower right of the screen before using the mouse on the menus. It is a very strange behavior, probably due to a bug in event translation between windows and WSL. AFAIK there is no fix yet.


Thank you for your comment @aron.helser.

I also have a similar crash when importing the vtk library in python. I suppose this stems from the same problem. E.g.

import vtkmodules.all as vtk

reader = vtk.vtkXMLUnstructuredGridReader()

mapper = vtk.vtkDataSetMapper()

actor = vtk.vtkActor()

renderer = vtk.vtkRenderer()
render_window = vtk.vtkRenderWindow()
render_window_interactor = vtk.vtkRenderWindowInteractor()
renderer.SetBackground(0.1, 0.1, 0.1)

gives an error in the 2 last lines of code

libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/ cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
2023-10-18 14:20:19.377 (   0.222s) [        A6E60740]vtkXOpenGLRenderWindow.:651    ERR| vtkXOpenGLRenderWindow (0x2c30a30): Cannot create GLX context.  Aborting.

Actually, visualizing results with paraview/vtk library is the last bit to move my workflow to Linux (WSL) altogether, so I’m longing for a solution. Please let us know when there’s a fix! :slight_smile:

Regarding “message output”, if you Edit>‘Reset to default setting’, then this window gets docked can be close. But everything gets messed if it is dragged and undocked.

“Choose preset” window also doesn’t accept mouse events. i guess it has to do with some type of not-docked windows.
Also, if a docked window (properties, information, etc…) is drag/undocked, afterwards doesn’t accept mouse events anymore.

“Choose preset” window problem only occurs in ParaView version 5.12.0.
Same behaviour in Ubuntu 22.04 and OpenSuse 15.5 running in WSL.

Perhaps there’s some configuration interfering? Does paraview --dr also have this problem? If so, can you please document how to make it occur from that state and file an issue?

Yes, also occurs with “paraview --dr”.

It has nothing to do with specific states or files. This occurs in WSL2, under Windows 11, using both Ubuntu 22.04 and OpenSuse 15.5. It’s very easy to replicate.

To sum up,

  1. The ‘Output Messages’ window when undocked, you can’t dock it any more or resize it, but you can still close it or select the checkboxes. If it pops up automatically, it becomes completely non-responsive. The only option is to close it in the ‘View’ menu. It’s annoying because you’re not able to choose where it will pop up. ‘Edit’ > ‘Reset To Default Settings’ is the only way i found to dock it again.

  2. In v5.12.0, the ‘Color Map Editor’ > ‘Choose Preset’ window is always non-responsive to mouse events, and even with TAB you can’t move to all checkboxes. It gets stuck in the default color presets displayed, and you can’t select the other groups o presets (linear, diverging, etc). This problem doesn’t occur in 5.11.2.

1 Like

Please file an issue so that we can track it there. I don’t have WSL2 around, so I can’t test it myself.

done. Thank you!

I see, thanks.