Bug 74151 - PRINTING: fields in table do not print
Summary: PRINTING: fields in table do not print
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.5.1 rc
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-01-28 11:26 UTC by Theo
Modified: 2014-06-18 03:56 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
test document (61.38 KB, application/vnd.oasis.opendocument.text)
2014-01-28 19:16 UTC, Theo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Theo 2014-01-28 11:26:26 UTC
Problem description: 
An odt document with a table containing user fields does not print all fields.
OS: OSX 10.9
LO: 4.2.0.3 64 bit version

Steps to reproduce:
1. Create a document with a table containing fields
2. Print the document

Current behavior:
Document shows fine on the screen. In the print-out not all fields are printed, sometimes the paragraph following the table is not printed either. PDF output is fine. I tried multiple printers.

Expected behavior:
Expect fields to show up in the printout as well.

              
Operating System: Mac OS X
Version: 4.2.0.4 rc
Last worked in: 4.1.4.2 release
Comment 1 sophie 2014-01-28 17:54:51 UTC
Hi Theo, Could you attach a document containing the fields that are not printing? or at least, indicate what sort of field are not printing. That will save us some paper and ink ;) Sophie
Comment 2 Theo 2014-01-28 19:16:25 UTC
Created attachment 92939 [details]
test document

test document. The text under item 1 does not print under LO 4.2.0.3 and 4.1.5.1. It does print under AOO.

It seems to be related to the logo graphic. If I remove this it prints fine. Not sure what causes this.
Comment 3 sophie 2014-01-29 10:22:32 UTC
Hi, thanks for the document. I can't reproduce, the document printed fine on my system, all fields are in the table are printed. May be it's a Mac only issue.
Version Version: 4.2.0.4
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 on Ubuntu 13.10 x64.
The version field should be filled with the first version you found the bug, so I set it to 4.1.5.1. Set it back to Unconfirmed - Sophie
Comment 4 Theo 2014-01-29 11:06:57 UTC
I can confirm that this is a Mac-only issue. At least: on win8 it does not show up.
Comment 5 Thomas van der Meulen [retired] 2014-01-30 19:12:38 UTC
Test details: 
Version: 4.2.0.4
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
os: mac osx 10.9.1
Comment 6 Thomas van der Meulen [retired] 2014-01-30 19:13:40 UTC
Thank you for your bug report, 
I can reproduce this bug.
The first paragraaf after the table isn't printed.
In 4.1.3.2 it was printed. 


Test system details: 
Version: 4.2.0.4
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
os: mac osx 10.9.1
Comment 7 Michael Stahl (allotropia) 2014-02-12 21:18:39 UTC
cannot reproduce on Linux.
could probably benefit from bibisecting on Mac.
Comment 8 Jorendc 2014-02-12 22:34:45 UTC
(In reply to comment #7)
> cannot reproduce on Linux.
> could probably benefit from bibisecting on Mac.

Can someone please verify:
NOT reproducible with latest commit I can checkout too: 
commit 6ca0dcc3cd12b5ba6b13bd8b05b59999bb2e22a9 
Author: Norbert Thiebaud <nthiebaud@gmail.com>
Date:   Sat Dec 7 13:22:03 2013 -0600
 af00fce7c50afabf778580e842d3487650f00e96 (http://cgit.freedesktop.org/libreoffice/core/commit/?id=af00fce7c50afabf778580e842d3487650f00e96)


reproducible with Version: 4.1.5.3 
Build ID: 1c1366bba2ba2b554cd2ca4d87c06da81c05d24

also reproducible with Version: 4.2.0.4 
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71


BUT it is not always reproducible... very weird behavior. Sometimes it works, sometimes it doesn't. Did restart 3 times, then could reproduce this behavior.

Related to bug 74780?

Kind regards,
Joren
Comment 9 Joel Madero 2014-06-18 03:56:52 UTC
With Joren's comment I am closing as WFM - if this is not true please set to NEW and provide confirmation that the problem exists on 4.2.5.2 or newer.