https://bugs.kde.org/show_bug.cgi?id=384903
--- Comment #20 from Jack <ostrof...@users.sourceforge.net> --- I think it is clearly a problem with gdrive, probably some interaction with how KMM actually saves a new version of the file. The developers may correct me, but I believe it actually saves the new file with a temporary name, and then, once it is fully written and closed, it renames it. I think with normal files (at least on Windows and Linux) that rename operation replaces the original file with the same name - perhaps gdrive doesn't work like a local hard drive - either because of something Google does intentionally, or perhaps it's a subtle timing issue related to Google syncing the local file with the online version. Perhaps you can try "Save as" instead of save, but using the same name - just to see if it behaves any differently. Another test - save to a new name on gdrive. If that always works, then there is some issue with the specific details of how KMM saves the file. -- You are receiving this mail because: You are the assignee for the bug.
