Package Details: standardnotes-desktop 3.0.21-1

Git Clone URL: (read-only)
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: FillFeile
Last Packager: FillFeile
Votes: 35
Popularity: 3.46
First Submitted: 2017-06-04 13:58
Last Updated: 2019-11-16 10:31

Latest Comments

1 2 3 Next › Last »

FillFeile commented on 2019-10-09 07:06

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

@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

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

@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

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

@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

@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

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

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

@rjocoleman: Thanks for the patch, great work!