Bug 80454 - Writers autosave repeatedly every second
Summary: Writers autosave repeatedly every second
Status: RESOLVED DUPLICATE of bug 71625
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-24 02:37 UTC by tzou.fleir
Modified: 2014-06-24 11:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tzou.fleir 2014-06-24 02:37:16 UTC 
OS: win 8 64bit
platform: Intel x86
situation: 
1. I have set recovery and autosave loop at 3 mins.  
2. When using writer, sometimes the file will start autosave every second, which literally put the software out of function.  
3. I have to move the mouse cursor to tool, keep clicking it until it had the chance to show the menu, then choose "option", then go to the "saving" setting to set the autosave loop at a different minute, and click "ok", back to the editing file and the 1-second autosave loop will stop.  
4. This happens almost every 10 mins. which is really disturbing.
Comment 1 ign_christian 2014-06-24 03:12:41 UTC 
Hi.. Your description is too general.. No exact procedure to reproduce the problem?

Please observe previously reported bugs: https://bugs.freedesktop.org/buglist.cgi?list_id=437386&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDINFO&longdesc=autosave&longdesc_type=allwordssubstr&product=LibreOffice

Perhaps you have same situation with one of the bugs?
Comment 2 tommy27 2014-06-24 05:14:58 UTC 
also consider upgrading to LibO 4.2.5.2
the 4.1.x branch you are using is END-OF-LIFE and will receive no more updates.
Comment 3 Yousuf Philips (jay) (retired) 2014-06-24 11:09:22 UTC 

*** This bug has been marked as a duplicate of bug 71625 ***