Created attachment 91318 [details] Database with three forms. Print the forms into files and have a look at the tablecontrols. Open the form "Transactions_Currency_black" of the attached database. Print the content which is shown in a *.pdf-file. The content of the tablecontrol isn't printed except the headers of the tablecontrol and the content of the check-boxes. Now open the form "Transactins_Currency_negativ_red". Print it in a file. The content is shown, beginning with the currencyfield, which shows a negative value. The values before this where lost. If you try the same with "Transactins_Currency_negativ_red_start", the whole content will be shown. The printing of all forms worked in LO 3.3.4. It first fails in LO 3.4.0beta1. One hint: The printing into a file shows beginning with LO 3.4.0beta1, in the properties of the file the content of the form as "Title".
Created attachment 91319 [details] Printout with LO 4.1.4.2 - look at the content of the tablecontrol
Created attachment 91320 [details] Printout with LO 3.3.4 - content of the tablecontrol is shown completely
Created attachment 91321 [details] Printout with LO 4.1.4.2 - red formatted currency-values. Tablecontrol shows content beginning with these values.
Created attachment 91322 [details] Properties of the *.pdf-files, as I could see ith with the file-manager.
Under GNU/Linux x86_64 using v4.3.0.3 Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7 these are the results from following the instructions in comment 0: - Form "Transactions_Currency_black" prints to PDF as indicated i.e., without any content showing in the Budget 1, Budget 2, Budget 3, Amount, or Account columns (despite values being shown in these fields in the form). - Form "Transactions_Currency_negativ_red" prints to PDF as indicated i.e., without any content showing in first row for the Budget 1, Budget 2, and Budget 3 columns (despite values being shown in these fields in the form). Confirmed. Status set to NEW.
Adding self to CC if not already on
Migrating Whiteboard tags to Keywords: (preBibisect) [NinjaEdit]
Still reproducible with current master under Ubuntu 15.10 x86-64. Best regards. JBF
This applies to 5.0.6 and 5.1 but not 4.4.7 on Ubuntu 14.04. I could not run 3.3 on my system so I cannot check it.
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Bug still exists in LO 5.4.1.2 and Version: 6.0.0.0.alpha0+ Build ID: 3b33f018713247dd511d232f8efdc7ce46de48f6 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-08-31_23:06:56 Locale: de-DE (de_DE.UTF-8); Calc: group It must be a regression - see description. Fails first with LO 3.4.0beta1.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists in LO Version: 6.1.0.3 Build-ID: efb621ed25068d70781dc026f7e9c5187a4decd1 OpenSUSE 15, 64bit rpm Linux.
Dear Robert Großkopf, 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 https://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! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists in Version: 7.0.5.2 Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Couldn't test it with a newer version, because LO crashes immediately when trying to print a form. Will write a new bug for this.
Couldn't be tested in LO 7.1 and newer, because printing of forms crashes whole LO. See bug 144139.
FWIW I see the same problem affects AOO 4.1.10
as far as I can see no explicit font color is set so it's rendered with what ever color the outputdevice starts with, and for the pdf export the default unset color is transparent
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2db427f9e098439ef68ce309bd8b440160ff37a0 Resolves: tdf#73139 text defaulted to transparent in pdf export It will be available in 7.3.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: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
done in trunk, backport to 7-2 in gerrit
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/3f9f935eed6f6110525aab48c72c3ba910691f32 Resolves: tdf#73139 text defaulted to transparent in pdf export It will be available in 7.2.3. 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: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.