Created attachment 60615 [details]
This is an example file, which opens corectly in LO 126.96.36.199, but is desroyed after saving.
Resaving original RTF file (produced in Word) to RTF format destroys file and causes LibreOffice Writer to crash on opening this file.
[Reproducible] with "LibreOffice 188.8.131.52 (RC1) German UI/Locale [Build-ID: 21cb047-d7e6025-9ba54fc-b4a51a8-f42372b] on German WIN7 Home Premium (64bit)
After save as Example_353.rtf the new document is much smaller (36kB lost), and MS WORD viewer indicates a Table problem in the dew document.
In LibO 333 there was a bug (inherited from OOo) that placed contents "Паллета 1 из 1" 1 cell to the left during fileopen. That problem is fixed, but exactly the cell with "Паллета 1 из 1" seems to be involved into the problem.
May be the roots of the problem are already in FILEOPEN, it seems that LibO has some problems with the RTF code. After having opened the original sample document and clicking alternating into most bottom cells with "Адрес доставки: г. Город, Проспект пр., д. 19е" and "Паллета 1 из 1", I see strange reactions in Navigator, Tables 2 and 3 are interchanging their places for a moment; and I believe there are only 2 tables in the document?
I will split away the FILEOPEN CRASH problem.
Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug.
I created "Bug 49178 - CRASH when FILEOPEN particular RTF" for the fileopen problem
Created attachment 60620 [details]
comparing VIEW in MS WORD VIEWER for original document and after having been saved from LibO
The bug still exists in LO 3.5.3
I am having the same problem! I'm tested v3.5.4, v.3.5.5 and v184.108.40.206rc
On pc Debian x86-64 with 3.5 sources updated yesterday, I don't reproduce the problem.
Aaron/Rainer: could you give a try to 3.5.6 and tell if it's still reproduceable? (in this case, it could be a Windows only bug)
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
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