Bug 103011 - Damaged File saved as .RTF
Summary: Damaged File saved as .RTF
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-05 14:43 UTC by wilburk
Modified: 2017-05-31 10:45 UTC (History)
1 user (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 wilburk 2016-10-05 14:43:14 UTC
i wrote an article with LO 64bit/vs. 5.2.1/german) which contained textpassages and some charts containing figuires and numbers - no graphical parts. 
the file i used was an older text-file i had produced last year with LO - i just changed some text-passages and some of the digits in the charts.   

i saved that as a RTF-file under a new file-name.  

when openimg it some days later it was a mess. some of the numbers had disappeared, others contained strange digits i never had typed. some text-passages had vanished, digits in columns were twisted and torn. 

i think this is an extremely critical bug - in fact there is nothing more severe than finding a partly destroyed file when you want to open/use it again. nobody can trust LO if you never know if you get your correct data again - although  saved in a correctly named file.     

i did not yet try saving that file in another format - .doc or .odt - but in any case this is unbearable!... 
if LO is not capable to control saving simple text-files as .RTF correctly it should not offer that option!!!

sincerely 
wilf burkard, berlin/germany
Comment 1 Xisco Faulí 2016-10-05 14:47:06 UTC
Hi,
Could you please attach the problematic file?
Comment 2 QA Administrators 2017-05-02 11:36:23 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2017-05-31 10:45:42 UTC
Dear Bug Submitter,

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-20170531