unDocUMeantIt

> Yesterday, a client laptop came online and flagged the same error! This is where the real headache begins. The local store of files on the laptop were in error...

> Try this: quit the Seafile client, backup/rename the directory .seafile-data, launch the client and re-sync the library(s). hm, i have three different servers configured and dozens of libraries from...

just for the record: i didn't have an issue with reappearing files. changing the file's name just didn't make the error message go away. the file itself was correctly synced...

> changing the file's name just didn't make the error message go away. i have now upgraded to 8.0.3 but this issue is still not fixed. there is exactly one...

> 3. Implement file names check ONLY in Windows version of daemon/client - I assume the problem is in Windows file system limitations, so why Apple and Linux users should...

here's the content of all PAM files that contain either pam_fscrypt or pam_fprintd, and SDDM: ``` # /etc/pam.d/common-auth auth [success=2 default=ignore] pam_fprintd.so max-tries=1 timeout=10 # debug auth [success=1 default=ignore] pam_unix.so...

no real solution yet. i tried to fix the resulting LaTeX file for a while, to get an idea what `kableExtra` could generate. now i'm not sure this can be...

same here (vidcutter v6.0.0 from ubuntu 18.04 PPA)

i just ran into this as well, trying to verify QR codes i had created myself. they contain PGP signed meta data, and the non-UTF-8 decoding of umlaut characters now...

you're right, i forgot: it's 7.0.6, the version that is shipped with ubuntu 20.04. this report is a summary of an earlier [forum post](https://forum.seafile.com/t/synced-libraries-unavailable-after-changing-server-url/12916).