Package Details: standardnotes-desktop 3.14.1-2

Git Clone URL: (read-only, click to copy)
Package Base: standardnotes-desktop
Description: A standard notes app with an un-standard focus on longevity, portability, and privacy.
Upstream URL:
Keywords: notes
Licenses: GPL3
Conflicts: sn-bin
Submitter: FillFeile
Maintainer: lsf
Last Packager: lsf
Votes: 48
Popularity: 0.051428
First Submitted: 2017-06-04 13:58 (UTC)
Last Updated: 2022-04-10 10:24 (UTC)

Latest Comments

jsutton commented on 2022-03-25 12:55 (UTC)

@lsf: it looks like python2 can be removed from the makedepends. I just built the current version without it successfully.

haven commented on 2022-02-21 18:26 (UTC)

standardnotes-desktop.js ... FAILED ==> ERROR: One or more files did not pass the validity check! error: failed to download sources for 'standardnotes-desktop-3.11.1-1': error: packages failed to build: standardnotes-desktop-3.11.1-1

Could not update.

Darkness commented on 2021-12-11 19:52 (UTC) (edited on 2021-12-11 19:52 (UTC) by Darkness)

@lsf: You're right, my bad! Been on Manjaro for so long I forgot it differs from vanilla Arch :) Manjaro just updated today, I installed electron15 and build works, sorry about that.

lsf commented on 2021-12-10 12:30 (UTC)

@Darkness: I assume that's a Manjaro-related issue again – Manjaro stable is behind with the electron version a bit, but for upstream Arch (which is at 16) we need to explicitely use electron15.

Darkness commented on 2021-12-08 18:50 (UTC)

Hi, install is broken due to the following:

cat: /usr/lib/electron15/version: No such file or directory

Electron 15 is the current version and as such most people aren't going to be using electron15-bin. It would seem this file doesn't exist in the repo package.

andrewSC commented on 2021-09-20 20:01 (UTC)

lsf: pinning the build to electron13 was the fix for me--thanks!

ubmarco commented on 2021-09-16 07:11 (UTC)

I'm getting this error on Manjaro where electron system package is still electron13:

electron13-bin: /usr/bin/electron13 exists in filesystem (owned by electron)

This error is also reported for electron13-bin.

lsf commented on 2021-09-13 17:44 (UTC) (edited on 2021-09-13 17:44 (UTC) by lsf)

I've just pushed an update to the package to ensure electron13 is used (I've had some issues building/running it with the most recent version) – maybe that also fixes your issue?

If not, that does sound like an issue I've had with other electron apps when using Wayland – maybe that's something you could dig into a bit (unless you're using kde5 with X11, in which case I have no idea /o\)

=> It works, for me at least, on sway, with


in ~/.config/electron13-flags.conf.

andrewSC commented on 2021-09-13 17:15 (UTC)

While this builds successfully, when I go to run the program the interior pane/view is completely blank. I'm on the latest kde5 packages in the official repo. Any suggestions?

lsf commented on 2021-07-29 12:36 (UTC)

Good news: aarch64 builds are back again :)

lsf commented on 2021-05-31 19:04 (UTC)

I'm currently unable to get this to build on aarch64 anymore.

I'll keep trying, though – and if anyone has any ideas how to get this resolved, I'm all ears!

lsf commented on 2021-02-28 15:24 (UTC)

Oh dear, what have I gotten myself into ;)

But I totally understand you @FillFeile – building and packaging NodeJS/Electron based packages is (imho) really a terrible experience, and it's even more complicated with this package than with many others (I'm currently unable to build the -git version of it anymore, for example… hope this will improve before the next release is made).

Anyway, I'll try to keep maintaining it a bit – but I can't make any promises and might not spot any issues, as I'm not using it at the moment myself.

FillFeile commented on 2021-02-28 15:10 (UTC) (edited on 2021-02-28 15:11 (UTC) by FillFeile)

Hi all, Hi @randomguy343,

I just decided to disown this package as I'm currently not able to properly maintain it anymore. At the moment I do not find the time to cope with the frequent build system changes on upstream which have been challenging for me to keep up with as I'm not very experienced with the NodeJS and Electron build/package frameworks.

Thank you all for the feedback over the last years which have been a great opportunity for me to learn how to maintain a package. I hope someone (maybe @lsf) will pick this one up and keep it alive.

Cheers, FillFeile

randomguy343 commented on 2021-02-28 11:58 (UTC)

