I'm using Linux, and error happens when I try to log into Logseq Sync

Junyi_Du · December 19, 2022, 5:34am

You might see the url redirection throws error after typing your username and password then click the Login button, like:

If you are using Linux, you may have to execute
xdg-mime default Logseq.desktop x-scheme-handler/logseq
to map the application with the MIME type.

Sorry for the inconvenience. We will have a in-app Login UX very soon.

Reference:

github.com/logseq/logseq

Fix: Appimage desktop file entries

logseq:master ← logseq:fix/appimage

opened 12:41PM - 04 Nov 22 UTC

sprocketc

+6 -2

This PR adds some missing entries to the produced `Logseq.desktop` file, require…d to register a mimeType that handles logseq urls. [Desktop entry specification](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html) Fork diff of electron-forge-maker-appimage https://github.com/trusktr/electron-forge-maker-appimage/compare/master...logseq:electron-forge-maker-appimage:master - [x] Add `%u` to `Exec` in order to pass the URL as a single parameter - [x] Add `mimeType` to `forge.config.js` - [x] Set product name to partially handle https://github.com/logseq/logseq/issues/3432. The app can now be properly pinned and it won't spawn a separate icon on launch. We now have to find a way to fix the icon image. The produced `Logseq.desktop` should look like this ``` [Desktop Entry] Name=Logseq Exec=Logseq %u Terminal=false Type=Application Icon=Logseq StartupWMClass=Logseq X-AppImage-Version=0.8.10 Comment=A privacy-first, open-source platform for knowledge management and collaboration. MimeType=x-scheme-handler/logseq Categories=Utility ``` The contents of the appimage can be extracted for inspection by running `./Logseq-linux-x64-0.8.10.AppImage --appimage-extract` Users might still have to execute `xdg-mime default Logseq.desktop x-scheme-handler/logseq` to map the application with the MIME type. Related to https://github.com/logseq/logseq/issues/7203 https://github.com/logseq/logseq/issues/7202 https://github.com/logseq/logseq/issues/4984 https://github.com/logseq/logseq/issues/2631 https://github.com/logseq/logseq/issues/3432

bagelbyte · December 30, 2022, 4:51pm

hey there, so apparently AppImages for electron apps using the electron-builder used to have a option where you could make the AppImage install its assets to the system, which would handle creating the desktop file, which is needed to handle the mime associations for the link that the login button tries to open. however, this option has been deprecated, and now you need to use the AppImageLauncher to handle this. basically just install AppImageLauncher from the logseq releases page via a deb or rpm or whatever, and then when you download the logseq appimage and attempt to run it, you will get prompted to install the appimage to your system. after you do this, everything should work fine

Zhiyuan_Chen · January 12, 2023, 11:49am

this workaround should work after this pr is merged: feat: export login-callback fn by RCmerci · Pull Request #8326 · logseq/logseq · GitHub
also post the steps here:

For Firefox users to find out the code:

For how to open Devtool (on browser & in app)

Elessar · February 22, 2023, 11:57am

This is not working for me on 0.8.17 in with #8326 had been merged. Clicking Login button in Logseq, and logging in does bring me back to Logseq now, but the login to setup sync does not continue.
The dev console code also does not work…

frontend.handler.user.login_callback("f7de0d41-0003-4446-99bc-24342594e8d7")
VM162:1 Uncaught ReferenceError: frontend is not defined
    at <anonymous>:1:1
(anonymous) @ VM162:1

Junyi_Du · February 22, 2023, 12:09pm

It’s working on my side (0.8.17 release build, using a fake token)

Be ware, execute the code on the Devtool of Logseq INSTEAD OF the browser’s

frontend.handler.user.login_callback(<PASTE YOUR TOKEN HERE>)