Package Details: logseq-desktop 0.10.15-2

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: 32
Popularity: 0.094254
First Submitted: 2021-03-28 16:28 (UTC)
Last Updated: 2025-12-04 01:16 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

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

xiota commented on 2025-12-04 01:02 (UTC)

Thanks for the notice. Will push update momentarily.

Related: logseq/logseq/12243

Tagman commented on 2025-11-25 09:05 (UTC)

Apparently the sha of tarball has changed again. The checksum validation is failing when updating.

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.

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