Thanks, works fine so far but needs yarn as an dependency. I rarely use Standard Notes myself, but I'll report any issues nonetheless.

lsf commented on 2021-02-27 13:16 (UTC)


I have a seemingly working PKGBUILD over at

You could give it a try, if you wish – it's only barely tested, though; I'm not using standardnotes myself at the moment.

randomguy343 commented on 2021-02-27 11:59 (UTC)

Is this package still actively maintained and will be updated soon or what's the current status?

PrzemekS commented on 2020-12-01 08:31 (UTC) (edited on 2020-12-01 08:32 (UTC) by PrzemekS)

Hello, recently I noticed top bar is not working. Cannot minimize, close etc. In terminal I see:

extServer: Server started at
09:25:29.933 › Checking for update
09:25:29.961 › Error: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
} Cannot check for updates: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: Exception caught while checking for autoupdates: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
09:25:30.530 › Checking for update
09:25:30.531 › Error: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'
} Cannot check for updates: Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'
updateManager: Exception caught while checking for autoupdates: [Error: ENOENT: no such file or directory, open '/opt/standardnotes-desktop/app/dev-app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/standardnotes-desktop/app/dev-app-update.yml'

Regards, Przemek

jackyzy823 commented on 2020-11-21 15:30 (UTC)

Here's my working version which tested under electron 10. just for your reference.

diff --git a/PKGBUILD b/PKGBUILD
index a20e6fc..82b1f49 100644
@@ -1,15 +1,15 @@
 # Maintainer: Daniel Haß <>
 pkgdesc="A standard notes app with an un-standard focus on longevity, portability, and privacy."
-makedepends=('npm' 'node-gyp' 'git' 'jq')
+makedepends=('npm' 'node-gyp' 'git' 'jq' 'python2')
@@ -30,8 +30,11 @@ prepare() {

 build() {
   cd $srcdir/$_pkgname/
+  # see
+  cp .env.js.sample .env.js
   # use temporary npm cache -
   npm install --cache "${srcdir}/npm-cache"
+  npm install --prefix ./web --cache "${srcdir}/npm-cache"
   npm run bundle
   ./node_modules/.bin/electron-builder --linux --x64 --dir $dist

Note: 1. python2 is required to an old-version node-gyp to build node-sass which can't found a ABI-matched prebuilt binary from it's github releases because of nodejs ABI bumping to 88 .

  1. .env.js is required to pass the webpack build.

FillFeile commented on 2020-10-30 14:09 (UTC)

I recognized the comments and will dry to address the issues and feedback as soon as possible.

lsf commented on 2020-10-30 09:37 (UTC)

If the patching/workaround is simple enough (as in this case with a one-line-fix), I'd find that more attractive – but that's probably because for my specific case (a separate repo), maintaining different electron versions as well is just way more of a hassle.

So yeah, both solutions should be fine, I guess ^^

FiveYellowMice commented on 2020-10-30 06:27 (UTC) (edited on 2020-10-30 06:28 (UTC) by FiveYellowMice)

Launching with electron9 /usr/bin/standardnotes-desktop works.

I guess issue #620 (on extensions not loading) is just due to upstream not supporting Electron 10 yet? If that's the case, just changing the shebang in standardnotes-desktop.js to electron9 and make electron9 the dependency is probably an easier solution to patching.

lsf commented on 2020-10-29 18:11 (UTC) (edited on 2020-10-29 18:16 (UTC) by lsf)

I'm building standardnotes slightly differently over at and from (very cursory) testing at least, the issue #620 (not the dev-app-update.yml-issue, the other part of it) does not seem to occur with my builds.


I just realized: it's probably not that, but the workaround for electron 10 I've added, as even if it's built with 9, it's still run with 10.

sed 's#shell\.openItem#shell.openPath#' -i app/javascripts/main/menus.ts

in prepare()

My previous idea was the following, for completeness' sake.

Mainly, I'm running a few more parts of the build scripts manually in the PKGBUILD as well:

  npm run bundle
  npm install
  npm --prefix ./app install ./app
  npx rimraf app/dist/
  npx webpack --config

This might do the trick (or I might be totally wrong about this – I'm also explicitly building with electron 10, for example).

balek commented on 2020-10-28 22:57 (UTC)

Latest version still not working

ZorinArch commented on 2020-10-26 17:54 (UTC)

Hi FillFeile,

It working just fine."Office" Category is enough any way.


Chosto commented on 2020-10-26 16:57 (UTC)

Getting the same issue :

FillFeile commented on 2020-10-26 15:52 (UTC)

Hi ZorinArch,

thanks for the feedback, I added the Category "Office" to the Categories list in the .desktop file. I was not able to find a category "Application" in the Freedesktop Standard ( I think this is already set via the "Type" field.

If you think this is an error please let me know.



ZorinArch commented on 2020-10-26 09:40 (UTC) (edited on 2020-10-26 09:43 (UTC) by ZorinArch)

Please add categories to standardnotes-desktop.desktop


because it locate the app in Lost & Found section.


balek commented on 2020-10-21 10:27 (UTC)

Same as tate

tate commented on 2020-10-19 22:26 (UTC)

Getting this exact error. Looks like the app is up to v. 3.4.10 as well.

easthvan commented on 2020-10-01 23:27 (UTC)

Thank you for this! It is my fav note app on Android too and I did not want to use the Snap version (commercial Ubuntu stuff...) and only your Aur pack was available on my Manjaro OS.

FillFeile commented on 2020-09-10 15:22 (UTC)

v3.4.3 was just released on the upstream and removes the need for the workaround fix in the current PKGBUILD. I updated the package accordingly.

Please let me know if problems pop up on your side.

Cheers, FillFeile

FillFeile commented on 2020-09-07 17:02 (UTC)

News regarding the upstream issue: The devs promised to release a hotfix version v3.4.3 later this week ( After that I will cleanup the PKGBUILD and remove the current workaround patch.

FillFeile commented on 2020-09-06 16:12 (UTC)

Hi all, sorry for the inconvienence caused. Sadly the error was not cause by the new PKBUILD. Version 3.4.2 is bricked on upstream as you can see here:

My local tests ran trough cause somehow my local npm cache must have provided a version of a subpart that is not available anymore. I switched the PKGBUILD to use a temporary npm cache for the future so this will not happen again.

The current packaged version uses a slightly older subpart version for standard-notes-web (the one from version 3.4.1). This is not completly clean but the app seams to work anyways. I will bump the upstream issue to get this fixed as soon as possible. If you want to help I would kindly ask you to upvote the linked github issue.

sparklyballs commented on 2020-09-06 11:53 (UTC)

Also seeing the same error as Lanthanus Attempting to upgrade from 3.4.1

Tried with yay and cloning the repository directly and running makepkg -si with same results.

Lanthanus commented on 2020-09-06 10:00 (UTC)

Unfortunately it stopped with an error. Seems to be a problem with the postinstall script.

> electron-builder install-app-deps
  • electron-builder  version=22.6.0
  • loaded configuration  file=package.json ("build" field)
  • installing production dependencies  platform=linux arch=x64 appDir=/var/tmp/pamac-build-user/standardnotes-desktop/src/desktop/app
  ⨯ /usr/bin/node exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Error output:
Error output:
npm WARN standard-notes@3.4.2 No repository field.
npm WARN standard-notes@3.4.2 No license field.
npm ERR! code 128
npm ERR! Command failed: git checkout 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! fatal: Referenz ist kein "Tree"-Objekt: 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-09-06T09_53_26_617Z-debug.log
Error: /usr/bin/node exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Error output:
Error output:
npm WARN standard-notes@3.4.2 No repository field.
npm WARN standard-notes@3.4.2 No license field.
npm ERR! code 128
npm ERR! Command failed: git checkout 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! fatal: Referenz ist kein "Tree"-Objekt: 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! 
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-09-06T09_53_26_617Z-debug.log
at ChildProcess.<anonymous> (/var/tmp/pamac-build-user/standardnotes-desktop/src/desktop/node_modules/builder-util/src/util.ts:243:14)
at Object.onceWrapper (events.js:421:26)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1051:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
npm ERR! errno 1
npm ERR! standard-notes@3.4.2 postinstall: `electron-builder install-app-deps`
npm ERR! Exit status 1
npm ERR! 

FillFeile commented on 2020-09-06 08:46 (UTC)

As promised the new verison is packaged and uploaded. I hope the update runs smooth for everyone. The PKGBUILD now uses electron-builder, as the upstream does, to build the app.

Sorry again for the delay!

Cheers, FillFeile

ajgraves commented on 2020-09-05 14:28 (UTC)

Thanks @FillFeile for the update!

FillFeile commented on 2020-09-05 14:16 (UTC)

Hi all, sorry for the delay with the recent update. I will continue to maintain this PKGBUILD but the latest update was delayed for two main reasons. I faced some time constrains on my side + Standard Notes (again) changed their build toolchain which broke the current PKGBUILD. The upstream package.json doesn't contain a build script for the plain linux "dir" target anymore. I'm currently working on a patched version that hopefully will arrive tomorrow. Thank you for your patience, I will keep you updated!

ajgraves commented on 2020-08-29 15:54 (UTC)

Hello, this has been flagged out of date for some time. Is nobody maintaining this PKGBUILD any longer?

FillFeile commented on 2020-06-07 15:11 (UTC)

@vyachkonovalov - thanks a lot for the heads up! You're totally right. Fixed this with 3.4.1-2.

crabvk commented on 2020-06-07 11:12 (UTC)

Hi. I'm getting

==> ERROR: Cannot find the git package needed to handle git sources.

You should add 'git' to makedepends=.
Thank you for the package.

mausworks commented on 2020-01-19 15:57 (UTC)

@Zwenn76, that's interesting! I had to cleanbuild the package (I'm using yay), otherwise it wouldn't work after the update. That error-message is new to me, however, but it doesn't seem like it's an external dependency causing the problem.

Does it build if you clone the GitHub repo, and is node and NPM up-to-date?

Zwenn76 commented on 2020-01-19 15:26 (UTC)

It still doesn't work on my system since the last two updates:

A JavaScript error occurred in the main process Uncaught Exception: /opt/standardnotes-desktop/app/index.js:13 import menuManager from './javascripts/main/menuManager.js' ^^^^^^

SyntaxError: Cannot use import statement outside a module at Module._compile (internal/modules/cjs/loader.js:815:22) at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10) at Module.load (internal/modules/cjs/loader.js:735:32) at Module._load (internal/modules/cjs/loader.js:648:12) at Module._load (electron/js2c/asar.js:717:26) at Function.Module._load (electron/js2c/asar.js:717:26) at Object.<anonymous> (/usr/bin/standardnotes-desktop:30:19) at Module._compile (internal/modules/cjs/loader.js:880:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10) at Module.load (internal/modules/cjs/loader.js:735:32)

Any suggestions

mausworks commented on 2020-01-16 22:13 (UTC)

Awesome @FillFeile! Thanks for the quick update, and thanks again for maintaining!

FillFeile commented on 2020-01-16 19:17 (UTC)

Hey guys, I just uploaded the package-release 2 of version 3.0.25 which should work properly again. Thanks to @Deciare and @mausworks who spotted the problem! I switch from yarn to npm which seems to fix the problem. Back when I started maintaining this package there was a particular reason to use yarn, which I acctually to not remember anymore.. as of now the package uses the standard node package manager again. I also updated the application wrapper JS and removed the deprecated setName() function.

Happy updating!

mausworks commented on 2020-01-16 10:09 (UTC)

@Deciare I did find it a bit peculiar that yarn was used over npm, but I never investigated it, as they should essentially do the same thing. However, yarn does have some fancy "pruning" and "cleanup" functionality built in. It is also "non-standard" to use for NPM.

After cloning the project (and building it) from the GitHub URL i also got it working, but I was using npm install followed by npm run build.

So the fix seems to be to simply use npm over yarn. It will also remove the yarn build dependency which is probably a good idea in the first place.

Deciare commented on 2020-01-16 01:22 (UTC) (edited on 2020-01-16 01:22 (UTC) by Deciare)

This may not be a proper solution, and I'm not familiar with building electron apps. However, I've been able to make the package build successfully by using npm instead of yarn to do the dependency installation and building.

In the PKGBUILD, just replace:

yarn install
yarn build


npm install
npm run build

Even if it's not a proper solution, it may be a helpful workaround for people who just need a working app for now.

mausworks commented on 2020-01-15 10:15 (UTC)

Hey FillFeile, thanks for maintaining this package!

I'm getting the same error as @bryanOmalley, are you sure the error is upstream?

I have electron/node/js experience, so I'll see if I can figure out what's wrong when I get home.

FillFeile commented on 2020-01-14 09:22 (UTC)

Dear @bryanOmalley, sorry about that! I was able to reproduce the issue. Something seemed to glitched trough my pretesting. Sorry about that. As it looks like an error with the app itself I will try to contact the author and report a bug asap. Feel free to do so yourself if you like. Cheers, FillFeile

bryanOmalley commented on 2020-01-12 19:21 (UTC) (edited on 2020-01-12 19:22 (UTC) by bryanOmalley)

Last update seems to have introduced some kind of bug. Standardnotes doesn't open on my end anymore

(electron) 'setName function' is deprecated and will be removed. Please use 'name property' instead.
App threw an error during load
Error: Cannot find module '/opt/standardnotes-desktop/app/dist/node_modules/request/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:268:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:460:18)
    at Module._resolveFilename (internal/modules/cjs/loader.js:704:27)
    at Function../lib/common/reset-search-paths.ts.Module._resolveFilename (electron/js2c/browser_init.js:7615:16)
    at Module._load (internal/modules/cjs/loader.js:622:27)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:775:19)
    at require (internal/modules/cjs/helpers.js:68:18)
    at Object.<anonymous> (/opt/standardnotes-desktop/app/dist/javascripts/main/fileUtils.js:23:15)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module '/opt/standardnotes-desktop/app/dist/node_modules/request/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:268:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:460:18)
    at Module._resolveFilename (internal/modules/cjs/loader.js:704:27)
    at Function../lib/common/reset-search-paths.ts.Module._resolveFilename (electron/js2c/browser_init.js:7615:16)
    at Module._load (internal/modules/cjs/loader.js:622:27)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:775:19)
    at require (internal/modules/cjs/helpers.js:68:18)
    at Object.<anonymous> (/opt/standardnotes-desktop/app/dist/javascripts/main/fileUtils.js:23:15)

FillFeile commented on 2019-10-09 07:06 (UTC) (edited on 2019-10-09 07:06 (UTC) by FillFeile)

Dear Users, I'm unable to update the package to the latest version at the moment, cause it seems that the latest release tag (v3.0.17) is somehow messed up. Please find details here: Cheers, FillFeile

dymdipi commented on 2019-07-31 20:53 (UTC)

@FillFeile: I raised this to the devs and then tested the appimage:

The appimage works normally and so this strangely seems to be something with the AUR build and maybe some interaction with pacman or Manjaro?

FillFeile commented on 2019-07-27 06:48 (UTC)

Sorry for you guys to hear that you are suffering from that issues on your Manjaro setups. But I have to say that it rather sounds like an application issue than a packaging one. So please be free to open an issue at to get the developers of standardnotes to take a look at it.

dymdipi commented on 2019-07-25 22:01 (UTC)

@ivanjara: I'm getting the same behavior on Manjaro XFCE. The bottom menu with "Account", "Help", "Extensions" etc is also hidden. I have to scroll down for this to be visible. It's hidden even if I expand or maximize the window.

I'm running stable branch, fully updated, 'Linux 5.1.18-1-MANJARO' kernel, XFCE 4.13. Building the application from AUR via command:

pamac build standardnotes-desktop

Does anyone have any ideas?

ivanjara commented on 2019-07-24 14:37 (UTC) (edited on 2019-07-24 14:40 (UTC) by ivanjara)

I'm running Manjaro KDE, and the Maximize/Minimize/Close buttons are not responding. Manjaro Kernel: 4.19.60-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 Desktop: KDE Plasma 5.16.3 Distro: Manjaro Linux.

Version: standardnotes-desktop-3.0.15-1

Using the "Error console" I found: ReferenceError: require is not defined at index.html:12 index.html:71 Uncaught TypeError: window.nodeRequire is not a function at index.html:71

/usr/lib/electron/resources/electron.asar/renderer/security-warnings.js:170 Electron Security Warning (Insecure Content-Security-Policy) This renderer process has either no Content Security Policy set or a policy with "unsafe-eval" enabled. This exposes users of this app to unnecessary security risks.

Can anyone point me in the right direction to have this fixed?

Thanks in advance for any response!

Delan commented on 2019-06-09 11:25 (UTC)

@davidhaller: thanks for the answer I was aware of the unstable/testing/stable branch distinction but not the AUR/Arch vs. Manjaro limitation. Uninstall/reinstall did the trick and it now properly launch. Thank you for the quick follow-up!

davidhaller commented on 2019-06-09 11:20 (UTC) (edited on 2019-06-09 11:21 (UTC) by davidhaller)

@Delan: The package was updated to be compatible with the new electron version in Arch Linux. Since Manjaro lacks a few weeks behind Arch Linux, it still has the old electron version. I'm not familiar with Manjaro, but iirc they have an unstable/testing branch, maybe you could try a new electron version from here, or you could just build this package without the new patch and wait until Manjaro gets the new electron version.

(Please remember: Officially, the AUR only supports Arch Linux)

Delan commented on 2019-06-09 11:02 (UTC)

Hi, following the last update on Manjaro, Standard Notes doesn't launch anymore. I copied the logs here:, I'll try the uninstall/reinstall and edit the comment with the outcomes.

Remark: I don't know if it's relevant, but during the last update, the GUI of Pamac disappeared (however the package manager was still running since I couldn't relaunch the update from another instance of Pamac). To properly update the two AUR packages (Tor and Standard Notes) I had to go through the CLI (no modification of build files). Log are provided here:

FillFeile commented on 2019-06-09 10:23 (UTC)

Dear @rjocoleman, thanks for submitting the patch. Nice one!

I added it to package release 2 of version 3.0.12. So from now on there shouldn't be a need for users to patch their AUR package locally.

Sorry for any inconvenience caused trough this messed-up package release. I normally test my builds locally before releasing a new package version. This one somehow glitched into the repo without proper testing. I blame this one on me even though its an upstream issue. The broken version shouldn't have made it into the AUR repo..

davidhaller commented on 2019-06-09 07:39 (UTC)

@rjocoleman: Thanks for the patch, great work!

rjocoleman commented on 2019-06-08 21:34 (UTC)

Hello @FillFelle, thanks for this package! As of latest release it's crashing due to the build happening with a newer version of Electron than upstream currently supports.

There is a defensive PR upstream ( to deal with this but in the mean time here's a patch for this package that integrates it directly.

(git apply standardnotes-desktop-aur-deprecation.patch)

kaymmm commented on 2019-02-02 16:49 (UTC)

FYI I was getting the error

'prebuild-install' command not found

so I installed it using

npm i -g prebuild-install

not sure why this wasn't captured in the yarn installation process, but it works now.

scottwernervt commented on 2018-12-04 14:21 (UTC)

Alternate package

JoshuaRLi commented on 2018-12-04 05:56 (UTC)

Going to be disowning this; I don't use sn-bin anymore ( is easier for me) and no longer have the obligation to maintain this low popularity package. Please feel free to adopt it.

FillFeile commented on 2018-10-14 11:48 (UTC)

@knokelmaat thanks for the quick feedback. I updated the PKGBUILD accordingly.

knokelmaat commented on 2018-10-14 11:10 (UTC)

@FollFeile I can confirm that installing node-gyp did the trick. I had exactly the same error as tinhtruong and this solved it, so you can update the package! Thanks for the quick fix!

FillFeile commented on 2018-10-13 14:30 (UTC)

@tinhtruong - thank you for using this package! It looks like your setup is lacking the node-gyp package. Actually there is some discussion on the yarn side if this dependency should be handle by the application itself or by yarn.

Nevertheless, could you try the following and see if it fixes your error?

sudo pacman -S node-gyp

Please let me know if this fixes the issue, if so I will update the package accordingly.

tinhtruong commented on 2018-10-13 12:55 (UTC)

I have problems while trying to upgrade to 2.3.7. Here is the error:

Error: /usr/bin/node exited with code 1 Error output: warning package.json: No license field warning ../package.json: No license field warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. warning standard-notes@2.3.7: No license field warning electron-editor-context-menu > lodash.isarray@4.0.0: This package is deprecated. Use Array.isArray. error /home/auser/.cache/yay/standardnotes-desktop/src/desktop/app/node_modules/spellchecker: Command failed. Exit code: 127 Command: prebuild-install --verbose || node-gyp rebuild Arguments: Directory: /home/auser/.cache/yay/standardnotes-desktop/src/desktop/app/node_modules/spellchecker Output: /bin/sh: prebuild-install: command not found /bin/sh: node-gyp: command not found

at ChildProcess.childProcess.once.code (/home/auser/.cache/yay/standardnotes-desktop/src/desktop/node_modules/builder-util/src/util.ts:251:14)
at Object.onceWrapper (events.js:273:13)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:962:16)
at (internal/child_process.js:381:11)
at Socket.emit (events.js:182:13)
at Pipe._handle.close (net.js:606:12)

From previous event: at installOrRebuild (/home/auser/.cache/yay/standardnotes-desktop/src/desktop/node_modules/electron-builder-lib/out/util/yarn.js:68:17) at /home/auser/.cache/yay/standardnotes-desktop/src/desktop/node_modules/electron-builder/src/cli/install-app-deps.ts:57:5 at (<anonymous>) at runCallback (timers.js:694:18) at tryOnImmediate (timers.js:665:5) at processImmediate (timers.js:647:5) From previous event: at installAppDeps (/home/auser/.cache/yay/standardnotes-desktop/src/desktop/node_modules/electron-builder/out/cli/install-app-deps.js:174:17) at then (/home/auser/.cache/yay/standardnotes-desktop/src/desktop/node_modules/electron-builder/src/cli/cli.ts:43:10)</anonymous>

Any help would be appreciate!

FillFeile commented on 2018-04-28 16:15 (UTC)

The upstream issue with npm should be fixed now (see here: The current version (including the fix) is available in through the arch repos.

scorpionzezz commented on 2018-04-11 04:39 (UTC)

@h313, read the comment from the author... just below your comment :D

h313 commented on 2018-04-11 01:21 (UTC)

I'm getting this error when doing the npm install:

npm ERR! code MODULE_NOT_FOUND npm ERR! Cannot find module 'node-gyp/bin/node-gyp'

FillFeile commented on 2018-04-09 15:37 (UTC) (edited on 2018-04-09 15:37 (UTC) by FillFeile)

Currently it is possible that you may face an error during the package install. This is caused by a movement of the library node-gyp. Details:

You may see this error: Error: Cannot find module '/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js'

One workaround is to jump into /usr/lib/node_modules/npm an run an npm install node-gyp there.

FillFeile commented on 2018-03-16 17:05 (UTC)

@alien2003 - Extensions should work now. The problem was that the extention-manager submodule is not included in the release source tarball that I used to download the sourcecode. Now I switch to directly accessing the git-repo and fetching the required submodules afterwards.

Please let me know if the extensions are working for you after this change.

FillFeile commented on 2018-03-16 16:05 (UTC)

@alien2003 - thank you for your feedback. I'm not using the extended plan which is as far as I know mandatory for extentions.

Can you provide any error message or go a little more into details what is not working?

alien2003 commented on 2018-03-14 08:53 (UTC) (edited on 2018-03-14 08:53 (UTC) by alien2003)

Extensions do not work for me

FillFeile commented on 2018-02-26 20:42 (UTC)

Hey folks, I would like to apologize for the long period it took me to provide you with this overdue update! Updates will find there way into the package more frequently again. Cheers, FillFeile

Plexcon commented on 2018-02-25 16:06 (UTC)

Update please v.2.1.0

veras commented on 2018-01-18 00:06 (UTC)

It works - however it would be nice for the PKGBUILD to include a .desktop file in /usr/share/applications.

JoshuaRLi commented on 2018-01-16 13:57 (UTC)

@securitybreach I just updated the executable name to standard-notes. Sorry about that! If you want a shorter name either alias or symlink.

securitybreach commented on 2018-01-15 22:09 (UTC) (edited on 2018-01-15 22:10 (UTC) by securitybreach)

Executable conflicts with mono:

error: failed to commit transaction (conflicting files)

sn-bin: /usr/bin/sn exists in filesystem

pacman -Qo sn

/usr/bin/sn is owned by mono

JoshuaRLi commented on 2018-01-11 16:10 (UTC) (edited on 2018-02-02 18:36 (UTC) by JoshuaRLi)

As this is out-of-date, I will be actively maintaining sn-bin, which is a direct binary (PKGBUILD) download + installation from the project's Releases page.

arthurtaborda commented on 2018-01-05 14:38 (UTC)

Please, add this line to the .desktop file

StartupWMClass=Standard Notes

it will prevent the taskbar to have duplicated icons for this app.

commented on 2017-08-20 17:36 (UTC)

Thanks for your answer @FillFeile, libevent is indeed a dependency of electron. I don't understand why it's not installed by Yaourt when installing standardnotes-desktop. I'll look into it. Cheers

FillFeile commented on 2017-08-14 09:46 (UTC)

Hey @M-Gregoire, Thanks for you support! I think the libevent dependency is already covered through electron (standardnotes -> electron -> libevent). Could you please double check this for me? Cheers FillFeile

commented on 2017-08-13 13:23 (UTC)

This packages depends on libevent ( If it's not installed, the app cannot be launched. Thanks for putting standard notes in the AUR.