Description: Attempting to change items at the bottom of the Print Properties Device tab, such as "Printer language type," "Color," or "Color depth" are completely ignored and remain unset after clicking OK. I found this testing old bugs relating to PostScript vs PDF Mode printing. It turns out that as of LO 5.0, this bug keeps these settings from being applied. Steps to Reproduce: 1. New document/drawing/spreadsheet/etc... 2. File->Print 3. Click Properties 4. Select "Device" tab 5. Change "Printer language type" to something else 6. OK 7. Click Properties 8. Select "Device" tab again. Actual Results: The Printer language type was never actually set, so it will return to its original value. Printing after clicking OK will generate a print job that does not have the settings applied. Expected Results: The Printer language type should be set to whatever we changed it to, as it used to. Reproducible: Always User Profile Reset: Yes, fresh profile. Additional Info: LibreOffice refuses to set any 3 of these drop-down items ("Printer language type," "Color," and "Color depth"). It's not that these items are applied but not remembered. Attempting to set these items will affect the print job. This could cause someone to accidentally print a huge job in color and potentially waste a lot of money. Note that I believe there is a bug with pdf mode printing where attempting to change the print job to grayscale by using the Color dropdown will be ignored. It only works under PostScript printing. LibreOffice appears to honor the global setting for either PDF Mode or Postscript level from driver (Tools->Options->Print->PDF as standard print job format). One workaround is that if an item is selected in the Device tab main list like Media Type (or whatever options your printer offers), the drop-down setting will then be applied/remembered. My guess is there is problem with the logic for determining when a setting has been modified and will need to be saved/applied. This affects LO 5.0.0+ but not 4.4.7. I wasn't sure if this would fall under UI or Printing. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Confirmed in Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) but not in Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8)
** 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
Still repro and this seems to be Linux-only as Windows offers the dialog of the printer driver itself. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 8e63d451b2aeb646ece98c4e219f92957f4482bd CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on June 1st 2018
Still reproducible with the new print dialog Version: 6.3.0.0.alpha0+ Build ID: 0d46fb02f3f19d11db40b6c5335d78a3894502d7 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded @Daniel Silva, I thought you might be interested in this issue...
Dear tmacalp, 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
Why has no one ever bibisected this yet? It is easy to reproduce. It started in LO 5.1 - where there is no per-commit bibisect on Linux, so I used Miklos' daily one to get the range https://cgit.freedesktop.org/libreoffice/core/log/?id=4daa3f54437730fe4e509082faa0d3509c62cea0&qt=range&q=ee3d40b30816a8fc6d4e8f984659c8dfac19ec3b..efa2c05e84d0696b31bd822d3234798be43853ad I didn't see anything in that range that seemed obviously. It seems very much like a Caolan thing, but his four patches didn't seem to be related to this on the surface. I believe there is a Windows 5.1 per-commit bibisect, so perhaps someone having that could zero in on an exact commit? (P.S. the screen wasn't redrawing properly for me, so I had to mostly guess at where to click - but that was good enough to do the bibisecting. I hope you do not have that same problem on Windows, but it is not insurmountable.)
I suspect its commit 07602e5a8b869be1c45158cf71d6015d17a5f797 Author: Katarina Behrens <Katarina.Behrens@cib.de> Date: Wed Jun 24 17:31:32 2015 +0200 tdf#91362: Don't override printer page autodetection if printer settings haven't been modified which is close to, but not mentioned in, the range you isolated
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/07ec53a20caa416ba3f64f04151c3317313fa381 Resolves: tdf#106484 Print Properties Device tab dropdown change not detected It will be available in 7.2.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.
fixed in master, backports to 7-1 and 7-0 in gerrit
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/cc2595a8041f0e863c786ff0d028561cb3f40552 Resolves: tdf#106484 Print Properties Device tab dropdown change not detected It will be available in 7.0.5. 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.
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/95617b04651ae9f515ced79760851123a7e09236 Resolves: tdf#106484 Print Properties Device tab dropdown change not detected It will be available in 7.1.1. 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.
Verified, thanks Arch Linux 64-bit Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 55933f49f5a04708d27dc69e8778ec126646e3a5 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 26 January 2021