Steps to reproduce:
1. Open attachment 63853 [details] from bug 49666
Observed behaviour: Footer isn't imported / displayed
Build ID: 7635e0c1c7f821a1081f8e3868f641ae74a172d6
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Version 184.108.40.206.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
but not in
Reproduced too with:
Build ID: 100e00fd3273536ebff130cfddc5da2b1fe609b1
CPU threads: 2; OS: Windows 6.1; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-04-20_05:12:24
Locale: en-US (fr_FR); Calc: CL
LO 220.127.116.11 (Build ID: e29a214)
Freezes LO 18.104.22.168. Footer is already missing with oldest commit of bibisect-43all. => notBibisectable
** 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!
still repro in
Build ID: cec31fdedd7c94f4ebf903a66456a75867db22b0
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2018-10-21_22:54:44
Locale: ru-RU (ru_RU); Calc: threaded
repro Version: 22.214.171.124.alpha0+
Build ID: 7673b027daed248d1be4dd1a773bfc0334a00c53
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
*** Bug 142903 has been marked as a duplicate of this bug. ***
Bug 142903 is about a footnote, imported but not numbered.
This bug, 107413, is about a footer.
Created attachment 177919 [details]
The example file in Word and Writer master
Looks good since:
author Attila Szűcs <firstname.lastname@example.org> Tue Jul 27 11:45:58 2021 +0200
committer László Németh <email@example.com> Wed Aug 25 13:45:23 2021 +0200
tdf#143384 DOCX import: fix SAXException at header with table
This is another example of negative page margin, which was worked around with a frame.
Thanks Attila for fixing this one too!
*** This bug has been marked as a duplicate of bug 143384 ***
Unittest added in https://gerrit.libreoffice.org/c/core/+/129216
Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":
tdf#107413: sw_rtfexport5: Add unittest
It will be available in 7.4.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:
Affected users are encouraged to test the fix and report feedback.