Bug 105243 - FILESAVE Error due to missing lock file
Summary: FILESAVE Error due to missing lock file
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-10 22:09 UTC by henning.buhl
Modified: 2019-06-08 03:04 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
This file causes the error if saving is attempted. (9.86 KB, application/vnd.oasis.opendocument.text)
2017-01-11 16:36 UTC, henning.buhl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description henning.buhl 2017-01-10 22:09:35 UTC
Description:
Error messages appear stating "General Input/Output error" or "couldn't save contets/styles.xml" when I try to save. The lock file goes missing sometimes if I try to save. It does not occure on my slower Laptop (AMD 1.8 GHz processor), only on my desktop PC (Intel 4x4 GHz).
This only happens when I save a file with custom paragraph styles.

Steps to Reproduce:
Save the file with or without any changes made to it.

It can be reproduces, but only on my desktop PC (It's working on my Laptop).

Actual Results:  
The program outputs an error message and the save process was not finished.

Expected Results:
Saving the Document and not tinker with the lick file.


Reproducible: Sometimes

User Profile Reset: Yes. LibreOffice crashed (.exe has stopped working) and in the Just-In-Time Debugger from Visual Studio an Exception was caught with the Message "A heap was corrupted".

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Comment 1 Xisco Faulí 2017-01-11 16:05:45 UTC
Hello,

Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 henning.buhl 2017-01-11 16:36:42 UTC
Created attachment 130319 [details]
This file causes the error if saving is attempted.
Comment 3 Xisco Faulí 2017-01-11 20:10:46 UTC
Hello ,

Thank you for reporting the bug.

I can't reproduce it in

Version: 5.4.0.0.alpha0+
Build ID: db4badfc971b9cc60809c3408f579bae04a77c34
CPU Threads: 1; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-01-10_23:25:07
Locale: es-ES (es_ES); Calc: group

Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 4 henning.buhl 2017-01-11 21:38:23 UTC
I tried the versions 5.2.4 and 5.3.0.1
The error still persists.

I recorded a video with the bug occurring in it.

https://www.youtube.com/watch?v=uCERDFwZX-k&feature=youtu.be

As you can see the lock file goes missing.
Comment 5 Buovjaga 2017-01-13 19:29:25 UTC
(In reply to henning.buhl from comment #4)
> I tried the versions 5.2.4 and 5.3.0.1
> The error still persists.
> 
> I recorded a video with the bug occurring in it.
> 
> https://www.youtube.com/watch?v=uCERDFwZX-k&feature=youtu.be
> 
> As you can see the lock file goes missing.

Well, here we see the very important detail that you are using Dropbox.. Maybe this could be closed as a duplicate of bug 103506?

Henning: what do you think?
Comment 6 henning.buhl 2017-01-13 20:37:29 UTC
I tested it in other locations. I think that would be obvious.

Dropbox does not influence the w10 filesystem.

https://www.youtube.com/watch?v=S8BkP83CqYc&feature=youtu.be
Comment 7 Dieter 2018-06-24 20:06:55 UTC
Henning, is this bug still reproducible for you with an actual version of LO?
Comment 8 hasan md mahamudul 2018-06-26 07:27:58 UTC Comment hidden (spam)
Comment 9 Dieter 2018-06-26 07:36:36 UTC Comment hidden (obsolete)
Comment 10 Akshya Kumar 2018-06-26 07:44:26 UTC Comment hidden (obsolete)
Comment 11 Xisco Faulí 2018-10-18 15:01:27 UTC
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 12 QA Administrators 2019-05-08 17:30:20 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2019-06-08 03:04:05 UTC
Dear henning.buhl,

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-FollowUp