Unable to install Joplin on Manjaro

blyatmobilebr · 2020-09-02T17:16:50.595Z

Hi there,

Since I’m unable to install Joplin for whatever reason, I won’t be able to provide either the log and the latest version of the app. I tried to install Joplin using yarn, npm, pacman, yay and finally:
wget -O - https://raw.githubusercontent.com/laurent22/joplin/master/Joplin_install_and_update.sh | bash.

I’m using a custom shell called Fish. Here’s the OS specs:

ma-specs774×415 139 KB

How should I proceed in order to install Joplin and get rid of Evernote cough cough proprietary software forever?

laurent · 2020-09-02T19:10:22.054Z

What’s the error?

blyatmobilebr · 2020-09-02T23:17:00.947Z

Basically a npm ERR when I use npm as my package manager.

CalebJohn · 2020-09-02T23:22:46.111Z

@blyatmobilebr you need to provide the actual error, otherwise it’s impossible to help you.
The npm error is probably an unmet dependency and the error will tell you what’s missing.

It would also be helpful to give the error for when you try the wget command, because that one would be fixable on our end.

blyatmobilebr · 2020-09-02T23:34:49.099Z

NPM error:

➤ sudo npm i -g joplin                                                        20:26:29
[sudo] senha para blyatmobilebr: 
npm WARN deprecated jssha@2.4.2: jsSHA versions < 3.0.0 will no longer receive feature updates
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
/usr/bin/joplin -> /usr/lib/node_modules/joplin/main.js

> keytar@5.6.0 install /usr/lib/node_modules/joplin/node_modules/keytar
> prebuild-install || node-gyp rebuild

prebuild-install WARN install EACCES: permission denied, access '/root/.npm'
gyp WARN EACCES current user ("nobody") does not have permission to access the dev dir "/root/.cache/node-gyp/14.8.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/joplin/node_modules/keytar/.node-gyp"
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/joplin/node_modules/keytar/.node-gyp'
gyp ERR! System Linux 5.7.17-2-MANJARO
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/joplin/node_modules/keytar
gyp ERR! node -v v14.8.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! keytar@5.6.0 install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the keytar@5.6.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-09-02T23_28_14_583Z-debug.log

blyatmobilebr in ~ via ⬢ v14.8.0 took 1m12s

And actually when I use wget it tells me I already have the latest version installed, but when I type joplin in my terminal it doesn’t work. My bad on that one.

laurent · 2020-09-03T00:04:11.087Z

Npm doesn’t work well with sudo. Instead you should try to install as suggested on the homepage.

blyatmobilebr · 2020-09-03T00:21:20.011Z

I only tried using sudo because the command from the homepage doesn’t work. Otherwise:

➤ npm i -g joplin                                                             21:18:55
npm WARN deprecated jssha@2.4.2: jsSHA versions < 3.0.0 will no longer receive feature updates
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN checkPermissions Missing write access to /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!  [Error: EACCES: permission denied, access '/usr/lib/node_modules'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/lib/node_modules'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/blyatmobilebr/.npm/_logs/2020-09-03T00_19_29_853Z-debug.log

blyatmobilebr in ~ via ⬢ v14.8.0 took 26s

That’s shown to me with npm i -g joplin

CalebJohn · 2020-09-03T02:03:55.865Z

When installing Joplin with wget it doesn’t install the command line version. You can either use your desktop launcher (It will be the the xfce4 applications menu) to open Joplin or issue the command

~/.joplin/Joplin.AppImage

which will launch the desktop version.

blyatmobilebr · 2020-09-03T02:19:04.815Z

I’ll open an issue related to the window though, I’m not being able to close it neither when pressing the X icon nor when right-clicking on the icon and trying to close it.

RedDocMD · 2020-09-04T04:08:06.307Z

That is because you have used npm previously as sudo. Once you do that, you will keep on running into problems from then onwards

blyatmobilebr · 2020-09-04T04:36:29.417Z

Hi there,

Well, I was able to terminate the process using the terminal. Then I uninstalled whatever package I installed with npm and eveything's fine here