Package Details: joplin-appimage 2.8.8-1

Git Clone URL: (read-only, click to copy)
Package Base: joplin-appimage
Description: The latest stable AppImage of Joplin - a cross-platform note taking and to-do app
Upstream URL:
Keywords: appimage joplin markdown note notetaking productivity
Licenses: MIT
Conflicts: joplin-desktop
Submitter: kirillz
Maintainer: thynkon
Last Packager: thynkon
Votes: 61
Popularity: 4.54
First Submitted: 2020-06-19 14:03 (UTC)
Last Updated: 2022-06-07 06:42 (UTC)

Pinned Comments

thynkon commented on 2021-06-16 20:49 (UTC)


From now, this package will only track stable releases of Joplin.

Latest Comments

galvez_65 commented on 2022-07-28 03:09 (UTC)

made a variation of this PKGBUILD ( file which expands the applimge file rather than using the appimage as is.

maderios commented on 2022-03-17 18:51 (UTC)

2.7.15 is out

thynkon commented on 2022-01-23 20:42 (UTC)

Hi @deafmute, thank you for your feedback. Instead of creating /usr/share/appimagekit/no_desktopintegration, PKGBUILD now sets an environment variable to disable desktop integration.

The last update should fix your problem.

As always, if you still have problems, feel free to contact me.

deafmute commented on 2022-01-23 13:08 (UTC) (edited on 2022-01-23 13:10 (UTC) by deafmute)

Right now, the integration disabler script in PKGBUILD breaks the install if any other package has done the same thing. I get this error on my system:

joplin-appimage: /usr/share/appimagekit/no_desktopintegration exists in filesystem (owned by sonixd-appimage)

Workaround is to manually delete this file and then attempt install again.

PKGBUILD should either detect that the desktop integration prevention has not been done already before attempting, or simply delete this file per-emptively before attempting.

inverse commented on 2022-01-14 08:01 (UTC)

@thynkon Can confirm latest fix resolved it for me. Thanks :)

thynkon commented on 2022-01-13 17:24 (UTC)

Thanks @graves501, @chiwanpark and @vith for your comments. I'm running KDE and it's weird that I didn't have the same problem as you.

It' s now solved. As always, if you still have problems, feel free to contact me.

vith commented on 2022-01-13 17:14 (UTC)

It also doesn't show up in gnome-shell for me.

/usr/share/applications/joplin.desktop exists but MenuLibre says:

Exec program 'APPIMAGELAUNCHER_DISABLE=1 /usr/bin/joplin-desktop --no-sandbox %U' has not been found in the PATH

adding env at the beginning of the Exec value seems to fix it.

thynkon commented on 2022-01-13 17:03 (UTC)

Hi @inverse, I am sorry you are having problems since the last update. Could you tell me if the file /usr/share/applications/joplin.desktop exists?

inverse commented on 2022-01-13 15:21 (UTC)

Since the latest update - I don't have desktop file to launch. I can launch via CLI only.

graves501 commented on 2022-01-11 13:26 (UTC)

I agree with chiwanpark!

The desktop file needs to be fixed by adding env, resulting in this line:

Exec=env APPIMAGELAUNCHER_DISABLE=1 /usr/bin/joplin-desktop --no-sandbox %U

chiwanpark commented on 2022-01-09 13:04 (UTC)

We need to modify desktop file.

