Desktop sync no longer working, still working on android

Questions & Help
1

Hi, I’m having an issue with logseq syncing, it was working before on both my windows pc and android clients, but the past few days it’s only been working on my android. My pc client just shows this symbol. anyone know how to fix it?

image

2

I am having the exact same issue. It was working just fine last night. This morning, I have that same icon.

I tried closing and opening Logseq several times. I tried turning sync off/on again. Restarting the computer. Logging out and back in. Nothing works and I am at the point where I am considering uninstalling Logseq and reinstalling.

3

The same problem here. The symbol turns yellow in stages and then changes back to the crossed-out cloud. Worked about year before. Both Android devices are synced correctly and show the cloud icon with the green dot.

Desktop System

  • Linux Mint 22 Cinnamon (6.2.9)
  • Kernel 6.8.0-56-generic
  • Logseq 0.10.9

Android System

  • Pixel 7 & Pixel Tablet
  • Both Graphene OS
  • Logseq 0.10.10

What I tried on Desktop

  • Restarted Logseq
  • Logged into another graph an back
  • Restarted OS
  • Refresh of graph
  • Re-Index
  • Cleared Cache and added graph again

In addition, when I’m surfing in the settings it quits suddenly.

Did anyone solved the sync issue and how?

Thank you in advance. All the best,

Oliver

4

Problem solved!

After the new installation (flatpack), I started Logseq via the terminal. I noticed an error message that a filename was too long.

12:37:10.572 › fetch remote files error: Io(Os { code: 36, kind: InvalidFilename, message: ‘The file name is too long’ })
Error occurred in handler for ‘main’: [Error: io: The filename is too long (os error 36)] {
code: ‘GenericFailure’
}

In my case, I had added an zotero entry with a very long title (225 characters!) using /zotero on Android, which was created as a page. Since deleting the corresponding file (page) via Android, the desktop sync is working properly again.

My takeaway:

  • In case of a problem → run logseq in the terminal and check the output for errors.
  • Avoid long file names

Cheers,
Oliver

1 Like
5

Are you guys using Syncthing or the logSeq sync?

6

Hi nerdPoint,
we are using the official Logseq Sync. Afaik we do not have the cloud symbol with other solutions.
Cheers, Oliver

7

I have the same problem, however, my problem is with Android and not Windows.

Windows it works fine, android it just crashes on open.