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
Currently the com.logseq.Logseq Flatpak installs the OG version (0.10.15), but it will probably switch to the DB version in the future, so a separate Flatpak is needed for Logseq OG.
I just asked a related question in the Logseq discussion forums, because I really want to stay on the OG version, but it's also really important to me that I not screw anything up in the transition because of how heavily I currently use Logseq (mardown files only).
A true guide to how to do this safely, not just for Flatpak but on any other platform too (Android would be of particular interest to me), would be so helpful.
For anyone who don't want the existing 0.10.15 to be replaced by the DB version when the flathub manifest changes: flatpak [--user] mask com.logseq.Logseq.
A permanent solution would be for them to actually publish an OG flathub entry, and users uninstall the current com.logseq.Logseq, reinstall with whatever the new package id is. (this should not cause data lose, since all note/graph data is stored on local fs, not within flatpak sandbox)
Activity
auspiciouslink commentedon Apr 30, 2026
I just asked a related question in the Logseq discussion forums, because I really want to stay on the OG version, but it's also really important to me that I not screw anything up in the transition because of how heavily I currently use Logseq (mardown files only).
https://discuss.logseq.com/t/how-to-switch-to-using-the-logseq-og-version-of-the-app/34988
A true guide to how to do this safely, not just for Flatpak but on any other platform too (Android would be of particular interest to me), would be so helpful.
toymil commentedon Sep 6, 2026
For anyone who don't want the existing 0.10.15 to be replaced by the DB version when the flathub manifest changes:
flatpak [--user] mask com.logseq.Logseq.A permanent solution would be for them to actually publish an OG flathub entry, and users uninstall the current
com.logseq.Logseq, reinstall with whatever the new package id is. (this should not cause data lose, since all note/graph data is stored on local fs, not within flatpak sandbox)