-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error #226
Comments
Hi @ChetanGaonkar and thanks for reporting the issue. The
It also seems that this was solved in later versions:
As you have kernel 5.8, this seems to be a likely cause of the problem. Are you able to upgrade the kernel or Debian? |
Dear Daniel,
I got a popup saying new version is available so I upgraded.
The older version dont have any issue as I have two PC one with older and
other with upgraded version.
I ran the phylogenies on the older one and they work well.
Thank you,
Chetan
…On Wed, Dec 8, 2021 at 1:41 AM Daniel Edler ***@***.***> wrote:
Hi @ChetanGaonkar <https://github.com/ChetanGaonkar> and thanks for
reporting the issue.
The spawn /tmp/.mount_raxmlGw2KeKS/resources/static/bin/raxml-ng EACCES
part means that raxmlGUI doesn't have access to the directory. From what I
have found it seems to be a sandboxing issue
<https://docs.appimage.org/user-guide/troubleshooting/electron-sandboxing.html>
with Debian:
AppImages based on Electron require the kernel to be configured in a
certain way to allow for its sandboxing to work as intended (specifically,
the kernel needs to be allowed to provide “unprivileged namespaces”). Many
distributions come with this configured out of the box (like Ubuntu for
instance), but some do not (for example Debian).
It also seems that this was solved in later versions
<laurent22/joplin#2246 (comment)>:
If you run the Debian 10 (Buster) stable kernel 4.19 you will still be
affected by this issue.
If you upgrade to Bullseye (which will become the new stable release in a
few months) you will not be affected.
If you install the 5.10 kernel from Buster-backports you will not be
affected.
As you have kernel 5.8, this seems to be a likely cause of the problem.
Are you able to upgrade the kernel or Debian?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJT3FMJNNC5W5UEGJHIY5NTUP4D35ANCNFSM5JSHUZ3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Ok, in raxmlGUI 2.0.6 there was a new version of raxml-ng added, maybe @jtklein knows something about this? |
In the meantime @ChetanGaonkar, if you can upgrade the kernel pleasy try that. That will help us if more get the same problem. |
I am not 100% sure how to upgrade the kernel.
Will look into it and try again
Chetan
…On Wed, Dec 8, 2021 at 11:43 AM Daniel Edler ***@***.***> wrote:
In the meantime @ChetanGaonkar <https://github.com/ChetanGaonkar>, if you
can upgrade the kernel pleasy try that. That will help us if more get the
same problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJT3FMMNIA3KLQ3ILZEHKFDUP6KKRANCNFSM5JSHUZ3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I'm having the same issue. My kernel version is 5.10-98. Keep up the good work! |
Hi @thauffe, thanks for your information! To help us check if the problem is the new raxml-ng binary since 2.0.6, can you or @ChetanGaonkar try running the 2.0.5 version and tell us how it goes? |
Hi, Version 2.0.5 works. I run a Beginning in line 85 of v205.txt:
. |
Thanks @thauffe, that is very helpful! From this we should investigate the @jtklein, do you know if the raxml-ng in 2.0.6 was compiled or signed in another way than the version in 2.0.5? Are you able to test the latest in a linux environment? We can take the opportunity to replace raxml-ng 1.0.3 with the latest 1.1.0 also. |
Hi I had to go back to the older version and ran my phylogenies.
I can send you the version and the log tomorrow if that is ok?
Regards
Chetan
…Sent from my iPhone
On Feb 18, 2022, at 5:55 AM, Daniel Edler ***@***.***> wrote:
Hi @thauffe, thanks for your information!
To help us check if the problem is the new raxml-ng binary since 2.0.6, can you or @ChetanGaonkar try running the 2.0.5 version and tell us how it goes?
—
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 were mentioned.
|
@ChetanGaonkar, we are testing a new version today, hopefully that will solve the issue. Will let you know. |
Hi all, we just released v2.0.7 that should fix this Linux issue. You should get it on the automatic update check when raxmlGUI starts. Please try and write if it solves the issue for you! |
Great, works in my case. Thank you! |
Great thanks.
Will check it out too in next few days and keep you updated.
Chetan
…On Tue, Feb 22, 2022 at 1:01 PM Torsten Hauffe ***@***.***> wrote:
Great, works in my case. Thank you!
—
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJT3FMPJRSPWNFNB4XLK6TTU4PMQZANCNFSM5JSHUZ3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Autogenerated report:
Active state:
Process: renderer
raxmlGUI 2.0.6
Electron 13.5.1
linux 5.8.0-50-generic
Locale: en-US
The text was updated successfully, but these errors were encountered: