Bug 92711 - Autosave blocks all uses for new, but unsaved files
Summary: Autosave blocks all uses for new, but unsaved files
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: All All
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-13 18:03 UTC by Balaco
Modified: 2015-07-15 15:12 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 Balaco 2015-07-13 18:03:34 UTC
Configure LibreOffice to autosave every 2 minutes (or less, if you don't want to wait as much to reproduce this like it happened to me now). I did:

Window:

Tools->Options --> Load/Save->General

Check the options as showed:

[V] Save autorc. every 2 minutes
  [V] Auto save documento too
[ ] Edit doc. properties before saving
[ ] Always create backup
[V] Save URLs relat. to f.s.
[V] Save URLs relat. to Internet

Open any existing .odt document. Open a new window with a new document (or just do CTRL+N, if you prefer). Start writing the document, but DO NOT save it yet.

After the 2 minutes time expires, the program will quickly show that progress bar on its "status" line (lower window part), that it always shows before saving, and will start flickering, repetitively and quickly. You cannot edit the document anymore, neither save it (menus don't open, as most thing are unresponsive). I can't figure out what I should/could do!

This will usually result in the loss of many unsaved works, depending on how much time the person had it configured to autosave (it happened to me at least 3 times in the last two weeks...).

If you cannot reproduce it with the steps I gave, I'll try it again. If there are other configurations that should affect this behaviour, please tell me and I'll check and add them to this report.

Thank you
Comment 1 Maxim Monastirsky 2015-07-13 18:17:36 UTC
Hi,

(In reply to Balaco from comment #0)
> I can't figure out what I should/could do!
The first thing I would do is to upgrade to a newer version. 4.1.6 is old and unsupported for a very long time now, and it's known to have a bug similar to what you're describing here. So please retest with a newer version, and report back whether it solves the bug for you. Thanks.
Comment 2 Balaco 2015-07-13 18:54:26 UTC
Really? I'm using Fedora, and they (people who takes cares of some computers I use) updated LibreOffice today. And it was just 4.1.2  before this update.

I'll see what I can do to update and retest this with a newer LO version, but it may not be possible (I don't choose the Fedora version I use here, for example).

Just with the current version of L.O. the bug reports can be accepted?
Comment 3 Maxim Monastirsky 2015-07-13 19:00:45 UTC
(In reply to Balaco from comment #2)
> Just with the current version of L.O. the bug reports can be accepted?
Currently bug reports are accepted only for 4.4/5.0/master (and also 4.3 for Mac users downloading from the App Store).
Comment 4 m_a_riosv 2015-07-13 22:10:05 UTC

*** This bug has been marked as a duplicate of bug 71625 ***
Comment 5 Balaco 2015-07-15 14:34:33 UTC
I use the latest available version from Fedora repositories. I updated it yesterday, before reporting the bug.

This machine (and several others my coleagues use) is not allowed to install/reinstall versions, separated from other.

However, looking at bug 71625 Maxim pointed at, I have seen that:

- the report of #71625 was not (initially, at least) clear, with steps to reproduce the problem; I tried to make a report with this quality, and I can improve it if you think it should

- the major version I use is the same, so bug reports should be accepted; office programs are thing that should not be expected to be updated with much frequency

- this bug (and at least a couple of the other duplicates) are marked as solved, but I can't find an impossible information: what is the first version of LO that this bug was fixed? We need this information because for the infrastructure I use here, it is not always feasible to update it to the newest available version. It could imply in updating many other programs and things. Can you tell me? Reading a few other "dup" bugs I could not find the "root bug" (i.e., the only one not considered a duplicate of any others, for this problem)
Comment 6 Balaco 2015-07-15 14:36:13 UTC
(In reply to Balaco from comment #5)
> I use the latest available version from Fedora repositories. I updated it
> yesterday, before reporting the bug.
> 

Id est, the Fedora repositories my machine uses, and has access to. Even if it is not necessarily the lastest release of Fedora. However it is, I cannot change this fact.
Comment 7 Maxim Monastirsky 2015-07-15 15:12:58 UTC
(In reply to Balaco from comment #5)
> looking at bug 71625 Maxim pointed at
Well, that was not me but m.a.riosv, although I do agree that it's probably the same bug.

> - the report of #71625 was not (initially, at least) clear, with steps to
> reproduce the problem; I tried to make a report with this quality, and I can
> improve it if you think it should
Your effort to make good bug reports is much appreciated, and I wish everyone will follow you, but that doesn't matter anymore after the bug was identified as already fixed (given that it's indeed the same bug, and that it's indeed fixed in later versions).

> - the major version I use is the same, so bug reports should be accepted;
> office programs are thing that should not be expected to be updated with
> much frequency
The Document Foundation (in whose BugZilla we're talking right now) has a clear release schedule of monthly releases, whether you like it or not:

https://wiki.documentfoundation.org/ReleasePlan

It clearly states what versions are EOL, thus unsupported anymore by TDF.

Of course, downstream users such as Linux distros, are free to not follow this schedule, but then it's solely their responsibility to fix bugs in the software they're shipping. If your distro version is still supported, you should ask the distro maintainers for support, not the TDF.

> - this bug (and at least a couple of the other duplicates) are marked as
> solved, but I can't find an impossible information: what is the first
> version of LO that this bug was fixed?
There is a field named "Whiteboard", where these versions are listed.