Can't open local graph (no file dialog) 0.6.3 beta Linux Manjaro KDE

[jellespijker]

What happened?

Clicking the Open button right top won't show a file dialog.
Looks like an empty path is the problem. See snippet of system log below

Reproduce the Bug

1. Open fresh logseq install
2. Click the open button top right corner

Expected Behavior

Showing a (native) file dialog allowing me to specify the directory where the graph is

Screenshots

No response

Desktop Platform Information

Operating System: Manjaro Linux
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.15.25-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 19.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

Mobile Platform Information

No response

Additional Context

Log entry obtain with KSystemlog

14-03-2022 07:24	krunner	Error occurred in handler for 'main': Error: path empty
14-03-2022 07:24	krunner	    at /tmp/.mount_Logseqi4jAYN/resources/app/electron.js:13758:267
14-03-2022 07:24	krunner	    at Function.$G__96958__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/tmp/.mount_Logseqi4jAYN/resources/app/electron.js:4046:173)
14-03-2022 07:24	krunner	    at /tmp/.mount_Logseqi4jAYN/resources/app/electron.js:12935:80
14-03-2022 07:24	krunner	    at async node:electron/js2c/browser_init:201:563

[jellespijker]

Tried the workaround suggested in #3202 but that didn't work

GIO_USE_VFS=local Logseq.AppImage

[jellespijker]

Is there a work around for this issue?
Maybe set the default path in the preference.json?

[andelf]

@jellespijker Could you try the .zip format of the Logseq release?

[jellespijker]

Same behaviour in the AppImage and the zip for the nightly 20220316

~/Downloads/Logseq-linux-x64 » ./Logseq
08:17:45.466 › Logseq App(0.6.3) Starting... 
[15571:0317/081745.548859:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Error occurred in handler for 'main': Error: path empty
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:13773:267
    at Function.$G__106151__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:4046:175)
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:12941:80
    at async node:electron/js2c/browser_init:201:563
Error occurred in handler for 'main': Error: path empty
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:13773:267
    at Function.$G__106151__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:4046:175)
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:12941:80
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async node:electron/js2c/browser_init:201:563
Error occurred in handler for 'main': Error: path empty
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:13773:267
    at Function.$G__106151__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:4046:175)
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:12941:80
    at async node:electron/js2c/browser_init:201:563
Error occurred in handler for 'main': Error: path empty
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:13773:267
    at Function.$G__106151__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:4046:175)
    at /home/*****************/Downloads/Logseq-linux-x64/resources/app/electron.js:12941:80
    at async node:electron/js2c/browser_init:201:563

[jellespijker]

Is there a work around for this issue?

[jellespijker]

I could really use some help here, logseq is currently not working for me, since I keep on seeing the demo graph and I want to use a previously stored project.

Which key do I need to set in the configuration text file to point logseq to another default root folder?

I did this workaround ages ago but I recently reinstalled and I forgot how I did it at the time.

[jellespijker]

This seems fixed in version 0.6.7