Steps to reproduce:
1. New Form with 1 Subform
2. Table-Field (Main-Form) + Table-Field (Sub-Form) place in Print-View
3. Printing this Form
The content of every table-field except the first table-field ist printing in grey. Changing Font-Color didn't change the printed result. Create new table-field or/and new subform didn't change the printed result. After unchecking printable on first table-field the second table-field is printed well. So only one table-field is printed well. Works with printing to pdf-file or with HP-Printer (didn't try other printers).
Every table-field and its content is printed black as usual fields.
Operating System: Linux (Other)
Version: 126.96.36.199 release
The version you use won't get a new bugfix-release. Actual versions are 4.0 or 4.1. Could you please test it with such a version?
Could you add the special Linux-Version and the printer you use?
Am 15.10.2013 20:55, schrieb firstname.lastname@example.org:
> email@example.com <mailto:firstname.lastname@example.org> changed
> bug 70502 <https://bugs.freedesktop.org/show_bug.cgi?id=70502>
> What Removed Added
> CC email@example.com
> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=70502#c1> on
> bug 70502 <https://bugs.freedesktop.org/show_bug.cgi?id=70502> from
> firstname.lastname@example.org <mailto:email@example.com> *
> The version you use won't get a new bugfix-release. Actual versions are 4.0 or
> 4.1. Could you please test it with such a version?
> Could you add the special Linux-Version and the printer you use?
> You are receiving this mail because:
> * You reported the bug.
my Linux is Linux Mint 14 and i use the printer HP 6500A Plus. But
printing with my HP-Drucker or Printing to file shows no differences.
Even a "printed" pdf-file got grey content of table-files.
The content is printed, regardless of changing font color, light grey.
can you please verify the behavior on a more recent release of LO, as i can't reproduce it with 4.2 / 4.3
Adding self to CC if not already on
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03