Package Details: logseq-desktop 0.10.9-5

Git Clone URL: https://aur.archlinux.org/logseq-desktop.git (read-only, click to copy)
Package Base: logseq-desktop
Description: Privacy-first, open-source platform for knowledge sharing and management
Upstream URL: https://github.com/logseq/logseq
Licenses: AGPL-3.0-or-later
Submitter: xuanwo
Maintainer: xiota
Last Packager: xiota
Votes: 28
Popularity: 0.53
First Submitted: 2021-03-28 16:28 (UTC)
Last Updated: 2025-01-07 17:38 (UTC)

Latest Comments

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

rc0r commented on 2025-01-07 17:31 (UTC)

The .desktop in -4 is still not quite right. The Exec directive is fixed, but the Icon directive was reverted to a broken state: For icon installation, $_pkgname is used, so the .desktop entry should use it too.

rc0r commented on 2025-01-03 08:48 (UTC)

-Exec=logseq %u
+Exec=$_pkgname %u

This is not quite right for the .desktop entry in the latest PKGBUILD. On my system the binary is logseq whereas the package name is logseq-desktop. This results in not being able to launch Logseq from any launcher. Resetting to Exec=logseq %u in the desktop entry works as expected.

nando commented on 2024-12-28 22:46 (UTC)

The wrapper script (/usr/bin/logseq) contains a small mistake on the last line: A space is missing between the first two arguments of exec. Because of this, logseq fails to start when flags are passed to it using logseq-flags.conf

xiota commented on 2024-10-31 23:00 (UTC) (edited on 2024-11-01 02:32 (UTC) by xiota)

@tiziodcaio Produces errors when trying to use system electron version that isn't EOL. If you have a working PKGBUILD, I can add you as comaintainer. Otherwise, not worth the effort.

tiziodcaio commented on 2024-10-06 09:48 (UTC)

Can't we use electron from extra repository instead of bundling it? https://wiki.archlinux.org/title/Electron_package_guidelines

Xanazf commented on 2024-07-10 23:27 (UTC)

@xiota thanks for the update

that error looks like a shell error, as far as i know electron-forge is an npm/npx script, and if you run it with npx it'll suggest to install it if it's not already.

also, installing -bin version doesn't cause the same issues, perhaps it's worth looking at?

i'd still rather have this versions, don't like binaries

xiota commented on 2024-07-10 19:32 (UTC)

@Xanazf Update on progress. Problem is wrong node/npm version in repos. Solution is to use nvm to select the correct version. However, there is another problem much later in the build that I don't know how to fix.

error Command "electron-forge" not found.

I suspect may be related to more version mismatch issues. Will take more time.

xiota commented on 2024-07-10 04:28 (UTC)

@Xanazf Thank you for letting me know. I will review the package. May take a little while though. Feel free to edit your previous comment with any other problems or new information. I will check this page while working on the package.

Xanazf commented on 2024-07-10 03:49 (UTC) (edited on 2024-07-10 03:50 (UTC) by Xanazf)

having this issue here, don't understand why it's happening, tried to build manually with makepkg -sri also nothing, tried going into the folder and doing the whole yarn install && yarn gulp:build && cd static && yarn install && cd .. && clojure -P -M:cljs also nothing, seen some people say that you're supposed to go yarn install && yarn release, but since the gulp build fails either way, don't see any merit in that, send help


[06:44:52] Using gulpfile /home/xnzf/.cache/yay/logseq-desktop/src/logseq-0.10.9/gulpfile.js
[06:44:52] Starting 'build'...
[06:44:52] Starting 'clean'...
[06:44:52] Finished 'clean' after 6.47 ms
[06:44:52] Starting 'syncResourceFile'...
[06:44:52] 'syncResourceFile' errored after 19 ms
[06:44:52] TypeError: Cannot assign to read only property 'atime' of object '#<Stats>'
    at onFutimes (/home/xnzf/.cache/yay/logseq-desktop/src/logseq-0.10.9/node_modules/vinyl-fs/lib/file-operations.js:258:27)
    at FSReqCallback.oncomplete (node:fs:188:23)
    at FSReqCallback.callbackTrampoline (node:internal/async_hooks:130:17)
[06:44:52] 'build' errored after 27 ms