-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Terminal application cannot find spellfix.so #3783
Comments
I am seeing this as well on Ubuntu 20.04 x86_64 and npm 6.14.4 |
I updated my post with node/npm versions as well. |
On my Raspberry Pi, I get the same error, and the app doesn't start even with a directory structure containing spellfix.so in the current dir. That instance is installed in my home folder using nvm though, so it's installed using:
and ends up in:
The environment for that computer is: Joplin version: 1.1.7 File .config/joplin/log.txt: |
Same here. |
same here |
Same on macos |
facing the same issue on arch kernel 5.8.10 |
Fixed with : then reinstalled joplin, and worked. |
Actually, it was commit 6aca233 which fixed it. I already had the latest version of libsqlite3-dev installed. |
I can confirm that the issue is resolved in version 1.2.1 for both my Ubuntu laptop and my Manjaro raspberry pi. |
After updating the joplin terminal application to version 1.1.7, when I try to run it, I get the following error:
The file actually resides in
~/.joplin-bin/lib/node_modules/joplin/lib/sql-extensions/spellfix.so
but that's not the path that gets reported. If I create the folder structure in the current directory with a symlink to the so-file, joplin starts just fine.Environment
Joplin version: 1.1.7
Platform: terminal
OS specifics: Ubuntu 15.04.5 LTS x86_64
Node version: 14.11.0
Npm version: 6.14.8
Steps to reproduce
NPM_CONFIG_PREFIX=~/.joplin-bin npm install -g joplin
Describe what you expected to happen
Joplin should launch normally.
Logfile
File .config/joplin/log.txt:
2020-09-21 14:29:35: "Profile directory: /home/johan/.config/joplin"
The text was updated successfully, but these errors were encountered: