Package Details: logseq-desktop 0.10.14-3

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
Keywords: clojure clojurescript git graph knowledge-base knowledge-graph local-first markdown note-taking org-mode pkm
Licenses: AGPL-3.0-or-later
Submitter: xuanwo
Maintainer: xiota (Edu4rdSHL)
Last Packager: xiota
Votes: 30
Popularity: 0.184218
First Submitted: 2021-03-28 16:28 (UTC)
Last Updated: 2025-10-14 19:54 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

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

xiota commented on 2025-10-15 01:59 (UTC)

@skimm Package already fixed.

skimm commented on 2025-10-15 01:14 (UTC)

Same issue as @gnaeljmdmmcbqvpz, the quick fix is just setting the term in the desktop entry, but that shouldn't be required.

Adding TERM=xterm-256color to my menu item for it allows me to launch it via Plasma 6 without issue.

gnaeljmdmmcbqvpz commented on 2025-10-14 00:44 (UTC)

Since a recent update, Logseq is no longer launching. I'm using Plasma 6. Looking in my logs, I can see the following messages:

systemd[1956]: Started Logseq.
logseq[3447]: tput: No value for $TERM and no -T specified
systemd[1956]: app-logseq\x2ddesktop@903174a6f90e428ea45065f36b1b6d2f.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
systemd[1956]: app-logseq\x2ddesktop@903174a6f90e428ea45065f36b1b6d2f.service: Failed with result 'exit-code'.

I assume this is an interaction between the setopt, Plasma, and tput. Plasma runs applications under Systemd, Systemd doesn't set $TERM, and tput fails because it can't find a terminal to produce colour codes for.

Running logseq from within a terminal works just fine, as expected, but I'd really rather not have to do that.

luqtas commented on 2025-10-09 05:17 (UTC) (edited on 2025-10-09 05:18 (UTC) by luqtas)

setting it to launch with %u didn't worked for me, however if we enable Run on Terminal on XFCE and we launch exclusively from the App Finder it works... the below script also launch the app for me,

!/bin/bash

TERM=xterm-256color logseq

xiota commented on 2025-09-30 16:40 (UTC)

Switched to system Electron. Will switch back to vendored Electron if not updated to newer Electron before electron34 drops out of official repos.

projectgus commented on 2025-09-29 04:41 (UTC) (edited on 2025-09-29 04:42 (UTC) by projectgus)

GitHub seems to have regenerated its tarballs since the 0.10.14 release. I now get:

❯ sha256sum logseq-0.10.14.tar.gz 
0e6da0a48933f4c7c4fcdd0e195e0eb7d6eeb8fad4eb1a6226910f78345d1777  logseq-0.10.14.tar.gz

(Thanks for all your work packaging logseq!)

Swamp commented on 2025-08-18 17:26 (UTC)

I just updated Logseq Desktop and noticed a warning about the version of Electron being used:

WARNING: Logseq uses Electron/34.5.6. To check whether this version of Electron still receives security updates, see https://endoflife.date/electron

It's worth noting that support for version 34 ended 1 month and 3 weeks ago (on June 24, 2025). I want to second tiziodcaio's question—can we use the Electron version from the extra repository instead?

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.

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