Bug 121729 - Crashes almost every time I open libre office and Important work lost constantly
Summary: Crashes almost every time I open libre office and Important work lost constantly
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All Android
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-27 04:09 UTC by jacquelyn.routledge
Modified: 2019-06-27 02:54 UTC (History)
3 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 jacquelyn.routledge 2018-11-27 04:09:53 UTC
Description:
When I open libre office almost every time it tells me "Libre Office has crashed" and when it asked me to select files to recover half of the text is missing even though I saved it before I closed Libre Office. I am very upset as now I am going to have to rewrite a lot of important text that I may not be able to write again. I will be switching to another program. Please fix this so it does not happen to somebody else. 

Steps to Reproduce:
1.Open Libre Office, Libre Office Crashes
2. Select File to recover
3. Open file

Actual Results:
File did not save, half of content lost. 

Expected Results:
The information on a file to save when I save it! For nothing to have changed after I close the program!


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
If there is any way to restore the lost text please contact me. I am working on a project and it would be extremely helpful. I think the idea of this program is fantastic but if it cannot refrain from crashing every time I open it I am not going to use it anymore.
Comment 1 Joel Madero 2018-11-27 06:35:59 UTC
This is not a valid bug report so I am closing it as INVALID. The reason being that there is no set of reproducible steps, no clear information, really nothing to confirm a bug at all.

@Jacquelyn - if you need help figuring out how to properly report a bug, please jump in the chat and ask: https://irc.documentfoundation.org/?settings=#libreoffice-qa

Please do not reopen this bug as it stands because it'll just be closed again as INVALID. For examples of correct bug reports see: https://wiki.documentfoundation.org/QA/BugReport#Good_Reports

For general questions please go to: ask.libreoffice.org
Comment 2 Xisco Faulí 2018-11-27 10:18:41 UTC
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 3 Buovjaga 2018-11-27 10:46:05 UTC
Jacquelyn: you selected Android as the operating system. Was this a mistake?
Comment 4 QA Administrators 2019-05-27 02:46:04 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-06-27 02:54:51 UTC
Dear jacquelyn.routledge,

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