-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Some questions about peacock #24164
-
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment · 8 replies
-
I recall this issue may be related to the underlying application no longer able to launch. Can you enter your 'moose' environment and perform a mamba deactivate
mamba activate moose
mamba list Next, I'd like to run the actual app, see if that works: cd ~/projects/moose/modules/heat_conduction
./heat_conduction-opt --dump You don't have to report everything this command prints out (its a lot). All I am after, is if this command succeeds or fails in some way. Peacock runs the above command to produce the Input parameters available to display. If it fails, I can see Peacock seg faulting. Also, regardless what happens, the next thing I want you to try is to delete head_conduction-opt, and then run Peacock. Without a binary, Peacock will be forced to just "load up". And this would simply test that the issue not exactly a Peacock-only one. cd ~/projects/moose/modules/heat_conduction
rm heat_conduction-opt
mamba deactivate
mamba activate peacock
peacock Also, if you can, please paste the text of the above output, instead of a screen shot of text. It help to use text instead so "searches" among our Discussions pages actually produce real results for others to find, if in the event they are running into the same error as you. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
What distribution of Linux is this? And at what version? I'll try to reproduce the issue on my end. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I use the WSL 2 and the distribution of Linux is Ubuntu 18.04.5. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Whats interesting is that you are using the Graphical GUI of Linux inside WSL 2. I am not familiar with running in this scenario. I like it! But this is something I have no experience doing. We usually instruct folks how to connect an Xhost served by native windows. Off topic, can you tell me how you managed to start up GNOME (or... is that Xfree86, there are so many windows managers) while inside WSL2? Was it a simple I don't think Windows is getting in the way, so I'll try and treat this as a native Ubuntu 18 install on my end. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I use the VcXsrv and the xfce4 to open the Graphical GUI of Linux inside WSL 2. I'm not sure if this is what you ask. If you want to try this, you should first install VcXsrv, and then install the xfce4 use
After this, you need to configuration environment |
Beta Was this translation helpful? Give feedback.
All reactions
-
Segmentation fault(core dumped) |
Beta Was this translation helpful? Give feedback.
All reactions
-
First read the posting guidelines. Then see that posting on old threads is not the way to do this. You should be making your own discussions post and include more details. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Ok sir, sorry for this actually I'm getting the same kind of error asked in this question that's why. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
Whats interesting is that you are using the Graphical GUI of Linux inside WSL 2. I am not familiar with running in this scenario. I like it! But this is something I have no experience doing. We usually instruct folks how to connect an Xhost served by native windows.
Off topic, can you tell me how you managed to start up GNOME (or... is that Xfree86, there are so many windows managers) while inside WSL2? Was it a simple
apt-get install
process? Edit: I'd like to know, because I think I'd like to improve our instructions on doing it this way instead of using Windows!I don't think Windows is getting in the way, so I'll try and treat this as a native Ubuntu 18 install on my end.