Created attachment 46663 [details] new_merged_cells.odt Downstream bug may be found at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/132916 OOo bug may be found at: http://openoffice.org/bugzilla/show_bug.cgi?id=26964 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy unoconv unoconv: Installed: 0.3-6 Candidate: 0.3-6 Version table: *** 0.3-6 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && unoconv --listener && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/132916/+attachment/132337/+files/new_merged_cells.odt && unoconv -f rtf new_merged_cells.odt && lowriter -nologo new_merged_cells.rtf new_merged_cells.odt the .rtf document looks the same as the .odt. 4) What happens instead is it does not.
I confirm the problem with LO 3.5.0 beta-1 under Ubuntu 10.04 x86_64 (LibreOffice 3.5.0beta1+ Build ID: 6e7299d-7f15fca-8eae9f1-ca8e46d-5bcbce4) Steps to reproduce: 1/ open the bugdoc 2/ save as RTF file and close the document 3/ reopen the RTF file The table is broken. Miklos: feel free to reassign if you can't handle this bug. Best regards. JBF
This is an export problem, the created RTF doesn't contain the table cell strings, at all.
Hm, and seems to affect DOCX export as well, so probably a bug in MSWordExportBase.
So the major problem was that with the sample document only the first cell of the whole table was exported at all, this is now fixed with http://cgit.freedesktop.org/libreoffice/core/commit/?id=83fbebfea32b27cd722466607aa978244ac53575 on master, also cherry-picked to -3-5: http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-5&id=99fccadd08d41e8a4abcc062d075886d4a0910be The export result should be now on par with the DOC export, though still not perfect. If you want that improved, please file a separate bug for the DOC exporter (on which the RTF export is based).
Tested in LO 3.5.1, LO 3.5.2 rc0+ and master : probable memory leak (up to 2 Go RAM allocated by LO and very, very, very (I am not patient enough to wait the end) long time to save the file in RTF format. Reopening the bug. Best regards. JBF
(In reply to comment #5) > Tested in LO 3.5.1, LO 3.5.2 rc0+ and master : probable memory leak (up to 2 Go > RAM allocated by LO and very, very, very (I am not patient enough to wait the > end) long time to save the file in RTF format. > Reopening the bug. > > Best regards. JBF Or infinite loop ? No problem when saving as MSWord97 format (unless merged cells are not merged anymore). Export as docx works but the result is incorrect (but that's probably another story). Best regards. JBF
I just tried to reproduce this again, the file save takes about 1-2 seconds here, so closing again. Regarding correctness, please follow the advice in comment 4, that should not be handled here. Thanks! :-)
Miklos Vajna, thank you for working on this. Unfortunately, the bug noted in the Description https://bugs.freedesktop.org/show_bug.cgi?id=37161#c0 is still not addressed: lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:4.1.3-0ubuntu2 Candidate: 1:4.1.3-0ubuntu2 Version table: *** 1:4.1.3-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status If you found the issue noted in the Description to be resolved, could you please post what version of LibreOffice this is fixed in, as well as a screenshot of both the .odt and .rtf proving this? Thank you for your understanding.
I am closing this as FIXED once again @Christopher - if you're seeing a similar problem please report a new bug.
Still reproducible in MASTER, and: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:4.2.6.3-0ubuntu1 Candidate: 1:4.2.6.3-0ubuntu1 Version table: *** 1:4.2.6.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Joel Madero, and anyone else who wants to toggle the bug report Status, let me be crystal clear here, I'm not going to file an additional, frivolous bug report as the original bug reported is still reproducible verbatim as per the Description -> https://bugs.freedesktop.org/show_bug.cgi?id=37161#c0 . Please review it in full so you understand the scope of this report. With this in mind, this report never was, isn't now, and never will be RESOLVED FIXED until a commit for the bug noted in the Description is released, and in turn, verified by me, the original reporter. It is not fixed when a commit partially fixes, fixes something not related, or anything but fully fixes the issue as previously advised to you. If your bug triage strategy is to close valid, and still reproducible LibreOffice bug reports when it is clearly not fixed, it would be best if you would cease toggling bug reports altogether. Despite this, please do not toggle the status of this bug report further unless I have advised it's fixed. Thank you for your understanding.
(In reply to Christopher M. Penalver from comment #10) > Thank you for your understanding. So ! When Miklos writes: " The export result should be now on par with the DOC export, though still not perfect. If you want that improved, please file a separate bug for the DOC exporter (on which the RTF export is based). " that explains the logic how this works. This issue 37161 then should have a dependency on the new bug.
Please stop messing with the settings if you don't know what you're doing. This bug has to be confirmed by an INDEPENDENT QA TEAM MEMBER. Reopened has a specific meaning and this doesn't meet that. Don't change it again.
Created attachment 108903 [details] deocument containing four screenshots, confirming the bug Hi! Managing bugs is important, but testing too! I confirm and set to new
new.. Hi Miklos, Since the export to doc is fine, I think currently the result in rtf does not depend on that? Docx-export is broken too, but different. Pls see my export result with the previous comment. What would be your advise? thanks, Cor
FYI: just to be sure, I tested the same document with an empty paragraph first, before the table. Results the same.
Reproducible with LO 4.4.1.2, Win 8.1 Table is almost fully broken (also compared to MSO).
I test the issue with LibreOffice 5.0.0.0.alpha1+ Build ID: bcbf45d9f94d177c6841ccede3ff0ba69c4f22b1 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-05-04_03:51:16 The file exported to docx is represented correctly in LibreOffice, but it can not be opened with MS Word Viewer under wine. The rtf export is partially fixed with bug 80708, but the cells are still unmerged.
Migrating Whiteboard tags to Keywords: (filter:docx filter:rtf) [NinjaEdit]
Reset Assignee to default till I actually start looking into this.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Attention! In LO 6.1.1.1 export from attached file to RTF gives empty RTF document! RTF doc doesn't have any table... bug still repro and it has become more bad
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Same observation as in comment #2: no table at all in the exported RTF file. Tested in LO 6.3.3.0+ Best regards. JBF
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No problem anymore when exporting with LO 7.2. Closing as WorksForMe. Best regards. JBF
Created attachment 174958 [details] RTF file exported by LO 7.2