Package Details: joplin-desktop 3.0.14-1

Git Clone URL: https://aur.archlinux.org/joplin.git (read-only, click to copy)
Package Base: joplin
Description: A note taking and to-do application with synchronization capabilities - Desktop
Upstream URL: https://joplinapp.org/
Keywords: markdown note notetaking productivity
Licenses: MIT
Groups: joplin
Conflicts: joplin-desktop-electron
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 262
Popularity: 1.41
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2024-07-29 19:54 (UTC)

Pinned Comments

masterkorp commented on 2021-12-27 11:30 (UTC) (edited on 2021-12-27 11:32 (UTC) by masterkorp)

Hello everyone,

There was been several difficulties upgrading the Joplin due to major changes in the build system upstream.

I have finnally got version 2.6.10 working with pacthes, but remenber:

  • You may need to remove your src/ folder before using this version

  • The patches are still not perfect, you must say yes to a prompt

I will continue working on this later today, but its usable and stable, please remenber you can always report issues on the github repository.

Regards, Alfredo Palhares

masterkorp commented on 2020-12-24 19:58 (UTC) (edited on 2020-12-24 20:00 (UTC) by masterkorp)

Hello everyone,

I will be renaming the packages to its final form.

  • joplin will contain the CLI application
  • joplin-desktop will contain the Desktop version

Also, please for problems with the package, please open an issue on the Github repo, its really hard to provide support on the comments section, you can also email me.

If you have problems with the check() function, just run makepkg with the --nocheck flag.

Thank you for your patience. Regards, Alfredo Palhares

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 54 Next › Last »

UM-Li commented on 2023-09-09 08:33 (UTC)

Hi, for the latest version gyp throws an exception and the build fails:

gyp ERR! stack Error: Cannot find module '@gar/promisify'
...
gyp ERR! System Linux 6.4.12-arch1-1
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd path/to/joplin/pkg/joplin/usr/share/joplin/.yarn/unplugged/keytar-npm-7.9.0-682d6e5c1d/node_modules/keytar
gyp ERR! node -v v20.6.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

mixin commented on 2023-09-06 20:09 (UTC)

Latest version v2.12.15 finally resolved the annoying issue that I noticed 4 months ago after updating to Gnome 44.1: it's now possible to close Joplin in maximised state and, when relaunched, it's visible and maximised.

mixin commented on 2023-07-14 20:10 (UTC) (edited on 2023-07-14 20:12 (UTC) by mixin)

Hi @jeremyjjbrown, that's quite unfortunate situation you are in. There's nothing wrong in the versions: you probably have installed "go-yq", which has the exact same executable "/usr/bin/yq" as "yq" so they can't co-exist. I'd first check if you really need "go-yq". If you do, please note that "yq" it's a build dependency for Joplin, so you could uninstall "go-yq", install "yq", build Joplin, uninstall "yq", install "go-yq".

jeremyjjbrown commented on 2023-07-10 02:52 (UTC)

I can't install because the package wants an old version of jq (3.2.2). 3.4 is installed

(4/4) checking for file conflicts                                                                                      [#######################################################################] 100%
error: failed to commit transaction (conflicting files)
yq: /usr/bin/yq exists in filesystem
Errors occurred, no packages were upgraded.
error installing repo packages

benoliver999 commented on 2023-07-02 07:15 (UTC) (edited on 2023-07-02 07:15 (UTC) by benoliver999)

Since the update I am getting the error splitCommandString is not a function when trying to edit, search and sync in the CLI version.

I posted an issue on github https://github.com/laurent22/joplin/issues/8401 but it appears to be working on their end.

The current CLI version is actually 2.11.1 and not 2.11.11, but I'll have to take their word for it because when I try to run joplin version I get

(process:3806): VIPS-WARNING **: 16:06:22.871: unable to load "/usr/lib/vips-modules-8.14/vips-openslide.so" -- libopenslide.so.0: cannot open shared object file: No such file or directory
Cannot find module './package.json'
Require stack:
- /usr/share/joplin/node_modules/joplin/app/command-version.js
- /usr/share/joplin/node_modules/joplin/app/app.js
- /usr/share/joplin/node_modules/joplin/app/main.js

tomacrisan commented on 2023-06-26 13:53 (UTC) (edited on 2023-06-26 22:41 (UTC) by tomacrisan)

I was able to build the released version, 2.11.11 with the PKGBUILD from https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=joplin-beta by changing: pkgver=2.11.11, then:

$ updpkgsums
$ makepkg --install

tomacrisan commented on 2023-05-31 21:48 (UTC)

I am having problems building the package. Here is the error I am receiving:

error Couldn't find package "@joplin/utils@~2.11" required by "./package.tgz" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
==> ERROR: A failure occurred in package_joplin().
    Aborting...

Any ideas?

mixin commented on 2023-05-12 16:32 (UTC) (edited on 2023-05-12 18:40 (UTC) by mixin)

I've tried version 2.10.18-1 and the GUI didn't show up. I needed to close it and reopen it few times for it to show. I've rolled it back to the previous version since I don't have time to investigate (might be related to the system upgrade I did at the same time). When doing that, it complained that the config files are newer. I then removed ~/.config/Joplin and ~/.config/joplin-desktop to start fresh (beware that this will delete all your notes and plugins, which is not an issue if you sync them on the cloud). Update: it's doing it also with the previous version. There are quite a few issues with latest gnome and app in fullscreen mode. It seems that if I don't use the app in fullscreen then it opens up fine.