Peacock won't run. It says aborted about 2 minutes after I run it.

[GraphicsMonster]

I installed moose pretty recently and for visualization would like to use peacock as that's what the rest of the team is using.
I set things up, added the path in .bashrc, set up xlaunch, initiated Xlaunch before opening the terminal and when I navigate to the exmaples directory in moose and run moose for the example I built it returns a simple "Aborted" message and no more information.

Would appreciated any sort of help. Thanks a bunch!

[milljm]

Please do not post images of text. Using images prevents any sort of search for the text contained within the image.

Are you able to display any sort of X functionality? xeyes for example?

[milljm]

Interesting, I must not have hit "reply". I had something all typed up... but I do not see my post!

Do you mean to say that peacock launches correctly? But fails to run the problem?

Whats happens when you call peacock directly?

cd ~/moose/examples/ex01_inputfile
../../python/peacock/peacock -i ex01.i

Also, lets try to run a render test (tests most Peacock VTK/Qt/PyQt functionality):

export PYTHONPATH=$HOME/moose/python
cd ~/moose/python/chigger/tests/writers
./writers.py

[GraphicsMonster]

Calling peacock through path results in the same segment fault.

Peacock launches correctly and I even see a new peacock window open that says looking for executable and then the terminal says found executable with a path to it and then suddenly it shows segmentation fault and the entire operation drops right there.

Running ./writers.py gives:

(moose) devansh@HP_15s:~/moose/python/chigger/tests/writers$ ./writers.py Traceback (most recent call last): File "/home/devansh/moose/python/chigger/tests/writers/./writers.py", line 15, in <module> import chigger ModuleNotFoundError: No module named 'chigger'

Do I need to manually install this library? Is this holding it back?

[cticenhour]

Based on that output you need to make sure the MOOSE Python modules are available, as @milljm mentioned in his suggestion:

export PYTHONPATH=$PYTHONPATH:$HOME/moose/python

chigger is supplied within that directory.

[milljm]

Hmm interesting. I think Peacock at that moment (when its up and now searching for an executable) will have something to do with Peacock finding the executable, and something going wrong when the executable is run with the json dump args.

Can you perform the following, and report back if it completes, or dies (it will print a lot of information to the screen)?

cd ~/moose/examples/ex01_inputfile
./ex01-opt --json

[GraphicsMonster]

This does complete. Ends with End JSON Data

[GraphicsMonster]

If you run the input file on the command line manually, does it still segfault?

cd ~/moose/examples/ex01_inputfile
./ex01-opt -i ex01.i

No it works manually. Gives me a "solve converged" message.
No luck with peacock though.

[GraphicsMonster]

Looks like it's printing a huge json file.

Dump also returns loads of text but in another format I reckon.

[milljm]

hmm. I am not sure why it would segfault. I can only guess Peacock is parsing the output incorrectly. I'll need to think about what might be happening here.

Can you try to use Peacock on a moose_test-opt test?

cd moose/test
make
cd tests/kernels/simple_diffusion
peacock -i simple_diffusion.i

I wrote that quick, hopefully no syntax errors

Unfortunately I am heading home for the day... I'll have to pick this back up tomorrow. I may request to stay home so I can access a Windows machine in order to troubleshoot.

[GraphicsMonster]

Hey! Just checking in. Have you been able to solve the issue? Sorry I had my exams come up last week.
I'm still seeing the same issues with no progress.

would really appreciate any help.

[GraphicsMonster]

A little update: Only running "peacock" with no input file specified does open a window with no input files but inside the window as soon as i hit the input files option the window gets terminated.
Trying to open a specific input file still gives segfault.

[milljm]

Is this Windows 11? I am reading over our thread, and I believe I mentioned turning off Access Control in VcXsrv. But if this is Windows 11, using VcXsrv might actually be the issue. As soon as Peacock tries to utilize OpenGL, it freezes/crashes.

This section from my previous link: Problems running Peacock:

From what I am reading, Windows 11 folks will enjoy native GL support without needing to Install VcXsrv. Their only pre-requisite is to install their optimized video card drivers (NVIDIA or AMD). While the rest of us still on Windows 10 continue to need VcXsrv. Considering myself something of a power user, even I was confused on Microsof's literature about WSL2/native GL support (but not on Windows 10).

If you are using VcXsrv, perhaps we need to tinker with some of its options. I am referring to these:

(specifically the Native opengl checkbox).

Or, simply uninstall VcXsrv and try to use Window's 11 native opengl support (if you are using Windows 11)