-
Notifications
You must be signed in to change notification settings - Fork 333
error loading sodium bindings #861
Comments
Thanks @rdbartlett! This is super useful for debugging the issue. If we get a potential fix together would you be available to test it before the actual realease? @mmckegg I saw that Sharp had a similar issue with Electron packages. If you're interested, here's their workaround: lovell/sharp#678 (comment). Maybe we could do the same with libsodium, is patchwork-builder still being used for Patchwork releases? |
I'm also getting "error loading sodium bindings" when I open Patchwork from the terminal on OSX and it gets stuck on "Scuttling..."/"Loading...". I just upgraded from maybe a 4-5 old version to 3.11.2. |
If you installed from source, you should be able to run |
@rdbartlett @marlun are you both running the AppImage on Linux? I haven’t tested the appimage build for some time. Maybe it’s broken? I don’t have a GUI Linux machine at the moment. |
@mmckegg I'm running it on my Mac (Patchwork-3.11.2-mac.dmg) and so does @rdbartlett it seems (from his message). |
Still getting this in 3.11.3. Starting from the terminal I see:
OSX 10.11.6 |
I think the error message might have been caused by a broken build. That message is most likely not the reason that patchwork is not running. There is an issue in the current releases 3.11.x where they get stuck on startup if you try and run patchbay on the same machine (one at a time). The cure is just to wait a while with the scuttling spinners (around 2 mins), and then restart (the indexes are completing in the background, but for some reason patchwork does not load when they complete). Anyway, next release of patchwork should fix this, so I'm going to close this issue. Feel free to open if the problem re-appears. |
Just installed the latest Patchwork on my mac. Had to reload a few times before it worked (was getting stuck in scuttling state). Now it is working, but I see this in my console, so I'm sharing in case it is useful:
The text was updated successfully, but these errors were encountered: