API server fails to automatically start

[caelia]

Search first

• [X] I searched and no similar issues were found

What Happened?

I am running LogSeq 0.9.18 on Arch Linux (installed from the AUR package logseq-desktop-bin.

I have configured my API server to automatically start on application startup. If I shut down and restart LogSeq, I see that the setting is saved (i.e. the "Auto start server with the app launched" checkbox remains checked), but the server does not automatically start.

I have confirmed that the server functions as expected when started manually. I am using the Omnivore-LogSeq connector plugin, and content captured with Omnivore appears in LogSeq as expected.

Reproduce the Bug

1. Enable autostart in server configuration.
2. Shut down LogSeq.
3. Restart LogSeq.

Expected Behavior

API server should be running, without manual intervention, when LogSeq is started.

Screenshots

No response

Desktop or Mobile Platform Information

Arch Linux Vivaldi 6.2.3105.48 LogSeq 0.9.18

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• [ ] I'm willing to submit a PR (Thank you!)

[ShrimpyChips]

I'm experiencing this same behavior on a Windows 10 installation and an installation on Linux Mint 21.2. Logseq is version 0.9.20 on both.

[ScriptingDad]

I'm also encountering this problem on Ubuntu 22.04 with the Appimage version 0.10.3 and with a flatpak version. Logs don't show any attempt to start the server.

~/Applications/Logseq-linux-x64-0.10.3_88a6a3e4fddd529425779f786d5c9fb1.AppImage -vv
(rsapi) init loggers
12:02:23.921 › Logseq App(0.10.3) Starting...
12:02:23.927 › restore proxy settings {:type "system"}
12:02:23.927 › set proxy to {:type "system"}
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[35639:0111/120226.806347:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
12:02:27.258 › :electron.handler/watch-dir {:path "/home/alharris/.logseq/config"}
12:02:27.430 › :electron.handler/unwatch-dir {:path "/home/alharris/Documents/Vault"}
12:02:27.431 › :electron.handler/watch-dir {:path "/home/alharris/Documents/Vault"}

I see some root cert stuff in there but since we don't appear to be using a certificate for the local server I don't think this is applicable.

Willing to try to make a PR if someone can point me to the files where the server starts and where the automatic start would trigger from.

[mbeware]

I have the same issue. API is configured and set to auto-start but it does not.

Linux version 6.6.10-76060610-generic ([email protected]) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #202401051437~1704728131~22.04~24d69e2 SMP PREEMPT_DYNAMIC Mon J

[marlonfan]

I'm experiencing this same behavior on a Windows 11 installation. Logseq is version 0.10.7.

[AnweshGangula]

experiencing the same behavior on

• Windows 11 Home Single Language,
• Logseq v0.10.8