Segmentation fault from Peacock on Big Sur with the latest package #19357
Answered
by
eastglow-zz
eastglow-zz
asked this question in
Q&A Getting Started
-
|
Hi, I'm trying to use Peacock on my laptop with Big Sur presuming Peacock would also work fine via the updates of #19230. I got most of the test passed and no fails. But when I try to run peacock, I'm still getting a segmentation fault error. Is there any workaround to make Peacock work? Thanks advance. The error log is attached below: [milljm: edit to include pre-formatted text] |
Beta Was this translation helpful? Give feedback.
Answered by
eastglow-zz
Feb 2, 2022
Replies: 5 comments 23 replies
-
|
I am getting the same error on an Intel Mac running Monterey, MOOSE has passed all tests. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Dear John, Wondering if you have fixed this problem? Because I am having the same issue now on Mac Monterey. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hello The updates in #19230 will not have fixed Peacock on Big Sur or Monterey. Guillaume |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
We don't have a newer version of pyQt for Python 3.8 or 3.9, so were capped at 3.7 for the moment, which I'm seeing was selected correctly in the output above. Regarding this particular segmentation fault, the basic set of peacock tests we perform for updates like this passed successfully, but you also might be hitting a corner case here. I might have missed something - what were you trying to do in peacock that triggered this? As I am not a peacock expert (and also in and out of internet service on vacation), I will have to defer to someone else for in-depth troubleshooting. @milljm @loganharbour do either of you know someone who uses Peacock more regularly and might be able to assist? |
Beta Was this translation helpful? Give feedback.
-
|
I just simply executed the binary file even without specifying any input file. When I prompt 'peacock', it hangs a while like 2 seconds and crashes with the segmentation fault. It doesn't even start or show any GUI. |
Beta Was this translation helpful? Give feedback.
-
|
hi, wondering if you have fixed this problem? Because I am having the same errors when running the peacock on Mac Monterey. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
Hi thanks for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
Merely making the changes outlined in the pull request will not create new packages for you. As @milljm mentioned, no new packages will be made until the request is merged. As you are new to moose and git, I would highly recommend waiting until this code is merged and a new package is built with our testing systems. This should happen relatively soon - likely a day or two. |
Beta Was this translation helpful? Give feedback.
-
|
The files you are seeing as modified in the MOOSE repository, are Conda recipes which build the packages you all install from our public Conda package channel. e.g. when you run this; you are grabbing files from https://conda.software.inl.gov/public. My PR has not updated this URL/location yet, because it is failing. So by pulling my PR, and trying to run Peacock, you've done nothing new. You will have to build moose-libmesh and moose-tools using |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for all the replies! Maybe I could try to look into the conda-forge and see what I can do. And as @cticenhour mentioned, a new package (which may help solve the Peacock problem on Monterey?) will be ready soon, and may I ask where I can find this new package when it is ready and what I should do with it? |
Beta Was this translation helpful? Give feedback.
-
|
When the package is ready, all you will need to do is |
Beta Was this translation helpful? Give feedback.
-
|
I started using Paraview again ✔️
…Sent from my iPhone
On Jan 25, 2022, at 1:32 PM, Jason Miller ***@***.***> wrote:
I am currently working towards a possible solution. The latest libraries Peacock requires, seems to have been built with the proper version of LLVM/Clang MOOSE requires.
I have PR in place that (while works on my Monterey machine) will hopefully solve this issue: #20128
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
11 replies
-
|
Seems like you have permission on that file. Somehow it could not run it to generate the json file. |
Beta Was this translation helpful? Give feedback.
-
|
Please see below. |
Beta Was this translation helpful? Give feedback.
-
|
it says no executable found. Can you please give us the output of |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I reset everything and found be able to run Peacock! Many thanks for your patient help! |
Beta Was this translation helpful? Give feedback.
-
|
Also, I just realized you invoked peacock using None of our Conda end-user instructions require the use of sudo (part of the reason we wanted to move to Conda!). |
Beta Was this translation helpful? Give feedback.
-
|
As per the news about the latest package from @milljm, my Peacock works well on my Big Sur with Intel silicon after updating both the environment and MOOSE code. I completely removed MOOSE code and cloned it again for the clean reinstallation, and it worked. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
GiudGiud
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the news about the latest package from @milljm, my Peacock works well on my Big Sur with Intel silicon after updating both the environment and MOOSE code. I completely removed MOOSE code and cloned it again for the clean reinstallation, and it worked. Thanks!