Closed NicosKaralis closed 10 months ago
deathaxe
commented
1 year ago That's a separate issue, related to PC 4.0 not being able to resolve compatible libraries for your version of ST, platform and CPU architecture. Could you please file a separate issue for that, to avoid cluttering this discussion with off-topics?
benfrain
commented
1 year ago That's a separate issue, related to PC 4.0 not being able to resolve compatible libraries for your version of ST, platform and CPU architecture. Could you please file a separate issue for that, to avoid cluttering this discussion with off-topics?
sure: https://github.com/wbond/package_control/issues/1651 thanks
hteumeuleu
commented
1 year ago ln -sf /opt/homebrew/Cellar/openssl@1.1/1.1.1u/lib/libcrypto.dylib /usr/local/lib/It works for me too, but the base path is different on Apple M2 Pro, macOS Ventura 13.5
This one worked for me on macOS Ventura 13.5.1. Thank you!
rsms
commented
1 year ago Package Control will be uppraded next time package update is triggered, either by automatic updates at ST startup or by manually calling "Package Control: Upgrade All Packages/Overwrite All" via Command Palette.
In case PC3.x is not working, you can
- download https://github.com/wbond/package_control/releases
- call Main Menu > Preferences > Browse Packages...
- navigate to to ../Installed Packages
- move downloaded package into Installed Packages and rename it to Package Control.sublime-package (replace the
.by).
This worked for me
pohongying
commented
1 year ago yes ,I have same situation with you and i quickly solve this problems make me a headache when finally i delete another openssl.Thank you!
kow-mingte
commented
1 year ago 1) Reinstall openssl@1.1
brew install openssl@1.12) If you need to have openssl@1.1 first in your PATH, run:
echo 'export PATH="/usr/local/opt/openssl@1.1/bin:$PATH"' >> ~/.zshrc3) For compilers to find openssl@1.1 you may need to set:
export LDFLAGS="-L/usr/local/opt/openssl@1.1/lib"
export CPPFLAGS="-I/usr/local/opt/openssl@1.1/include"4) run:
ln -sf /usr/local/Cellar/openssl@1.1/1.1.1v/lib/libcrypto.dylib /usr/local/lib/5) 🎉
pappu687
commented
1 year ago For me brew unlink openssl worked. Using ST4, MacOS Ventura.
canidam
commented
1 year ago Are there really no other solutions than downgrading openssl default version for the whole system?
Is there a way to do it only for Sublime?
faelin
commented
1 year ago Maintainer @deathaxe has explained several times in this thread that you can solve the problem simply by downloading the latest edition (4.0+) of Package Control!
For reference:
Changing the PATH variable, installed version, linked version, or otherwise modifying the version of OpenSSL used by the system is a BAD IDEA. It was always a stop-gap measure to work around the constraints of conflicting dependencies. Please do not change which OpenSSL you use unless you are ABSOLUTELY CERTAIN that you know what you are doing!
canidam
commented
1 year ago Thank you @faelin ! I got it working after reading this https://github.com/wbond/package_control/issues/1612#issuecomment-1636034709
I just had to download the latest package, which is https://github.com/wbond/package_control/releases/tag/4.0.0-beta8
Then place it manually in the Installed Packages directory. Works :)
MatthiasPortzel
commented
1 year ago The ln ... syslink solution is, at best, temporary, as it breaks when Homebrew updates OpenSSL (which is why I am back here today).
The first instructions posted by @deathaxe aren't helpful, as people experiencing this bug can't open package control settings inside Sublime.
The best (and only real) solution is in this comment (back up profile first): https://github.com/wbond/package_control/issues/1612#issuecomment-1636034709. After following those instructions I get a popup about dependencies being migrated to Python libraries. Wait for that to finish, then restart.
I'm unclear if just following those steps will allow me to receive future package control update; it seems like no.
jiajianjie
commented
1 year ago @nbrooks09 — the screenshot you've attached appears to be an unrelated problem. You have
libcryptoinstalled correctly, however your installation is built for the x86 architecture used by Intel macs, while your Sublime console output says that you need the arm64 build (i.e. you have an M1 mac, and therefore need the M1-compatible libcrypto).You may be able to solve this by replacing your Homebrew installation (if you use one) to the ARM-based Homebrew, or by manually building arm64 libcrypto, or you might be able to find an answer in this openssl github issue.
If someone with an M1 mac find a solution, please let us know! `` my mac's cpu is arm , need reinstall brewhome in /opt
brew install openssl@1.1 && ln -sf $(set -- `brew --cellar openssl@1.1`/1.1.1? && echo "$1")/lib/libcrypto.dylib /usr/local/lib/\n
ll /opt/homebrew/Cellar/openssl@1.1/1.1.1w/lib/libcrypto.dylib
/opt/homebrew/Cellar/openssl@1.1/1.1.1w/lib/libcrypto.dylib -> libcrypto.1.1.dylib
ln -sf /opt/homebrew/Cellar/openssl@1.1/1.1.1w/lib/libcrypto.1.1.dylib /usr/local/lib/libcrypto.dylibPlease stop spamming this issue with all those repetitive stupid posts, which already exist dozens and hundreds of times!
viniciuslopesgit
commented
1 year ago @rgaudin there's a typo in your final line (missing the
bindylib)For others, the command that should fix this issue (at least on OS Monterey)
brew install openssl@1.1 && ln -sf $(set -- `brew --cellar openssl@1.1`/1.1.1? && echo "$1")/lib/libcrypto.dylib /usr/local/lib/ # or for an exact command: ln -sf /usr/local/Cellar/openssl@1.1/1.1.1o/lib/libcrypto.dylib /usr/local/lib/EDIT: note that the command suggested by @rgaudin includes the path
openssl@1.1/1.1.1nbut my installation had the pathopenssl@1.1/1.1.1oinstead, so I designed the top version of the above command to be more portable.
Works for me. Thank you!
pronebird
commented
11 months ago Time to drop Sublime into the bucket I guess...
~/Library/Application Support/Sublime Text 3/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto_ctypes.py", line 688, in <module>
Package Control.package_control.deps.oscrypto._ffi.FFIEngineError: Error initializing ctypes
h0jeZvgoxFepBQ2C
commented
11 months ago Thank you @faelin ! I got it working after reading this #1612 (comment)
I just had to download the latest package, which is https://github.com/wbond/package_control/releases/tag/4.0.0-beta8 Then place it manually in the
Installed Packagesdirectory. Works :)
Did you follow this? This works for most people, including me.
pronebird
commented
11 months ago Thank you @faelin ! I got it working after reading this #1612 (comment) I just had to download the latest package, which is https://github.com/wbond/package_control/releases/tag/4.0.0-beta8 Then place it manually in the
Installed Packagesdirectory. Works :)Did you follow this? This works for most people, including me.
Yeah. Sadly it didn't help. I have both openssl1.1 and openssl3 installed on my mac.
rr0ss0rr
commented
11 months ago What steps did you do to install manually? Also beta8 is the latest. For the latest, Check out releases
NazarK
commented
11 months ago Thank you @faelin ! I got it working after reading this #1612 (comment) I just had to download the latest package, which is https://github.com/wbond/package_control/releases/tag/4.0.0-beta8 Then place it manually in the
Installed Packagesdirectory. Works :)Did you follow this? This works for most people, including me.
Yeah. Sadly it didn't help. I have both openssl1.1 and openssl3 installed on my mac.
just run:
brew link openssl@1.1
and restart sublime, it fixed it for me
hyrious
commented
11 months ago I have installed Package Control v4.0.0-beta8 on my macOS 14 with Sublime Text 4 with OpenSSL 3. It works perfectly.
$ openssl version
OpenSSL 3.1.3 19 Sep 2023 (Library: OpenSSL 3.1.3 19 Sep 2023)
$ subl -v
Sublime Text Build 4152
$ sw_vers
ProductName: macOS
ProductVersion: 14.0
BuildVersion: 23A344If you are stuck at the place where Package Control 3.0 cannot run to update itself, you can do either of the 2 steps:
install_prereleases section in Package Control's settings to let it update itself: https://github.com/wbond/package_control/issues/1612#issuecomment-1625595350
Hoatzin
commented
11 months ago So I was getting the _pluginhost-3.3 has exited unexpectedly error. Manually going through plugins and disabling them didn't do anything, so I archived my Sublime Text folder in the Application Support, and it opened without errors. I told it to install the Package Control automatically, and it did, but upon restarting the error came back. So I manually downloaded the beta, but when I started that one it said _pluginhost-3.8 has exited unexpectedly...
I tried to force openssl 1.1 via brew but that didn't seem to alter anything or allow me to interact with Package Control menus, to sort or permute lines, to shrink or enlarge text and so on.
I am some updates behind on the MacOS, so I am gonna try that next.
roubachof
commented
11 months ago Don't forget to rename Package.Control.sublime-package to Package Control.sublime-package (whitespace between package and control) or you will end up with a message saying it cannot find the 'Package' package in console view.
legendbb
commented
10 months ago I just got my issue resolved by deleting "0_package_control_loader.sublime-package" and "Package Control.sublime-package" from the Install Packages folder. And reinstall from cmd + ctrl + p > install package control. macOS 13.5.2, sublime 4152
jama211
commented
10 months ago Why has this not been fixed within the program? Why do I have to download the latest version from here, name it correctly (by removing the dot between Package.Control) instead of it working inside sublime? It's been months...
deathaxe
commented
10 months ago There are 2 major reasons:
Until then, the only chance to ship the package for download is via Github releases, which do NOT support spaces in file names. They are replaced by periods. That's why you need to rename it.
It would be easy to file a final 4.0.0 version, soon, but would still leave those behind whose systems refuses to run PC 3.x
dak1m
commented
10 months ago Running
ln -sf /usr/local/Cellar/openssl@1.1/1.1.1o/lib/libcrypto.dylib /usr/local/lib/solved the issue for me. Thanks.if i install sublime text 4126 using official sublimetext, will i face this issues? or while installing brew for the first time on mac will cause this on silicon mac? i'm glad that u found a fix!
libcrypto
good to me
plocket
commented
10 months ago I wonder if it'd be useful to edit the original question to add the currently helpful answer(s?) to it so it (they?) don't get lost in the rest of the comments until various fixes come through. Just not sure how else to help people find the info. Took me a while to dig through here to find the two pieces that worked for me. Thank you for the help!
deathaxe
commented
10 months ago Fixed by 4.0
Note: Whether Package Control 4.0 can be installed directly via Sublime Text's main menu depends on whether the related package file will be signed and uploaded to packagecontrol.io by @wbond.
Until then you may still need to
Package Control.sublime-packageas the beta builds before.
plocket
commented
10 months ago Where should we check to find out if the related package file is signed and uploaded to packagecontrol.io, @deathaxe? That way, Future People will know where to look to find out if they can start installing via the main menu again.
deathaxe
commented
10 months ago The link at https://packagecontrol.io/installation would point to the PC 4.0 binary, I guess.
The official release, which is also downloaded by ST's install helper is located at https://packagecontrol.io/Package%20Control.sublime-package
Package Control 3.4.1 Metadata
Name: Package Control.sublime-package Größe: 471460 Bytes (460 KiB) SHA256: 817937144c34c84c88cd43b85318b2656f9c3fac02f8f72cbc18360b2c26d139
Package Control 4.0.0 would differ.
I don't want to post the details to avoid confusion with possible future releases.
rchl
commented
10 months ago Well, after installing 3.4.1 from the main menu, it will still update itself to 4.0 on next ST start (or sometime later), doesn't it? So effectively it's gonna be installed already anyway.
@deathaxe I'm not sure if that part is clear from your messaging here and in release notes.
deathaxe
commented
10 months ago But this won't help those - especially MacOS users, who have already run into Package Control not working issue due to openssl3 being linked.
Those won't benefit from auto-update from 3.4.1 to 4.0. They must take the hard way and install manually from this repo's releases page.
leocxy
commented
10 months ago Fixed by 4.0
Note: Whether Package Control 4.0 can be installed directly via Sublime Text's main menu depends on whether the related package file will be signed and uploaded to packagecontrol.io by @wbond.
Until then you may still need to
1. download latest release from https://github.com/wbond/package_control/releases 2. rename it to `Package Control.sublime-package` 3. place it to ST's _Installed Packages_ directoryas the beta builds before.
It work for me. I am using a Macbook with an M2 Chip.
I downloaded the sublime 4 from the official site (Build 4169) Then I tried to install the Package Control. It shows a successful message, but I can't see it.
If you close the ST totally and re-open it, you can see some error messages from the console. (View -> Show Console)
Now you can open the installed packages folder.
plocket
commented
10 months ago But this won't help those - especially MacOS users, who have already run into Package Control not working issue due to openssl3 being linked.
Just checking if I understand correctly:
deathaxe
commented
10 months ago This isn't going to be the situation forever.
Depends on the original author of this package who is the only one with access to packagecontrol.io
after you download it you can check its meta data ...
You can check the version by...
The version is listed in the details part under package name.
If it's using the wrong version, you go through the procedures outlined above.
Unfortunatelly, correct.
Luka2552
commented
9 months ago Fixed by 4.0 Note: Whether Package Control 4.0 can be installed directly via Sublime Text's main menu depends on whether the related package file will be signed and uploaded to packagecontrol.io by @wbond. Until then you may still need to
1. download latest release from https://github.com/wbond/package_control/releases 2. rename it to `Package Control.sublime-package` 3. place it to ST's _Installed Packages_ directoryas the beta builds before.
It work for me. I am using a Macbook with an M2 Chip.
I downloaded the sublime 4 from the official site (Build 4169) Then I tried to install the Package Control. It shows a successful message, but I can't see it.
If you close the ST totally and re-open it, you can see some error messages from the console. (View -> Show Console)
Now you can open the installed packages folder.
1. Settings -> Browser packages. This will bring you to the "Packages" folder, the "Installed Packages" folder sitting at the SAME level of the "Packages" folder. 2. Go to the "Installed Packages" folder, and delete the "Package Control.sublime-package" binary file 3. Download the new release from the above release link 4. Rename and move it back to the "Installed Packages" folder.
Thank you very much! This worked for me!
Sublime Text 4169
macOS Big Sur 11.6
KvMadan
commented
9 months ago Thank you! Above solution worked for Mac 14.2 ST 4169
raffeyang
commented
9 months ago Doesn't work on intel macOS.
leonson
commented
9 months ago I just used the solution for my Intel Macbook and unblocked. I am using Sublime Text 4 Stable Channel, Build 4169. My processor is 2.3 GHz Quad-Core Intel Core i75.
The installation page's Manual section step 3 does not have the most recent release, thus manually downloading there did not help. The solution here has the right link, I would suggest either update the link on installation page's manual session, or if there is a reason not to do so, add a link(on installation page) to this issue.
In my console log I found following error message which is equivalent to this issue's:
Traceback (most recent call last):
File "/Users/leonson/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto_ctypes.py", line 305, in <module>
File "./python3.3/ctypes/__init__.py", line 366, in __getattr__
File "./python3.3/ctypes/__init__.py", line 371, in __getitem__
AttributeError: dlsym(0x7ff919620a40, EVP_PKEY_size): symbol not foundThe original author - quite inactive recently - is the only one with write access to packagecontrol.io and thus the only one who could upload latest release there, which would also be required for ST's Package Control installer to directly install it.
The error message indicates Package Control 3.x to still be loaded! PC4.0 would run on python 3.8.
Maybe refer to "Solution" section provided in OP?
I tried instaling the Package Control via Command Palette and even manually but it was not working, after some debugging I found that the ctypes file for python3.3 are not being correctly loaded
This is the relevant part in the debug
Here is the rest of the output log
``` During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 308, in reload_plugin m = importlib.import_module(modulename) File "./python3.3/importlib/__init__.py", line 90, in import_module File "", line 1584, in _gcd_import
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/2_bootstrap.py", line 26, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/bootstrap.py", line 20, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/download_manager.py", line 24, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/downloaders/__init__.py", line 20, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/downloaders/oscrypto_downloader.py", line 44, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/tls.py", line 11, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_mac/tls.py", line 39, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_mac/util.py", line 208, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto.py", line 15, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto_ctypes.py", line 688, in
Package Control.package_control.deps.oscrypto._ffi.FFIEngineError: Error initializing ctypes
reloading python 3.3 plugin Package Control.Package Control
Traceback (most recent call last):
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto_ctypes.py", line 305, in
File "./python3.3/ctypes/__init__.py", line 366, in __getattr__
File "./python3.3/ctypes/__init__.py", line 371, in __getitem__
AttributeError: dlsym(0x7f876fc44440, EVP_PKEY_size): symbol not found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 308, in reload_plugin
m = importlib.import_module(modulename)
File "./python3.3/importlib/__init__.py", line 90, in import_module
File "", line 1584, in _gcd_import
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/Package Control.py", line 89, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/commands/__init__.py", line 3, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/commands/advanced_install_package_command.py", line 10, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/package_manager.py", line 34, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/downloaders/__init__.py", line 20, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/downloaders/oscrypto_downloader.py", line 44, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/tls.py", line 11, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_mac/tls.py", line 39, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_mac/util.py", line 208, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto.py", line 15, in
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python33/sublime_plugin.py", line 1692, in load_module
exec(compile(source, source_path, 'exec'), mod.__dict__)
File "/Users/nicoskaralis/Library/Application Support/Sublime Text/Installed Packages/Package Control.sublime-package/package_control/deps/oscrypto/_openssl/_libcrypto_ctypes.py", line 688, in
Package Control.package_control.deps.oscrypto._ffi.FFIEngineError: Error initializing ctypes
```
Any ideas on how to solve this?
Solution
Recommended solution for this issue is to manually install Package Control 4.0
Until then run the following code snippet from within ST's console
or manually
Package Control.sublime-package