To add environment variable, we need to add env command before environment variable. (

Currently, joplin.desktop file has Exec entry as follows.

Exec=APPIMAGELAUNCHER_DISABLE=1 /usr/bin/joplin-desktop --no-sandbox %U

We need to fix it as follows.

Exec=env APPIMAGELAUNCHER_DISABLE=1 /usr/bin/joplin-desktop --no-sandbox %U

simona commented on 2022-01-08 22:49 (UTC)

now is perfect...

Rhinoceros commented on 2022-01-08 22:13 (UTC) (edited on 2022-01-08 22:13 (UTC) by Rhinoceros)

That great. Thanks @thynkon for the quick work! Your fix works perfectly on my system.

thynkon commented on 2022-01-08 19:34 (UTC)

I have just updated the package. The integration alert should now be gone. You can now call joplin-desktop from the terminal if you want to launch the application 'manually'.

If you still have problems, feel free to leave a message.

thynkon commented on 2022-01-08 12:09 (UTC)

Hi @jrwrigh and @Rhinoceros, you can't actually access the application image without specifying the full path. As appimages can be quite large, they should be in /opt.

But, as Rhinoceros pointed out, there should be a symbolic link in /usr/bin pointing to the appimage.

I will try to solve this problem as soon as possible and will keep you up to date.

thynkon commented on 2022-01-08 12:03 (UTC)

Hi @simona, thanks for your comment. I've been busy the last few days but I still had time to address your issue. It looks like you are using AppImageLauncher to manage appimages on your system.

I found out that it is possible to disable it when running the images (which is the case when you use this package) by doing this.

I'm working on this problem and I'll tell you more when it's solved.

Rhinoceros commented on 2022-01-08 04:28 (UTC)

@jrwrigh I have the same problem. I can't run joplin from the CLI. The desktop file points to /opt/appimages/Joplin.AppImage, so I can launch it from my DE. I think normally the package adds the executable to /usr/bin.

jrwrigh commented on 2022-01-08 00:58 (UTC)

Possibly user error, but the joplin appimage is not in my $PATH. I can access and run the appimage at /opt/appimages/Joplin.AppImage sucessfully. Before I manually add /opt/appiamges to my path, I just wanted to make sure I didn't miss a "correct" way of doing it.

simona commented on 2022-01-04 12:04 (UTC)

every time I launch joplin i have to confirm:
- opt/appimages/Joplin.AppImage non è stato integrato nel tuo sistema.

Integrandolo, l'AppImage verrà spostato in una posizione predefinita e verrà incluso nel programma di avvio dell'applicazione.

Per rimuovere o aggiornare AppImage, utilizzare il menu di scelta rapida dell'icona dell'applicazione nella barra delle applicazioni o nel programma di avvio.

La directory in cui sono archiviate le AppImages integrate è attualmente impostata su: /home/simona/Applications
- opt/appimages/Joplin.AppImage non è stato integrato nel tuo sistema.

Integrandolo, l'AppImage verrà spostato in una posizione predefinita e verrà incluso nel programma di avvio dell'applicazione.

Per rimuovere o aggiornare AppImage, utilizzare il menu di scelta rapida dell'icona dell'applicazione nella barra delle applicazioni o nel programma di avvio.

La directory in cui sono archiviate le AppImages integrate è attualmente impostata su: /home/simona/Applications

Rhinoceros commented on 2022-01-03 22:28 (UTC)

Thanks for this package. Please add a provides and/or conflicts with joplin-desktop.

thynkon commented on 2021-10-25 19:44 (UTC)

IMPORTANT: If you get the following error: 'Last error: FetchError: request to XXX failed, reason: certificate has expired', note that this is due to the Let's Encrypt root CA.

Although this has been fixed in v2.5, you can temporarily disable TLS certificate errors by checking 'Ignore TLS certificate errors' in Configuration > Synchronization > Advanced options.

For more details, see the upsteam note on this topic.

thynkon commented on 2021-08-16 18:41 (UTC)

CAUTION: This release will ask you to upgrade your sync target, whether it's Dropbox, OneDrive, Joplin Cloud, etc. Once it is done, only apps version 2.3+ will be able to sync with it, so make sure you are ready to upgrade all your apps before installing this version.

thynkon commented on 2021-08-11 08:06 (UTC)

IMPORTANT: If you are a plugin developer or if, as a user, you notice a plugin that no longer works, please read this post.

Zodiac commented on 2021-07-15 15:04 (UTC)

I switched over this package (previously i was using joplin-desktop) because its updated more frequently, faster, and It Just Works (tm). No problems so far, good job to the maintainer/s

thynkon commented on 2021-06-16 20:49 (UTC)


From now, this package will only track stable releases of Joplin.

thynkon commented on 2021-06-05 12:14 (UTC) (edited on 2021-06-05 12:14 (UTC) by thynkon)


This package was not updated to v2.0.4 because the checksum of the appimage file provided by the upstream is not correct. It will be fixed in the next Joplin's release. Github issue link

thynkon commented on 2021-05-19 18:33 (UTC)

Hi @FillFeile, since more people are using this package and there is no other AUR package that keeps up with the stable release of Joplin, I will do it.

I'm just waiting for the next stable release so I can update the description of this package.

Again, thanks for your feedback and feel free to contact me if you have any questions or suggestions.

FillFeile commented on 2021-05-18 06:55 (UTC)

Hi @thynkon, thanks for your fast reply.

Sorry for that.. a proper read might have clarified things in the first place.

I think what derailed me is the pinned comment which (also with a picture) refers to the latest release. Maybe if this is inaccurate one can remove it.

thynkon commented on 2021-05-17 19:38 (UTC)

Hi @FillFeile, thanks for your remarks. As you can see from the description of this package, I only package the Joplin pre-releases.

So yes, this is intentional. But, if most of the users of this package are only interested in the stable releases, I might start using this package to track the stable releases of Joplin.

If you still have questions, please let me know.

FillFeile commented on 2021-05-17 16:21 (UTC)

Dear @thynkon, thanks for maintaining this one.

I noticed that you recently packaged v2.0.1 of Joplin which is (as stated on GitHub and the project website) still a pre-release version.

The latest stable version at time of writing seems to be v1.8.5.

Is this intentional?

Cheers, FillFeile

thynkon commented on 2021-04-05 05:09 (UTC)

Hi @ocelotsloth, thanks for your feedback. I don't know how I missed that. fuse2 has been added to the PKGBUILD file as a runtime dependency.

If you still have problems building the package, feel free to contact me.

ocelotsloth commented on 2021-04-04 23:52 (UTC)

Looks like fuse2 is a runtime dependency.

❯ /opt/appimages/Joplin.AppImage 
dlopen(): error loading

AppImages require FUSE to run. 
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
for more information

Can you update the PKGBUILD to add fuse2 as a runtime dependency? Thanks!

thynkon commented on 2020-12-30 12:38 (UTC)

Usually this package tracks the highest/latest version but v1.5.14 fixed some errors that I thought that could be useful for everyone who uses this package. As you said, the upstream is tagging versions out of order and I don't know if they are working on a new version or if it was a mistake.

For now, the latest version of this package will remain "v1.5.14" for the reason I mentioned above and I will keep monitoring the upstream tags.

Thanks for your feedback @vith.

vith commented on 2020-12-30 12:13 (UTC)

It looks like the upstream project is tagging versions out of order because they're maintaining the 1.5 line while also working on 1.6, so the version here has gone backwards from 1.6.1 to 1.5.14.

If this package is supposed to track the "latest" release including pre-releases, maybe "latest" should be "highest version" instead of by timestamp.

thynkon commented on 2020-12-30 10:04 (UTC) (edited on 2020-12-30 10:04 (UTC) by thynkon)

Hi @ben2talk, self-contained packages like appimages should be installed in /opt as per Arch package guidelines.

I have reinstalled this package several times and I had no icons problems. Could you give me more information about your problem?

ben2talk commented on 2020-12-30 04:50 (UTC)

  1. No icon is apparent
  2. If installed via AUR it is put in /opt folder, not suitable for a user.
  3. Icons still need manual intervention (10th Dec '20).

thynkon commented on 2020-12-17 18:27 (UTC) (edited on 2020-12-18 20:15 (UTC) by thynkon)

Hi @winicius, appimages desktop integration allows you to launch appimages using your desktop environment launcher. I have disabled it for this package.
Are you using something like AppImageLauncher to launch joplin? In order to execute an appimage, all you need to do is to make it executable.

winicius commented on 2020-12-16 23:20 (UTC)

Is there any way to disable the integrate dialog? It always fails and I don't even know what it is supposed to do

thynkon commented on 2020-11-16 18:34 (UTC)

Thank you @vith for your feedback. The last update should fix the missing icons. If it does not, do not hesitate to contact me.

vith commented on 2020-11-16 07:04 (UTC) (edited on 2020-11-16 07:19 (UTC) by vith)

I needed to change the Icon field of the .desktop to Icon=@joplinapp-desktop for it to work for me.

edit: Actually that only worked briefly, then went back to showing a broken icon (on gnome-shell).

edit2: Looks like it needed the @, I was just confused by the cache. Icon=@joplinapp-desktop

thynkon commented on 2020-11-08 20:40 (UTC)

Thank you @petsam for your feedback. I have fixed the PKGBUILD file. For those who might have issues building the package (1.4.7-1), all you need to do is to update to the version 1.4.7-2 and the problems should be gone. If you still have issues, don't hesitate to contact me.

petsam commented on 2020-11-08 19:59 (UTC) (edited on 2020-11-08 20:11 (UTC) by petsam)

There are some changes in file names (.png, .desktop). I changed PKGBUILD and installed successfully. Here is the diff:

<     ./$_filename --appimage-extract "usr/share/icons/hicolor/*/apps/joplin.png" > /dev/null 2>&1
<     ./$_filename --appimage-extract joplin.desktop > /dev/null 2>&1
>     ./$_filename --appimage-extract "usr/share/icons/hicolor/*/apps/@joplinapp-desktop.png" > /dev/null 2>&1
>     ./$_filename --appimage-extract @joplinapp-desktop.desktop > /dev/null 2>&1
<     sed -i -E "s|Exec=AppRun|Exec=${INSTALL_PATH}|" squashfs-root/joplin.desktop
>     sed -i -E "s|Exec=AppRun|Exec=${INSTALL_PATH}|" squashfs-root/@joplinapp-desktop.desktop
<     find "$pkgdir/usr/share/icons" -type f -name "joplin.png" -exec chmod 644 {} \;
>     find "$pkgdir/usr/share/icons" -type f -name "@joplinapp-desktop.png" -exec chmod 644 {} \;
<     install -Dm644 "squashfs-root/joplin.desktop" "$pkgdir/usr/share/applications/joplin.desktop"
>     install -Dm644 "squashfs-root/@joplinapp-desktop.desktop" "$pkgdir/usr/share/applications/@joplinapp-desktop.desktop"

thynkon commented on 2020-11-07 20:28 (UTC) (edited on 2020-11-14 12:16 (UTC) by thynkon)

IMPORTANT: If you use the Clipper API, please note that there are a few breaking changes in this version. See this link for more information: #3983

Plugins: now returns an object instead of the button ID that was clicked. So for example instead of getting just "ok", you will get { "id": "ok" }. This is to allow adding form data to that object.

NeedleNardleNoo commented on 2020-07-30 09:29 (UTC)

The error in package() appears to come from the most recent change to the PKGBUILD. The line-change that needs to be reverted is the following:

        pkgrel = 1
-       url =
+       url =
        arch = x86_64

The url with .../releases/tag/v1.0.229 returns an html page instead of the intended source files. This fix also works when I modify the version to v1.0.232.

Parsec82 commented on 2020-07-30 07:50 (UTC)

Same problem on my system

amatriain commented on 2020-07-26 12:07 (UTC)

Build version 1.0.229-1 fails:

$ makepkg -s
==> Making package: joplin-appimage 1.0.229-1 (Sun 26 Jul 2020 14:05:39 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found Joplin-1.0.229.AppImage
  -> Found LICENSE
==> Validating source files with sha512sums...
    Joplin-1.0.229.AppImage ... Skipped
    LICENSE ... Skipped
==> Extracting sources...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...

     _             _ _       
    | | ___  _ __ | (_)_ __  
 _  | |/ _ \| '_ \| | | '_ \ 
| |_| | (_) | |_) | | | | | |
 \___/ \___/| .__/|_|_|_| |_|

==> ERROR: A failure occurred in package().

kirillz commented on 2020-07-24 09:37 (UTC) (edited on 2020-07-24 09:41 (UTC) by kirillz)

I agree, thank you. Somehow not exactly. I'll fix it in the next commit. "The latest pre-released AppImage of Joplin - a cross-platform note taking and to-do app"

marties commented on 2020-07-22 15:48 (UTC)

Hi, thanks for your answer, i checked the URL and it's labeled pre-release, maybe you should alter your description accordingly and not 'The latest released'. Anyway thanks for your involvement.

kirillz commented on 2020-07-22 11:29 (UTC)

Thank you for watching. Here is the answer to your question. I checked the functionality of the application myself. You can also take the stable version if you are not happy with the current one.

marties commented on 2020-07-21 13:47 (UTC)

Hello, how is this possible that your Joplin version is 1.0.229-1 while the github list the last update as 1.0.227 14 days ago?

I think this a dangerous use, as downgrading to the real version keeps the user out of his previous notes (wrong sqlite database version).

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

Thanks kirillz for maintaining this package! Good news: The update to joplin-appimage-1.0.224-1 fixed the problem. All is working well on 1.0.224-1.

kirillz commented on 2020-06-20 17:56 (UTC) (edited on 2020-06-20 18:06 (UTC) by kirillz)

SweetestRug, Thx for comment. Unfortunately, 223 doesn’t work for me either, but 221 worked. Downgraded to working version 221

SweetestRug commented on 2020-06-20 17:50 (UTC)

Joplin 1.0.223 fails to load application, either from the installed appimage or the downloaded appimage itself.

kirillz commented on 2020-06-19 14:27 (UTC) (edited on 2020-06-19 14:33 (UTC) by kirillz)

It's just a appimg from github releases.

hvksmr1996 commented on 2020-02-22 04:18 (UTC) (edited on 2020-02-27 02:57 (UTC) by hvksmr1996)


This package is to download AppImage file from GitHub Release and install it. It is not out-of-date if the latest release lacks such file.

Also this is what a true latest release looks like: