-
Notifications
You must be signed in to change notification settings - Fork 585
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
Doesn't work on Debian Buster (10.3) and Fedora v34 - to fix in next release #787
Comments
Thanks @puchalakd, I appreciate that you take the time to investigate and share solution! This issue happens only for Debian distribution and for Buster release, thus we can't make it as a standard fix for all Linux packaged zip, or update documentation to include this fix as standard. But will keep a lookout for similar reported issues, to see if there is a way to detect and code in a fix that will fix this for Debian Buster, without breaking for other Linux distributions. Hi @siowyisheng take note on this. |
Closing the issue for now |
Thank you for providing working around. |
Many (many) thanks @puchalakd for the workaround...I was beating my head against the desk trying to figure this out. |
Many thanks to @puchalakd for this as well. Can confirm this was an issue I encountered on Fedora v34 |
Thanks @puchalakd for your workaround and @Achsheyeh @Astrogeorgeonethree @adrhine for validating that the solution works! I've looked up one of the issues that @puchalakd shared and found that the issue is due to the OpenSSL v1.02 that is used by PhantomJS is confused by the config file if OpenSSL v1.1.1 is present. Thus the hack works by directing PhantomJS to go use a dummy config file. I'll continue to look out for more feedback on how this can be handled. If doing this programmatically for all macOS/Linux TagUI it can create an environment variable that causes problems with other apps on the system that depends on OpenSSL v1.1.1. Because the export command makes the env variable persists. |
Thanks to @puchalakd. Can confirm this was an issue I also encountered on Fedora v34 |
If I run this as sudo: |
I I run this as user: phantomjs://code/bootstrap.js:113 in __die phantomjs://code/bootstrap.js:113 in __die |
Should I use a different OS than Fedora 34? I'll switch, just not to Windows. |
Hi @TetraGenius! From your run output it looks like php command is not available. Can you try running below to install PHP on your system to see that works?
|
Thanks Ken, Installing php did make a difference, but now tagui scripts are failing silently. I terminated tagui every time after waiting about two minutes using end_processes. I had everthing working on previous versions of Fedora ;( |
I also replaced phantonjs with the replacement version; then I got this: |
There may be some file permissions issue. Can you go to your tagui folder and try this to see if it is permission-related -
The tagui_chrome.in is a temporary file used for TagUI to communicate with Chrome and shouldn't be write-protected. |
I've set the directory to 777; I've also installed via npm; there it gives me this: |
Hi Theuns, thanks for sharing all these details! Below are summary of the issue you are encountering and what I found for the 3rd issue. It looks like after your Fedora OS was updated to v34, a previously working installation started to fail.
PS - Oh don't use the version from npm it is very outdated. I've stopped using that as distribution channel. |
In the meantime, I've make a note on the open issue on refreshing PhantomJS, which might solve the root cause for this raised issue around Open SSL - #932 (comment) |
Hi @kensoh, any update on this issue? I'm having similar errors as above on Ubuntu 22.04. |
The PhantomJS is refreshed for Mac version but not Ubuntu version. I have another project but have not heard issues from Ubuntu users. Can u try step 2 below to see if that works? Copying @ruthtxh |
|
Hi,
I've followed installation instruction, but it didn't work.
Quick FIX. Create an empty openssl.cnf file and set environment variable to use it.
and now it works :)
$ tagui flows/samples/1_google.tag
I found some error reports that let me find a workaround:
drwetter/testssl.sh#1117
bazelbuild/rules_closure#351
Maybe based on this you can fix that in the code?
The text was updated successfully, but these errors were encountered: