Created attachment 63901 [details] switch beetween Print and Web Layout to see bug I dont know if this is related to #35449, but looks similar. System is Ubuntu 11.10 LibreOffice 3.5.4.2 release Attachment was originally Word .doc and converted to .odt Table of contents doesnt show entirelly. Corresponding pages neither. Switch to "Web Layout" and full pages are visible. +++ This bug was initially created as a clone of Bug #35449 +++ Hello, first I know that tables are not thought to be used in writer this way. But it's possible to do so and also hints at the internet recommend to use large tables to get independent columns for your document. The attachment contains a file consisting one table with just one line and two columns. This table goes over many pages and footnotes are set. Since this table got longer and longer problems appeared at page break. The Document is fine at "Web Layout", but gets problems at "Print Layout". Appearance: At "Print Layout" it seems that text is cut of at end of random pages, also the number of Page Count is less than it should be. Pressing Ctrl + A you see that the text get marked and the marking runs out of page. This also causes high CPU-usage, and even can freezes the window. Switching to "Web Layout" brings the whole written text back and everything works fine. If the problem not totally accrues after opening the document, it will accrue after switching from "Web Layout" to "Print Layout" (watch Page Count!). Systems: This behaviour was tested on Windows XP and Ubuntu-Linux (10.04 32bit and 10.10 64bit),with LibreOffice 3.3.1 and OpenOffice 3.2.1 as well. My opinion: This problem causes big confusion by users, even because it appears different at PCs with more or less power. If it should be impossible to implement a good working "Page Layout" with large tables, there might be at least a warning that tells the user that there will be problems. It could hint him to "Web Layout" or to different possibility’s like using boxes or marginalia, if this is adequate to his goal. I hope you see what I mean, if there are any questions I'm willing to help.
bug existed before .doc was converted to .odt
Hi thanks for your report. It is indeed related to the table. So good to keep issue 35449 in mind too. When you put the cursor in the table#36, and choose Table > Convert > To text, the TOC shows fully, also in print layout.
And I set the version on 3.3.0. But I guess if you try OOo 1.1.5 or 2.1, you'll have the same problem
** 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 (4.3.5 or later): 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) Thank you for your help! -- The LibreOffice QA Team
Can't test in 4.4.0 due to https://bugs.freedesktop.org/show_bug.cgi?id=86208 and https://bugs.freedesktop.org/show_bug.cgi?id=87663 Confirmed in 4.2.8
** 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.0.4 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
This bug is still present in: Version: 5.3.0.0.alpha0+ Build ID: a8bd44573b75d1399257d6f5d052611439607189 CPU Threads: 2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-06-13_23:46:49 Locale: it-IT (it_IT.UTF-8) OS: openSUSE Leap 42.1 (x86_64)
This does not depend on Bug 35449. What's missing here is "original Word .doc", so I set this to Needinfo in order to get that attachment here.
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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170929
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-20171030