Arch Linux User Repository

1. This package does not support system's electron anymore because yarn's electron already supports Wayland.
2. The desktop file by default launches Logseq with the regular X11 backend. There's an extra action defined in the desktop file to launch with the Wayland backend. How to trigger an action within a desktop file depends on your desktop environment or app launcher.
3. The package uses a user's home directory to store cached npm/clojure dependencies. Hope this speeds up the build process for users who don't have high-speed internet.

Extra notes to people who want to flag this package out-of-date:

This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.

Do you mind add the following args to logseq so that logseq adapt to the backend automatically?

logseq --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations

Reference: https://github.com/logseq/logseq/issues/5010#issuecomment-1234836567

@MithicSpirit I removed the step that packages things into a zip file in the PKGBUILD, so zip should not be needed anymore. Please let me know if it works. Thanks!

Please add zip to makedepends. Build fails for me otherwise with:

Making for the following targets: zip, appImage
- Making for target: zip - On platform: linux - For arch: x64
✖ Making for target: zip - On platform: linux - For arch: x64

An unhandled error has occurred inside Forge:
An error occured while making for target: zip
spawn zip ENOENT
Error: spawn zip ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'm building in a chroot so most regular system packages are missing.

1. This package does not support system's electron anymore because yarn's electron already supports Wayland.
2. The desktop file by default launches Logseq with the regular X11 backend. There's an extra action defined in the desktop file to launch with the Wayland backend. How to trigger an action within a desktop file depends on your desktop environment or app launcher.
3. The package uses a user's home directory to store cached npm/clojure dependencies. Hope this speeds up the build process for users who don't have high-speed internet.

Extra notes to people who want to flag this package out-of-date:

This is a GIT AUR package. It has nothing to do with the released versions. Whenever you (re-)build a GIT AUR package, it automatically pulls and (re-)builds with the latest commit and updates the version tag. So as long as the building process works fine, a GIT AUR package is not out-of-date.

@jw220725 The plugin should work now. Please let me know if it's still not working.

@jw220725 I will take a look this weekend. Did you try the release version (the AUR package logseq-desktop)? If so, did it also have the same issue?

The plugin-bar widget for the TODO List plugin (1.5.0) is not displaying content with Logseq (v0.7.8) built using this package (e.g. on macOS they work together for me).

See https://github.com/ahonn/logseq-plugin-todo/issues/12 for screenshots and other affected versions.

@pychuang sorry for the false report

@bader It seems you posted to the wrong page? It seems the error message is about the package rum, not logseq-desktop-git. rum is not a dependency of logseq-desktop-git.

@malcolm Thanks for the suggestion. I'll update the PKGBUILD later.

The package fails to build to an error during building rum.

> rum@0.7.1 build
> svelte-kit build

> config.kit.ssr has been removed — use the handle hook instead: https://kit.svelte.dev/docs#hooks-handle
    at file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:598:12
    at file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:677:43
    at file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:663:18
    at file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:663:18
    at validate_config (file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:822:9)
    at load_config (file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:799:20)
    at async file:///home/chell/.cache/yay/rum/src/rum/node_modules/@sveltejs/kit/dist/cli.js:920:19
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: rum