Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overwritten and modified ODS files not synced #182

Open
BBBalls opened this issue Dec 23, 2023 · 2 comments
Open

Overwritten and modified ODS files not synced #182

BBBalls opened this issue Dec 23, 2023 · 2 comments

Comments

@BBBalls
Copy link

BBBalls commented Dec 23, 2023

When an LibreOffice Calc ODS file in the local sync folder is overwritten, an directory not found error is produced, and the overwriting ODS file is not synced to Proton Drive.

When an ODS file in the local sync folder is edited, an directory not found error is produced, and the modified ODS file version is not synced to Proton Drive.

For the syncing of newer versions of ODS files with the same file name to occur, the original ODS file has to be deleted from Proton Drive.

@hwittenborn
Copy link
Owner

Hey @BBBalls! Are you still encountering this issue? I'm not entirely sure what might be causing it, there shouldn't be something specific to ODS files that'd be causing an issue. Do you experience the same behavior with other file types?

@BBBalls
Copy link
Author

BBBalls commented Dec 28, 2023

Yes, other file types seem to be affected. A test with a markdown file resulted in the same kind of error after editing it. The markdown file was synced from Proton Drive to the local folder, but after editing the file directory not found error was given, and the edited file was not synced with Proton Drive. The sync of the edited file only after the original file is deleted in Proton Drive.

This same phenomenon is occurring with the .sync-exclude.lst file as well. I just switched distro, so generated a new local sync folder. The unmodified .sync-exclude.lst file, as in blank, that is in the Proton Drive is in conflict with the newly generated and blank local .sync-exclude.lst file, giving the directory not found error.

My previous report was from Pop!_OS 22.04 using the Celeste Flatpak. The behavior was reproduced on Arch Linux using the Celeste Flatpak.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants