Readwise plugin won't write some files with ENAMETOOLONG error

[epicpilgrim]

Hi all

I’ve noticed Readwise is not syncing properly. Obsidian is giving me this error in Inspector:

app.js:1 Error: ENAMETOOLONG: name too long, lstat ‘/home/user1/Documents/User1’s Vault/Reading/Podcasts/Principles for Dealing with the Changing World Order Why Nations Succeed or Fail (Unabridged) - Chapter 1 — the Big Cycle in a Tiny Nutshell.md’
(anonymous) @ app.js:1
plugin:readwise-official:8027 Readwise Official plugin: error writing Reading/Podcasts/Principles for Dealing with the Changing World Order Why Nations Succeed or Fail (Unabridged) - Chapter 1 — the Big Cycle in a Tiny Nutshell–40924449.md: Error: ENAMETOOLONG: name too long, open ‘/home/User1/Documents/User1’s Vault/Reading/Podcasts/Principles for Dealing with the Changing World Order Why Nations Succeed or Fail (Unabridged) - Chapter 1 — the Big Cycle in a Tiny Nutshell.md’

The full path of the file, including folder name and filename, is 197 characters, so should be much shorter than any limits I’m aware of for filenames.

I’ve recently moved to Linux instead of Windows, don’t recall this error in Windows. Is this error an Obsidian error or a Readwise plugin error?

Running Obsidian 1.5.12 (installed with snap on Ubuntu 24.04) and Readwise plugin 2.0.1.

Thanks

[epicpilgrim]

Ok, I have figured out it’s because my home folder is encrypted using ecryptfs, and that means filenames are encrypted. The padding means technically a 143 byte filename turns into 255 bytes. So it’s not an Obsidian issue, but it’s a fun one I have to figure out how to work around, now. Seems like you can create an ecryptfs volume with filename encryption turned off, but you can’t just turn it off on a live volume, so I’m going to have to migrate the entire home folder to a new volume, and/or rebuild the machine with a block form of encryption.