Bug 82371 - [UI] (I think). LibreOffice Writer keeps crashing while typing (it's possible when autosaving but I can't tell)
Summary: [UI] (I think). LibreOffice Writer keeps crashing while typing (it's possible...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-08 21:33 UTC by Paul Gunn
Modified: 2016-08-28 10:31 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Gunn 2014-08-08 21:33:24 UTC
When I have more than two documents open, Writer crashes completely, and in auto recovery will usually fail to recover one of the documents with an error report that looks like this:

The file '$(ARG1)' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file.

The corruption could be the result of document manipulation or of structural document damage due to data transmission.

We recommend that you do not trust the content of the repaired document.
Execution of macros is disabled for this document.

Should LibreOffice repair the file?

When I click yes, it invariably fails to recover the document.
Comment 1 Yousuf Philips (jay) (retired) 2014-08-10 04:55:45 UTC
Hello Paul,

Thank you for reporting the bug. If the dialog appears with file '$(ARG1)', this seems like a filename wasnt given to the file. Is this correct?
Comment 2 Paul Gunn 2014-08-13 13:03:00 UTC
Hi Jay,

Yes, but I must admit that I included that message only because it was the
only error message I have received (usually, I work with named documents).
Essentially, the problem is that I'll be editing a document (with two or
three documents open at once), and Writer freezes, with the result that I
have to close it (getting a generic "LibreOffice Writer has stopped
working" message). I then lose whatever wasn't autosaved. This happens on a
daily basis (I am a writer), and it is incredibly frustrating.

Thanks,

Paul.


On 10 August 2014 05:55, <bugzilla-daemon@freedesktop.org> wrote:

>  Jay Philips <philipz85@hotmail.com> changed bug 82371
> <https://bugs.freedesktop.org/show_bug.cgi?id=82371>
>  What Removed Added  Status UNCONFIRMED NEEDINFO  CC
> philipz85@hotmail.com  Ever confirmed   1
>
>  *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=82371#c1> on
> bug 82371 <https://bugs.freedesktop.org/show_bug.cgi?id=82371> from Jay
> Philips <philipz85@hotmail.com> *
>
> Hello Paul,
>
> Thank you for reporting the bug. If the dialog appears with file '$(ARG1)',
> this seems like a filename wasnt given to the file. Is this correct?
>
>  ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 3 Buovjaga 2014-11-26 13:23:10 UTC
Which version of LibreOffice and Windows are you using? Please do not reply to the bug email, but comment on the bug page: https://bugs.freedesktop.org/show_bug.cgi?id=82371
Comment 4 QA Administrators 2015-06-08 14:28:51 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2015-07-18 17:27:27 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO

Message generated on: 2015-07-18