Download it now!
Bug 94015 - Footnote separator line shows wrong on screen
Summary: Footnote separator line shows wrong on screen
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Footnote-Endnote
  Show dependency treegraph
Reported: 2015-09-08 09:48 UTC by Henrik
Modified: 2019-02-25 18:38 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Henrik 2015-09-08 09:48:45 UTC
In a longer (80 page) document I use footnotes with a separator line above them. I have sent the file back and forth to a collaborator who have edited the document also using Libreoffice.

At some point the separator line have started to show as both thick and thin on different pages. It is not every other page, and I can't seem to find a system in it.

I have tried changing the separator line and removing it all together, but nothing have helped. In both these cases the actual lines shown on screen does not change. This is true, whether I use page styles or go through the Format - Page menu.

I have been able to change the lines to ........ [dotted lines], but as soon as I set them back to solid lines, the varied thickness reappear.

A search on the Internet have revealed a few others with the same problem. The most informative link was this:
Comment 1 Buovjaga 2015-09-15 16:29:08 UTC
I guess we can set to NEW right away per the old OOo bug report.
It would be good, though, if you could create a test case document and attach it.
Comment 2 QA Administrators 2016-09-20 10:32:26 UTC Comment hidden (obsolete)
Comment 3 mejl 2018-08-05 11:23:58 UTC
This bug persists in LibreOffice 6.0.3. It affects not only screen display, but also PDF exports.

Some footnote separators have roughly double the width. There are speculations in various online forums about this following a certain pattern, but there seem to be no workaround. For a fairly recent discussion, see