Arch Linux User Repository

Thank you dosenpils and masterkorp for supporting the package.

I replaced the PKGBUILD with the version I wrote for the archlinuxcn repo. I will do my best to follow the latest nodejs and electron versions.

Please try to build in a clean chroot (i.e., with extra-x86_64-build from devtools package) if you have problems building the package.

If you want to use the fcitx input method under wayland, please complete the following configuration:

cat .config/electron25-flags.conf 
--enable-wayland-ime
--ozone-platform=wayland

@luc4 I had to install nodejs 22 to build the package. I first tried changing the dependency to nodejs<=24 but the build failed. I then installed nodejs v22 and was able to build.

Okay, it turns out that previous version was not running on native wayland, it was not reading the electron-flags.conf file. However, I can confirm that it does work fine with Wayland running joplin-desktop --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland

Any ideas to fix this on the new version?

Any idea how to fix this error?

:: (1/1) Parsing SRCINFO: joplin
==> Making package: joplin 3.3.12-1 (mar 20 mag 2025, 19:13:42)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> nodejs<=23
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: joplin-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
joplin-desktop - exit status 8

I already have nodejs:

$ node --version
v23.11.1

Thanks.

After the last update, I cannot start Joplin natively in Wayland. It complains about the flag --ozone-platform-hint=auto. Shouldn't this be supported since it's using electron-36? Anyone running Joplin without XWayland here?

@mplx Oops, my bad. Fixed. Thank you for pointing this out.

Thank you cuihao for taking the maintainance of the joplin-package! A formal remark: your PKGBUILD states the software to be MIT licensed, however Joplin is AGPL-3.0-or-later - see https://github.com/laurent22/joplin/blob/dev/LICENSE

While I am able to build Joplin, I am experiencing a problem with the Build-In Backup Plugin not running. Under the Option settings for Plugins, the Back-up Plugin is enabled but for some reason it is not running. I have also experienced this problem when building Joplin with the joplin-beta PKGBUILD. I have reported the bug to the Backup Plugin author (Backup Plugin Anomaly) but the problem appears limited to building Joplin in an Arch environment.

The binaries built from the Joplin project work as expected in an Arch environment; it is only when I build the binaries that I experience the problem. Any ideas what could be wrong?

@cuihao, I never said those scenarios were directly linked, merely that they can be results of bad habits.

@OdinVex If my key is unfortunately leaked, the attacker is able to alter the checksums altogether :)

Regarding my name, thank you for clarifying. Uppercasing conventionally indiates the family name is placed at the beginning.

@cuihao, I'm just not the type to go lax on something I'm posting public. SKIP is expected for git pulls on -git packages but not for anything that is static and unchanging. Habits like earlier tend to bleed bleed into other areas of life and before you know it your SSH key is leaked and someone's uploading packages under your name or your boss is letting you go and blacklisting you in the neighborhood. Merely pointing out for a AUR package I used to use. As for email, "CUI" vs "Cui", is that an organization or?