Problem description: A very annoying "feature" of newer versions of LO is that the printing dialog doesn't remember that you printed handouts. Let's say you need to first print handouts for slides 1-50, then from 100-110, then from 130-140. Every time you open the printing dialog again, it is set back to the "Slides" default, which is very impractical and illogical from a user's point of view. It doesn't need to remember this setting on saving and loading the ODP file, but within one session, it should. And yes, this *did* work with an older LO/OOo version, I just don't remember when that changed. Steps to reproduce: 1. Just open an ODP file and print handouts several times. Current behavior: Doesn't remember value for Print-Document pull-down menu between printing Expected behavior: Should remember value for Print-Document pull-down menu between printing Operating System: Windows XP Version: 4.0.0.3 release
None of our print settings are currently saved outside of Writer, this is a known issue and I am currently investigating the issue. As for it working in the past, I can say that I went all the way back to 3.6 alpha and the issue existed. If you can point to a particular version that did work, I'd be interested to see it as it might have code pointers for me to fix the problem. This may very well be a duplicate but I'm not sure where the dupe is, if someone finds it please mark it as such. If anyone else dives into the code here are some pointers: Writer successfully stores settings but does it incorrectly, code can be found here: http://opengrok.libreoffice.org/xref/core/sw/source/ui/uno/unotxdoc.cxx#2439 incorrect in that the settings are stored even if you click Cancel, the function is called MUCH too often (any time to tick/untick a box, instead of just when you click Ok) the general print options are here: http://opengrok.libreoffice.org/xref/core/sw/source/core/view/printdata.cxx If someone wants to work on it with me, feel free to email me. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well. Marking as: New (confirmed) Minor (doesn't prevent high quality work but it does slow it down) High (you'd expect settings to be stored, can get frustrating to have to set it every time you open the dialog) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please visit WIKI to see examples of great bug reports..
Remove comma from whiteboard.
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
This seems to be getting worse. With version: 4.2.1.1 (Build ID: d7dbbd7842e6a58b0f521599204e827654e1fb8b), Win7 64bit, when printing "handouts", not even the "slides per page" are remembered any longer between printing jobs, it is always reset to the "default" (6 slides per page). Not only do you have to select "Handouts" every time, you also have to set it to the proper slides per page if you want to print handouts. Very annoying.
Please look whether this is a duplicate of Bug 80866 and check with new 5.0.2 version.
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
** 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
This is still present, also inherited from OOo as present in 3.3 too Version: 6.4.0.0.alpha1+ Build ID: 80109586e6cb6d3e2e0a53a9079c3125ec9b8368 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear Stephan, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug