Bug 97262 - FILEOPEN: Open CSV file from OneDrive for Business-synced folder on Windows creates sync error for lock file
Summary: FILEOPEN: Open CSV file from OneDrive for Business-synced folder on Windows c...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: CSV
  Show dependency treegraph
 
Reported: 2016-01-19 21:56 UTC by Frode Severin Hatlevik
Modified: 2018-03-02 10:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Images depicting the situation on a OneDrive synced folder (448.81 KB, application/x-zip-compressed)
2016-01-19 21:56 UTC, Frode Severin Hatlevik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frode Severin Hatlevik 2016-01-19 21:56:54 UTC
Created attachment 122098 [details]
Images depicting the situation on a OneDrive synced folder

Calc creates a lock-file for CSV files opened. This lock file causes sync error in OneDrive for Business-synced folders. OneDrive for Business complains about unsupported characters in the file name.

The nomenclature for the files is such:
CSV-file: pois_ekstra.csv
Lock file: .~lock.pois_ekstra.csv#

I found this link to a KB discussing invalid characters in filenames in OneDrive
https://support.microsoft.com/en-us/kb/2933738

There seems to be a problem with both the '~' and '#' characters in the lock file filename.

Resolving the issue is not easy. In my case the lock file seems to be a remnant of a stale Calc session, or more likely a remnant of an incident when Calc was runing and I shut down the computer forcefully by holding the Off-button until power off. Also a run-out battery might have caused the file to linger.

In any account the file does not show in the file list in Windows Explorer on Windows 7 with standard settings. I turned on 'Show hidden files, folders and volumes' to make it show up. Most users are oblivious of this setting, and so the error is mysterious, with no way to fix the sync error; OneDrive seems to complaining about an error in a filename of a file which is not present in the filesystem anymore.

I found a work-around: 
By adding a '.tmp' suffix to the filename, the sync error disappeared. This is due to the fact that OneDrive for Business does not even try to sync files with a '.tmp' suffix. I extracted this information from the help info for the sync error (Norwegian only, no URI, sorry): 
Du kan ikke laste opp OneNote-filer eller *TMP- eller *DS_Store-filtyper. Du kan heller ikke laste opp desktop.ini, tomlene.db eller ehthumbs.db.

Hence this nomenclature would work:
CSV-file: pois_ekstra.csv
Lock file: .~lock.pois_ekstra.csv#.tmp
Comment 1 Xisco Faulí 2017-03-08 11:47:31 UTC Comment hidden (obsolete)
Comment 2 QA Administrators 2018-01-29 10:27:16 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-03-02 10:05:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180302