You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to use LogSeq (via the flatpak) it launches fine, but when I go to select a folder to create a graph, nothing happens except this error in the log:
00:48:13.648 › :electron.handler/open-dir open folder selection dialog
00:48:13.672 › :electron.handler/open-dir {:path nil}
Error occurred in handler for 'main': Error: path empty
at /app/logseq/resources/app/electron.js:15353:71
at /app/logseq/resources/app/electron.js:15355:10
at Function.$G__109900__1$$ [as $cljs$core$IFn$_invoke$arity$1$] (/app/logseq/resources/app/electron.js:4104:175)
at /app/logseq/resources/app/electron.js:13064:80
Reproduce the Bug
Open logseq in sway on void linux
Try to open a file picker dialogue
Expected Behavior
It should work just like it does in Firefox, Zenity, Krita, and every other application on my system.
Screenshots
No response
Desktop or Mobile Platform Information
uname -a: Linux rectangle 6.6.38_1 #1 SMP PREEMPT_DYNAMIC Tue Jul 9 19:40:21 UTC 2024 x86_64 GNU/Linux
logseq: 0.10.9
Additional Context
It might be an issue with my setup, but the fact that it works in every other application is frustrating to me and it makes me think it may be an issue with either logseq or electron.
Are you willing to submit a PR? If you know how to fix the bug.
I'm willing to submit a PR (Thank you!)
The text was updated successfully, but these errors were encountered:
Search first
What Happened?
When I try to use LogSeq (via the flatpak) it launches fine, but when I go to select a folder to create a graph, nothing happens except this error in the log:
Reproduce the Bug
Expected Behavior
It should work just like it does in Firefox, Zenity, Krita, and every other application on my system.
Screenshots
No response
Desktop or Mobile Platform Information
uname -a
:Linux rectangle 6.6.38_1 #1 SMP PREEMPT_DYNAMIC Tue Jul 9 19:40:21 UTC 2024 x86_64 GNU/Linux
logseq
:0.10.9
Additional Context
It might be an issue with my setup, but the fact that it works in every other application is frustrating to me and it makes me think it may be an issue with either logseq or electron.
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: