Created attachment 50693 [details] Example for option buttons Documents containing option buttons and/or check boxes are not printed correctly: Some of the option buttons in the document are not printed. In documents with multiple pages it sometimes happens during printing that the buttons are placed anywhere in the document, but not in their orignial position. Furthermore, check boxes are not printed at all. The error with the option buttons also occurs when creating a PDF from the document using an external software (Nuance PDF Creator), but not when the internal converter of LO is used. The documents were originally created in OOo 3.2, where the print-out was flawless. When using LO 3.4.1 or 3.4.2. the errors described above occur. Since we are using quite a lot of documents containing option buttons and check boxes in our company, this regression is considered to be a reason nott to switch from OOo to LO. The error with the option buttons also occurs when creating a PDF form the document using an external software (Nuance PDF Creator), but not when LO internal converter is used. Sample documents for option buttons (example.odt.) and check boxes (check.odt) are attached.
Created attachment 50694 [details] Example for check boxes
Created attachment 54646 [details] Text docucument with some printed and not printed check boxes I can confirm that bug in LO 3.4.3, LO 3.4.4 and LOdev 3.5 (beta 1, LOdev 3.5.0 Build ID: 7362ca8-b5a8e65-af86909-d471f98-61464c4). Systems: Windows XP and Windows 7. In the document attached there are printed boxes and not printed ones. I have not found any differences in the properties of the different boxes. The disappearing check boxes are in tables. It seems to work in normal text. The change of anchor from "as Character" to "to Character" does not help. If I (as a user) could help to nail that bug down, please let me know.
I just found out, that the boxes will be printed if you delete the label(right click => Control... => tab "General" => Label) If you increase the size of the check box you can see the label next to the box. I assume if there is not enough space for the text, too, it will not be printed. If you increase the width of the column in the "Example for check boxes" (see above) the check boxes will be printed, too.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I confirm, that this bug still exists with LibreOffice 3.5.1.2 Build-ID: dc9775d-05ecbee-0851ad3-1586698-727bf66 Windows XP
Ah, I've seen this problem before. Maybe even in OOo . I don't remember, But I thought is was fixed..
Looking through the history of this bug I see two things: 1. No one has independently confirmed the bug 2. Reporter put it on MAB list. I am moving this off of MAB list and moving to UNCONFIRMED. @Reporter - Please don't set your own bugs to NEW, they should be left as UNCONFIRMED until independently confirmed. Also MAB list is handled by QA team and developers only. Thanks for your patience and understanding
For us the bug exists in all 3.x versions from 3.4.1 upwards and still makes it impossible for our company to switch to LO. I have not tested it in the 4.x branch. I am going to install LO 4.0 on our test server in the next couple of days and report if the bug is still existing. BTW: The bug was not put on the MAB-list by me.
I can confirm that this bug still exists in LO 4.0.0.3. I tested all 3 files. Am I allowed to set the status to "NEW"?
Thomas - indeed for priortization pointer: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Thanks Joel for your answer and the link. The chart is interesting. However for me it is still difficult to find the right prio. I would have chosen "normal". On the other hand we can not print dozens of our documents (without loosing essential information). The result of "printing only a part of the document" and "does not print certain documents" is about the same. So "Major/high" seems also possible. Our workaround is: Use OpenOffice for those documents. So I could understand if someone would choose "blocker/high" (because a part of the core functionality "print how I see the document" is broken and hinders us from using LO (at least for those documents). For a user like me it is not so easy to find the right answer.
Very highest should be major high in this case :) Blocker's apply to bugs that essentially affect everyone and have such a big impact that you basically cannot use LibreOffice at all. In this case I would have said Normal - High but Major is fine. Thanks for the confirmation:-D
Bug still exists in LO 4.0.2.2. It would be really great if someone could have a look into this. The bug is a regression and was reported 2011. We have many documents with not printed check boxes and would be very happy if this bug could be fixed.
Earliest reproducible is 3.3, therefore this isn't a regression. It's been inherited from the old OpenOffice. Workaround: convert the document to PDF and print the PDF. It won't look perfect but it will be readable and the checkboxes/buttons won't be lost.
Restricted my LibreOffice hacking area
** 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 (4.4.1 or later): 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
** 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.1.5 or 5.2.1 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-20160920
Tested with LibreOffice 6.4.6.2 Printing https://bugs.documentfoundation.org/attachment.cgi?id=54646 will not show the checkboxes. PDF export shows them. The bug is still present. It was inherited from OOo.
Dear technik, 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