We have critical bug impacting multiple forms, We opened bug in June 2026 and even after 3 months Bug is not assigned.
Any direction what could be causing this issue and where to start?
172403 – When table rows extend onto a new page, the column names disappear
It was working fine till 25.8.0.1 and we tested against latest and still broken.
Thanks
Abhi
In the interim you could downgrade to 25.2.7.2 or install parallel version Installing in parallel - The Document Foundation Wiki
[Edit]
I checked in version 24.2 and your test sample from the bug report ran to several pages instead of just 2. On further investigation, I found nested sections, one of which was hiding an empty table. After deleting the lower level sections the table behaved normally.
Here LO 26.2.6.3, Fedora 44 (Linux)
Even after deleting all your sections, the behaviour persists: the column heading reappears after deletion but if I add, then remove blank lines before the table, the column heading disappears again. So, the bug does not seem to be related to sections.
I suspected something about fonts (metrics, perhaps). Roboto is not installed on my system, so I replaced it, but it is independent from font choice.
Remark: your sections do not make sense. Creating 1-column sections without other properties like note management bring nothing to the document. It is rather detrimental to stability and performance.
In addition, you have conditionally hidden some sections but the conditions are faulty, always resulting in FALSE, making the section always visible.
Try to simplify your document structure and avoid direct formatting, use styles instead.
How we can try to fix bug ourselves,
Depends on your capabilities…
Can you read code?
How much time do you have to invest?
Ever compiled LibreOffice yourself?
In cases like this, where behavior changes from one version to another it is a possibillity to bibisect the codebase until you find the change, where behaviour changes. Then one can start to make sense of the findings or notify the developer of this change of the (unwanted?) side+effects.
https://wiki.documentfoundation.org/QA/Bibisect
I guess it is more efficient for you to try to avoid the situation by fixing the complex layout with nested section, as found by @EarnestAl above.
