-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
@ffi.def_extern() was not called in the current subinterpreter #3282
Comments
Yep this is a cryptography issue. It will be resolved when we merge #3229 (which will happen hopefully soon-ish and release as part of You can stop the error msg by using a single global instance in mod_wsgi rather than subinterpreters by setting WSGIApplicationGroup to %{GLOBAL}, but that may not be practical for your situation. |
(Resolved by 1.7) |
Is this in a released version or still only in HEAD? |
It's in 1.7+, which was released last month. |
But I still get the annoying error: Running Ubuntu 16.04 LTS, Kodi 17.0 - but the error was with Kodi 16.1 as well |
@krogsbell You are not running cryptography 1.7. Either your system or Kodi use an old version of cryptography. |
Right I was running 1.2.3 With these two commands: sudo pip install --upgrade pip I get: But testing with: I still get: Will a reboot solve this? |
Removing python 2.7 - No good idea - Kodi do not run without ;-( |
Also experiencing this problem with Kodi while not having 1.7 available. Is there any solution to upgrading the package on Ubuntu 16.10? |
You can install the package from Ubuntu Zesty https://launchpad.net/ubuntu/zesty/amd64/python-cryptography/1.7.1-2 no conflicts and seems to work just fine |
GLOBAL is a workaround for pyca/cryptography#3282 which is fixed in cryptography > 1.7
Work for me update cryptography! |
installed kodi from ppa in ubuntu 16.04.4 and got the above error. sudo apt install python-pip did the job for me EDIT: |
I run in all this problems and solutions... Knowledge sharing is wonderful |
I'm not sure this is a problem in cryptography, but I think it might be related.
Over the past few days, I've had problems with my Apache 2.4.23 server, where it failed to correctly serve HTML files from disk over HTTPS. Restarting it solves the problem temporarily.
This Apache installation makes use of mod_wsgi (with Python 2.7.10) to run a number of WSGI applications, some of which use cryptography. In the Apache error logs, I found a lot of messages like this:
I somewhat recently upgraded from cryptography 1.3.4 to 1.5.2, so this might be related.
Any suggestions on what might be wrong here?
The text was updated successfully, but these errors were encountered: