Bug 139955 - ERROR SAVING FILE, APP CRASHED, RECOVERY FAILED, END-UP CORRUPTED THE FILES !!!!!!
Summary: ERROR SAVING FILE, APP CRASHED, RECOVERY FAILED, END-UP CORRUPTED THE FILES !...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-28 02:02 UTC by kunj
Modified: 2021-08-29 04:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kunj 2021-01-28 02:02:36 UTC
Description:
After upgrade the version in 2020 somewhere in June (after years use of an old version), file cannot save. It says "Locking Problem, Sharing Violation". Opening several files, in the middle of editing in 1 file suddenly app crash shutting down all opened files. Re-launch being prompted with recovery files. Recovery unsuccessful. Repeated many times with failure. End up. Files corrupted. Today 28th Jan 2021 i installed new. Same happened. No improvement. WTF of upgrade.
Things are stable & in order before I upgrade to new version available in June 2020. The old version is stable enough without any problem or hint of upgrade needed. I just want to upgrade to have maybe some new features or improvements offer within the new version.


Steps to Reproduce:
1.Open any file Calc
2.Edit anything
3.Try click save

Actual Results:
Error Saving File. Locking problem.

Expected Results:
Save normally like other apps. Save as it is intended to do.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.4.2 (x64)
Build ID: dcf040e67528d9187c66b2379df5ea4407429775
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Version: 7.0.4.2 (x64)
Build ID: dcf040e67528d9187c66b2379df5ea4407429775
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 1 kunj 2021-01-28 02:13:45 UTC
now have the new error message says :
The lock file could not be created for exclusive access by LibreOffice, due to missing permission to create a lock file on that file location or lack of free disc space.
Got 2 options to select either Open Read-Only or Cancel.
after that prompt, the saving error message follows.
Comment 2 BogdanB 2021-01-28 05:07:47 UTC
It seems LibreOffice didn't installed correct. It doesn't have permission to save anywhere on disk.
Please try to install again.
Comment 3 Julien Nabet 2021-01-29 16:49:31 UTC
After having applied what BogdanB, you can give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?
Comment 4 m_a_riosv 2021-01-29 18:51:48 UTC
Please test with a clean profile Menu/Help/Restart in Safe Mode
Comment 5 QA Administrators 2021-07-29 04:31:13 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-08-29 04:09:17 UTC
Dear kunj,

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