Bug 39536

Summary: autodeleted .~lock.xxxx.ods# on first update and cannot save the file
Product: LibreOffice Reporter: PINEDEV <pinedev>
Component: LibreofficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID QA Contact:
Severity: major    
Priority: medium CC: LibreOffice
Version: 3.3.3 release   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: New empty calc file with another one c:\Users\Seven\Documents\.~lock.Test.ods#

Description PINEDEV 2011-07-26 00:23:31 UTC
Created attachment 49552 [details]
New empty calc file with another one c:\Users\Seven\Documents\.~lock.Test.ods#

OS Windows 7 Home Premium 32 bit
HD NTFS system
MS Security Essentials
MS Office 2007

LibreOffice 3.3.3 
OOO330m19 (Build:301)
tag libreoffice-3.3.3.1

I've worked with openoffice and LibreOffice from their first versions (include OS W-XP SP2) and this problem appeared with the LO version versions 3.1 - 3.2 & 3.3 on Windows 7 - NTFS HD system

I am ussualy working with calc (ods files) and do not know if it happens the same issue with other modules.

when I create a new file or open an existent one with Calc, it appears an hide file  .~lock.xxxx.ods#. This file appear on most of folders ( includding MyDocuments [ c:\Users\Seven\Documents\ ] but not on Desktop folder!

 On my first change (update) into the working file, this file (  .~lock.xxxx.ods# ) disappears and I cannot save or "save as" the  working file. I intented to make an backup of the .ods# file and to ad it when it happens but without any solution. 

I reinstall many times ( after deleting the temp files with CCleaner and cleaning the register ) but without any changes...

Thank you



Thank you
Comment 1 Rainer Bielefeld Retired 2011-07-26 04:06:53 UTC
NOT reproducible with "LibreOffice 3.4.1 RC2 - WIN7  Home Premium (64bit) German UI [OOO340m1 (Build:202)]", but I doubt that I understood the problem.

I created a new document on desktop, typed an "x" into 'A1', closed and saved the document, everything worked fine.

@reporter:
I recommend to discuss that problem on a user mailing list.
May I ask you to read  hints on <http://wiki.documentfoundation.org/BugReport> carefully?
Then please:
- Write a meaningful Summary
- Attach a sample document (not only screenshot)
- Attach screenshots with comments (you can add information using LibO DRAW
  and then attach your screenshot with comments as PDF) if necessary
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem. Start before you open LibO, avoid 
  any speculations what the reasons for the problem might be, only tell 
  your steps and observations
- add information 
  -- what exactly is unexpected
  -- and why do you believe it's unexpected
  -- concerning your PC 
  -- concerning your OS Version, Localization
  -- concerning your LibO localization (UI language)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration ...)
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an OOo Issue that might be useful
  -- everything else crossing your mind after you read a.m. URL
Can you please file Bug reports with status UNCONFIRMED if your are not absolutely sure that you contributed all required background information and that the problem will be reproducible with information you can provide? 
Thank you!
Comment 2 Björn Michaelsen 2011-12-23 12:26:52 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 Björn Michaelsen 2011-12-23 17:01:50 UTC
needinfo keyword redundant by needinfo status.
Comment 4 Florian Reisinger 2012-08-14 14:02:15 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:03:15 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:07:48 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:09:55 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.