My Logseq (0.10.15, ubuntu 25.04) install has stopped auto-closing brackets and graves, eg before i could be typing and just do a [[ then type the search term i want to find or create a page to link. Now, nothing happens, it just puts [[ on the page. The same goes for code blocks, typing ` used to complete, now it does nothing.
I saw some posts requesting that this be disable-able, maybe its been disabled somehow and i need to re-enable? Is there some keyboard shortcut that I’ve accidentally hit that disables all completions for me?
Any help gratefully accepted!
edit: things ive tried, none have worked:
clear cache
start a new graph
nuke everything and fully reinstall (delete .locseq, all notebook directories, everything)
It looks like its a wayland thing, running logseq --ozone-platform=x11 gets it working again. Wierdly, it works fine on another laptop with identical config but no nvidia driver - poss its some side effect of the nvidia/wayland combo.
have the same issue here with normal intel meteor lake. IMHO this is directly related to X11 and the way the completion is implemented. Additionally, the autosearch function doesn’t work either when starting to type after [[]].
I confirm that setting --ozone-platform=x11 fixes the issue by using Xwayland. It takes longer on startup though.
To be complete: If one uses the Logseq flatpak with wayland under KDE Plasma, go to Application permissions in the settings app, go to logseq, click on flatpak settings and activate “advanced”. There you can set the session type at the bottom. Note that by default access to session bus and system bus are disabled. You need to enable that for the application to start. Setting flatpak to Wayland windowing system and XDG_SESSION_TYPE to wayland removes the autocompletion. Setting it to x11 windowing system and XDG_SESSION_TYPE to x11, completion works