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.96
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

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 57 Next › Last »

Deuchnord commented on 2020-06-25 12:49 (UTC) (edited on 2020-06-25 12:50 (UTC) by Deuchnord)

Can you copy the application icon to /usr/share/pixmaps/joplin.png and update the line 6 of the joplin.desktop to:

Icon=joplin

This will make it possible to customize it in icon themes.

SweetestRug commented on 2020-06-15 21:38 (UTC)

Build as of June 15 is failing. Failure starts at

/bin/sh: pkg-config: command not found gyp: Call to 'pkg-config --cflags libsecret-1' returned exit status 127 while in binding.gyp. while trying to load binding.gyp

with multiple gyp ERR! following. For what its worth, I am running Manjaro.

<deleted-account> commented on 2020-05-22 23:21 (UTC)

It’s not Zemoose’s fault. To keep certain packages from breaking and bugs from arising, Joplin’s main team is locking in specific versions. The dependencies have gotten managed better than they used to be but the whole “use new libraries where able to save time and code maintenance” approach is a bit problematic at times.

I wouldn’t recommend updating most packages if you can avoid it because of this.

siddharthagolu commented on 2020-05-22 20:45 (UTC)

@ZeMoose, just to be on the safe side, you should periodically check for npm update and resolve those security vulnerabilities by running npm audit fix.

malcolm commented on 2020-05-21 13:56 (UTC)

this version is very outdated. please do something

<deleted-account> commented on 2020-05-18 17:13 (UTC)

Hey, all. My name is Brandon and I'm a member of the Joplin Team. I'm not one of the core devs but instead primarily am focused on Linux support and research.

Here's my credentials on the Forums: https://discourse.joplinapp.org/g/Team

Here's my main contribution to the project so far: https://github.com/laurent22/joplin/issues/3114

@ZeMoose, the dependencies of Joplin do concern me quite a bit myself. I'd love to hear which ones concern you the most.

RockhopperP commented on 2020-05-15 08:17 (UTC)

If confronted with a 'fatal error: unknown table: settings' it helped me to rm -rf ~/.config/Joplin/ ~/.config/joplin-desktop/ and reinstall joplin from the already compiled package.

Such was suggested here: https://discourse.joplinapp.org/t/solved-linux-fatal-error-unknown-table-settings/6253

ZeMoose commented on 2020-05-08 03:58 (UTC)

Should I be concerned about the hundreds of low and moderate severity vulnerabilities reported by npm during the build process?

avndp commented on 2020-05-06 02:47 (UTC)

Building fails all the time.

vv181 commented on 2020-04-29 21:52 (UTC)

@imlonghao

It still does not work.

I'll put the log here:https://pastebin.com/3CfZQ0NR

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 57 Next › Last »