Package Details: joplin-desktop 3.2.13-2

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: AGPL-3.0-or-later
Groups: joplin
Conflicts: joplin-desktop-electron
Submitter: masterkorp
Maintainer: dosenpils
Last Packager: dosenpils
Votes: 268
Popularity: 1.92
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2025-03-12 23:14 (UTC)

Pinned Comments

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

1 2 3 4 5 6 .. 57 Next › Last »

michaldybczak commented on 2025-04-20 12:06 (UTC)

Why, when updating to 3.2.13-2 it always only reinstalls 3.2.12-1? I see in the PKGBUILD correct version 3.2.13-2, but installation shows: Making a package: joplin 3.2.12-1 (Sun, 20 Apr 2025, 13:29:29). What is happening how to update it sucessfully?

luc4 commented on 2025-04-12 13:16 (UTC) (edited on 2025-04-12 13:16 (UTC) by luc4)

Installation failed for me on Endeavour with this error:

==> Checking runtime dependencies...
==> Missing dependencies:
  -> libexif
  -> nodejs-lts-iron
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: joplin-exit status 8

It seems installing libexif and nodejs-lts-iron manually fixed the problem.

OdinVex commented on 2025-03-16 19:56 (UTC) (edited on 2025-03-16 20:27 (UTC) by OdinVex)

@tomacrisan, Mine builds, but any attempt to check synchronization or synchronize just results in it timing out 2047s later while trying. Never syncs. Phone does, same network. I can open a browser and directly visit my Joplin instance (I host my own). It simply stopped working once I got the 10b22a33a84bb603e76cfa2aebf5376fe8d2b561 update. Tried cloning the older version but now the issue appears no matter how far I go back. Not sure what it is, though I do know I recently had to remove Manjaro's community repo and got a slew of updates, including for node and electron (but I'm using the same node business as you are). Edit: I should clarify, it does try, I see the DNS query and the TLS connection, it just never...ends/wraps up and there's zero status change ever.

tomacrisan commented on 2025-03-16 19:47 (UTC)

@OdinVex: I may have misunderstood your earlier message. My problem was with building. If I understand you correctly, your installation is building but not connecting. Do you mean it is not syncing or connecting to the Joplin server?

OdinVex commented on 2025-03-16 19:35 (UTC)

@tomacrisan, Thank you for the follow-up, same here. I guess I'll have to dive deeper.

tomacrisan commented on 2025-03-16 19:22 (UTC) (edited on 2025-03-16 19:28 (UTC) by tomacrisan)

@OdinVex: Now when I type $ node -v, I receive the following:

$ node -v
v20.18.3

This is the correct version of nodejs-lts-iron.

Also, when I type $ which node, I receive:

$ which node
/usr/bin/node

Before I deleted the extraneous version of nodejs, I would receive:

$ which node
/usr/local/bin/node

This version was executing before the required installed version.

I manually deleted the components of the old nodejs I found under the /usr/local/bin, /usr/local/, /usr/local/include, and /usr/local/lib/node_modules/.

OdinVex commented on 2025-03-16 18:10 (UTC)

@tomacrisan, Could you provide more details? I'd like to make sure I don't have something messing my installation up. Mine compiles but just stays "connecting", times out after 2047 seconds. Meanwhile other devices (different OS) connect fine, same network, wondering if it's just my installation.

tomacrisan commented on 2025-03-16 18:04 (UTC)

@dosenpils: I want to report the cause to my problems with building joplin using your PKGBUILD and it was clearly my fault. I found that I had a version of nodejs from 2023 installed under /usr/local/ that was unknown to the package manager but was executing before the nodejs-lts-iron package that is installed under /usr/.

The reason the joplin-beta PKGBUILD would work for me is that it would install a copy of nodejs of the required version in the build directory.

Thanks for your work in providing Joplin for the Arch community and apologies for any of your time I might have wasted.

OdinVex commented on 2025-03-16 16:20 (UTC) (edited on 2025-03-16 16:35 (UTC) by OdinVex)

Ever since 10b22a33a84bb603e76cfa2aebf5376fe8d2b561 I've not been able to connect to anything, unable to determine why either. Giving up. (Edit: Not saying it's this AUR or anything else, just mentioning the timing.) Edit: Fixed which commit.

rellieberman commented on 2025-03-13 13:25 (UTC)

not having the nodejs-lts-iorn dependency was good, some things on my system did not work well with it (only with the regular nodejs)

1 2 3 4 5 6 .. 57 Next › Last »