Arch Linux User Repository

This package sets HOME=${SRCDEST:-$startdir}/node-home to avoid cluttering the user home directory, while allowing data (over 4GB) to be reused between builds. $srcdir is not used for this purpose because it can be wiped between runs.

This is interesting. I have different results on two different computers. (AMD vs Intel?) Will go ahead and bump versions. Any users who have the same build failure, try rolling back to 0.9.13 or use the -bin package.

No need to re-report the same issue. I'll update if I find a solution.

Note: No solution as of Jan 2024.

Clean chroot. Attempting to build after bumping to 0.9.14 or later results in error. Possibly related to AMD processors. Anyone know how to fix?

[4/4] Building fresh packages...
$ yarn build:amplify
$ parcel build ./src/amplify.ts --no-source-maps
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in prepare().

@zany130

It's strange to see.

ls /opt/logseq-desktop/Logseq -lh
"/opt/logseq-desktop/Logseq": Permission denied (os error 13)

What's your outout of ls / -lh | grep opt and ls /opt -lh | grep logseq?

I expect the see the following:

:) ls / -lh | grep opt
drwxr-xr-x  13 root root  209 Nov 29 02:14 opt
:) ls /opt -lh | grep logseq
drwxr-xr-x 4 root root 4.0K Jan 13 02:57 logseq-desktop

@xuanwo

ls /usr/bin/logseq -lh
Permissions Size User Date Modified Name
lrwxrwxrwx    26 root  2 Feb 19:11   /usr/bin/logseq -> /opt/logseq-desktop/Logseq

ls /opt/logseq-desktop/Logseq -lh
"/opt/logseq-desktop/Logseq": Permission denied (os error 13)

 ╭─zany130@Garuda in ~ via  v3.10.9 as 🧙 took 1ms
[🔴] × sudo ls /opt/logseq-desktop/Logseq -lh
-rwxr-xr-x 1 root root 147M Feb  2 19:11 /opt/logseq-desktop/Logseq

@zany130

Interesting. Can you give the output of ls /usr/bin/logseq -lh?

Not working on garuda Linux get this

logseq
fish: Unknown command. '/usr/bin/logseq' exists but is not an executable file.

 ╭─zany130@Garuda in ~ via  v3.10.9
[🚫] × bash
[zany130@Garuda-Linux ~]$ /usr/bin/logseq
bash: /usr/bin/logseq: Permission denied
[zany130@Garuda-Linux ~]$ sudo /usr/bin/logseq
[sudo] password for zany130:
[0202/191636.827111:FATAL:electron_main_delegate.cc(298)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

I'm getting a compilation error for the better_sqlite3 dependency, but just bumping up the PKGBUILD to newest release (0.8.15->0.8.16) solves it. @xuanwo any chance for a version bump?

@Radeox Thanks for the reminder!

I'm guessing you are talking about logseq-desktop-bin. The package has been updated now!

@xuanwo I think you've forgot to update the checksum for logseq-desktop.desktop after the last commit

@gwpl Have you tried replacing nodejs with nodejs-lts-gallium?

logseq-desktop Archlinux does not compile https://pastebin.com/BMLG1EFu