Download it now!
Bug 73476 - PDF: PDF export and printing of specific document corrupts PDF and print-out
Summary: PDF: PDF export and printing of specific document corrupts PDF and print-out
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: filter:pdf
Depends on:
Blocks: PDF-Export
  Show dependency treegraph
 
Reported: 2014-01-10 14:57 UTC by Harald Koester
Modified: 2019-01-16 18:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Corrupted PDF document (840.78 KB, application/pdf)
2014-01-10 14:57 UTC, Harald Koester
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2014-01-10 14:57:38 UTC
Created attachment 91820 [details]
Corrupted PDF document

Problem description: 

Steps to reproduce:

[1] Open attached text document (attachment 91818 [details]). It is a chapter of the German LibreOffice user guide.
[2] Stay at the first page and export document as PDF. According the status bar a “repagination”  and then the export itself are performed. This PDF file is corrupted. I will attach it to this report.
[3] In order to create a correct PDF document first close the file without saving and open it again.
[4] Scroll through the whole document. **But be careful!** You can use the mouse wheel down to page 7, then scroll slowly with clicks on the single arrow of the scrollbar through page 8. Then you can go on with the mouse wheel up to page 30, then slowly through page 31, and then with the mouse wheel down to the end.
[5] Export file document as PDF. A repagination is not performed, the export starts without delay.
[6] Compare both PDF documents. In my attached document are several errors:
(a) Page 8: Illustration too small, in first hint (“Hinweis”) wrong position of “Hinweis”, display of second hint completely wrong.
(b) Page 10: Illustration too small, as a result of this the first paragraph 11 is shifted to page 10.
(c) Page 13: Hint of page 14 is shifted to page 13 and is empty. As a result some lines of page 15 are shifted to page 14.
(d) Page 17: Illustration too small, as a result text shifts in pages 17 to 19.
(e) Page 20: Illustration too small, as a result shifted text in the following pages.
(f) Page 31: Illustration too small, as a result shifted text, wrong position of “Hinweis”, footer missing.

The same problem appears if you print the document. I just tested it with page 8 and 13.

Bug already exists in Version 3.5.7

To my opinion this bug is a severe problem because you have to check all pages of a printed/exported documents to find these kind of errors. Usually this is not done particularly with larger documents. And if you find these errors it is not obvious how to avoid them.


              
Operating System: Windows 7
Version: 4.1.4.2 release
Comment 1 Harald Koester 2014-01-10 15:04:33 UTC
I think there is a close relationship between this bug and bug 73474 because they appear with the same document and some problems appear at the same position in the document.
Comment 2 Dominique Boutry 2014-01-29 15:46:34 UTC
I wrote for bug 73829 :

<I noticed in recent LibO versions a growing number of case where the display is updated within a perceptible delay (more than 1 second). So I supposed that the initial action of the drag&drop is processed by multiple threads, one very reactive catching the pointer position and resulting in a "move" decision, and another less reactive catching the new pointer position and updating the display to "resize" shape (or something like that ; the LibO delelopers will know...).

Anycase, this is a bug.

It would be interesting to look for a correlation with the computer overall workload (for instance detecting more frequent cases like the current one when LibO is used through CITRIX).>

IMHO the problems described here and in bug 73474 come from the same origin than above:
- just change "drag&drop a rectangle handle" with "scroll pages" (one thread is N pages in advance to another...)
- the load factor are the displaying of a large document and the image processing,
- see also the bug 73118 comment 6 on a behavior specific to a slow manipulation.
Comment 3 Buovjaga 2014-10-26 13:01:01 UTC
The problem with page 13 of the PDF persists, but not the others. Also, pg 13 of the PDF corresponds to pg 14 of the document, so there is something funky going on.

Win 7 64-bit dev build Version: 4.4.0.0.alpha1+
Build ID: fa58d91094895a530648630fa64b8724ea1e4305
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-26_09:30:18
Comment 4 QA Administrators 2015-12-20 16:21:09 UTC Comment hidden (obsolete)
Comment 5 Harald Koester 2016-01-04 21:07:28 UTC
Bug still exists with version 5.0.4.
Comment 6 QA Administrators 2017-10-30 08:33:54 UTC Comment hidden (obsolete)
Comment 7 Harald Koester 2017-11-11 19:04:08 UTC
Checked with 2 Systems:

Desktop with higher performance and versions 5.4.3 (64 bit) and 5.0.4 (32 bit): In both versions the bug does not occur. (Win 10, 64 bit)

Notebook with lower performance and version 5.4.2 (64 bit): The bug still exists on this system. (Win 7, 64 bit)

It seemed to me that the system performance has a major influence on the occurence of this bug. In comment 2 Dominique already expressed the same suspect.
Comment 8 Buovjaga 2017-11-13 16:14:57 UTC
(In reply to Harald Koester from comment #7)
> Checked with 2 Systems:
> 
> Desktop with higher performance and versions 5.4.3 (64 bit) and 5.0.4 (32
> bit): In both versions the bug does not occur. (Win 10, 64 bit)
> 
> Notebook with lower performance and version 5.4.2 (64 bit): The bug still
> exists on this system. (Win 7, 64 bit)
> 
> It seemed to me that the system performance has a major influence on the
> occurence of this bug. In comment 2 Dominique already expressed the same
> suspect.

Yep, on my high perf desktop (Linux) there are no problems.

Would you like to try with your notebook and 6.0 alpha? http://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/
Comment 9 QA Administrators 2018-11-14 03:45:38 UTC Comment hidden (obsolete)
Comment 10 Harald Koester 2019-01-16 18:50:19 UTC
Bug still exists with versions 6.1.3 (64 bit, Win 10).