Created attachment 64186 [details] doc version of the buggy file
Hi, There are two "signature" placeholders in the attached doc file - the right has three text lines. When loaded in LO, only second and third appear, the text "Pečiatka zamestnávateľa" is hidden. It appears, however, if the tab after "Podpis zamestnanca" (in the left signature) is deleted (and vanishes if the tab is inserted again). So, it appears that the missing text is "behind a corner". If opened in MSO and Abiword, all three lines are displayed. If the file is after loading in LO saved in the odf format, the line is still missing when loaded in LO, but is OK when opened in MSO and Abiword. Milos
Created attachment 71719 [details] Document that show the TABs bug. Confirmed in libo 4 Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7) Unbuntu 12.04 64bits what it do : The Third tab is over the line end depending on the size of text of previous tab (when centered ? ) - text could be inserted but not visible. Document joined is original of libo with same bug.
NEW per comment 2.
** 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.4.1 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: 2015-04-18
Hi, the bug is still present in Version: 5.0.0.0.alpha0+ and 4.4.2.2
** 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.5 or 5.2.1 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-20160920
The bug is still present in master 5.3.0.0.alpha0+ It is a regression present since LO36, not present in LO33 ApacheOO41 is also OK m Bibisected using the file BUG52065.odt: 7a864e30bffdf16060a3e8abe6d1f6853e841ce7 is the first bad commit commit 7a864e30bffdf16060a3e8abe6d1f6853e841ce7 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Wed Apr 25 10:25:21 2012 +0200 source-hash-4ff7252375b7b85eafbf176ca4e9184cc392d980 commit 4ff7252375b7b85eafbf176ca4e9184cc392d980 Author: Michael Stahl <mstahl@redhat.com> AuthorDate: Sun Feb 12 21:42:44 2012 +0100 Commit: Michael Stahl <mstahl@redhat.com> CommitDate: Mon Feb 13 00:25:03 2012 +0100 # bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574 # bad: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15 git bisect bad 8f4aeaad2f65d656328a451154142bb82efa4327 # bad: [369369915d3582924b3d01c9b01167268ed38f3b] source-hash-45295f3cdceb4c289553791071b5d7f4962d2ec4 git bisect bad 369369915d3582924b3d01c9b01167268ed38f3b # good: [351622aec2dff3cc3bbbb020ad0097c4322d2a21] source-hash-2c4537471c932b65e6f72e41881b505c4bbad12c git bisect good 351622aec2dff3cc3bbbb020ad0097c4322d2a21 # bad: [378efb6e51212a05d1bd4b85c916eec5753c1744] source-hash-d453788ac0476cc02b929b0907718ca771d6d956 git bisect bad 378efb6e51212a05d1bd4b85c916eec5753c1744 # good: [1a3c4b54a8782fe0f4bdba221e87012a92e4d323] source-hash-a330f38093e2643a26239557050561afae9ff23d git bisect good 1a3c4b54a8782fe0f4bdba221e87012a92e4d323 # bad: [5313c0086bde1a424c33b54120f14c4c79989cf7] source-hash-243fbda523cb71d0919539081d286eec4717ce15 git bisect bad 5313c0086bde1a424c33b54120f14c4c79989cf7 # bad: [45f31a35bb84d90093b303692f7424e63043f9aa] source-hash-f1c162967f032fcc5e4859f67c5b614c5dd19642 git bisect bad 45f31a35bb84d90093b303692f7424e63043f9aa # bad: [7a864e30bffdf16060a3e8abe6d1f6853e841ce7] source-hash-4ff7252375b7b85eafbf176ca4e9184cc392d980 git bisect bad 7a864e30bffdf16060a3e8abe6d1f6853e841ce7 # good: [9ee4ea8545fce94fc73af72ea32cc77621dedb3e] source-hash-f484e0b07820d5772376aa75bc0f823f1e77e2f2 git bisect good 9ee4ea8545fce94fc73af72ea32cc77621dedb3e # first bad commit: [7a864e30bffdf16060a3e8abe6d1f6853e841ce7] source-hash-4ff7252375b7b85eafbf176ca4e9184cc392d980 milos@trigan:~/LO/bibisect-43all$
bibisect range: f484e0b07820d5772376aa75bc0f823f1e77e2f2..4ff7252375b7b85eafbf176ca4e9184cc392d980 regression from: commit 36c905d8c2874f6f984d5fbbc07784ec20c43524 Author: Cédric Bosdonnat <cedric.bosdonnat.ooo@free.fr> AuthorDate: Fri Feb 10 21:57:54 2012 +0100 fdo#45908: Cleaning up the tabs too early can cause loops
** 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 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
Dear Milos Sramek, 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
repro 7.2+. I imagine the problem is related to a tab-stop following a centre-aligned tab-stop. Changing the 4.00cm tab-stop to left-aligned "fixes" the unseen content. Probably the space required for that first portion is mis-calculated (or simply needs to be calculated LATER and for some reason that isn't done). It is not a file open or save problem - since Word reads a round-tripped file just fine still. So it is "just" a layout issue.
Nice. PostFormat and PreFormat commands with no comments indicating why one would want to pre-format or post-format. And what does LastTab really mean - especially when it is nullptr? In any case, we get this warning at the moment: sw/source/core/text/txttab.cxx:325: SwTabPortion::PreFormat: rush hour Reverting Cedric's patch still causes that one document to hang. However, revert and removing the "return 0" fixes everything. (But what does it break?)
(In reply to Justin L from comment #12) > Reverting Cedric's patch still causes that one document to hang. That's attachment 56887 [details] (invoice.odt) from bug 45908. It would be good to add this file to sw/qa/core/data/oedt/pass as a unit test.
Proposed fix with unit tests at http://gerrit.libreoffice.org/c/core/+/112559
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b6850b9827a13b8f8d9b9749a982e128b7e0e867 tdf#52065 sw: revert tdf#45908: Cleaning up the tabs too early It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: d4f116d9576453f5974eb63db37a33c59ac53bc9 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded @Justin, thanks for fixing this issue!!