I reported this bug two years ago to the openoffice reporting tool but had no news. Now I'm a LibreOffice user so I report it here too. ISSUE: 1. Create a new spreadsheet 2. type something in a cell 3. Don't go out of this cell 4. Make a "Page Preview" every things seems fine 4. Try to print the document 5. The content of the cell isn't printed WORKAROUND: 1. Create a new spreadsheet 2. type something in a cell 3. Go out of this cell 4. Print the document 5. The content of the cell is now printed The problem also appears if you export into PDF instead for printing. It's not a big deal but it's quite annoying, our employees often complains that OOO doesn't always print the whole content of their documents. Thanks, Romain
[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
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
Hi Florian, I confirm that the problem still exist in the 3.5.2 version
(Not a problem with BASIC (the macro language), but a basic Calc problem, therefore adjusted component.)
Never confirmed by QA team - moving to UNCONFIRMED.
I can't reproduce this. Please test with latest version and report here. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Version: 4.2.7.2(In reply to Beluga from comment #9) > I can't reproduce this. > Please test with latest version and report here. Change back to UNCONFIRMED, > if the problem persists. Change to RESOLVED WORKSFORME, if the problem went > away. > > Win 7 64-bit Version: 4.4.0.0.alpha2+ > Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 > TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08 Beluga, I tried with the version packages into latest Linux Mint distribution: Version: 4.2.7.2 Build ID: 420m0(Build:2) And the problem persist, I'll try to obtain the latest version.
(In reply to Beluga from comment #9) > I can't reproduce this. > Please test with latest version and report here. Change back to UNCONFIRMED, > if the problem persists. Change to RESOLVED WORKSFORME, if the problem went > away. > > Win 7 64-bit Version: 4.4.0.0.alpha2+ > Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 > TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08 Reproducible for me in Calc from Debian testing. Version: 4.4.3.2 Build ID: 40m0(Build:2) While I can't reproduce with the steps written in the original post, I can reproduce the issue with this shorter chain of events: 1. Create a new spreadsheet 2. type something in a cell 3. Don't go out of this cell 4. Press ctrl+P to print 5. The content of the cell isn't printed If I either save the document, call "Page preview" with ctrl+shift+O or select another cell before I print, the changes are printed without problem. (The bug can also be tested without printing, as ctrl+P also shows a print preview where changes to the affected cell aren't seen.)
Thanks, Anders. I'll set to NEW in that case.
** 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
Can confirm that it the bug is still present without changes in LO 5.2.1 in Debian testing. Version: LibreOffice 5.2.1.2 20m0(Build:2) Also tested with LO 3.3 where the bug also was present, so setting version as "inherited from OOo".
** 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
Can confirm that it the bug is still present in LO 6.0.5 in Debian testing. Version: 6.0.5.1 Build ID: 1:6.0.5~rc1-2
Dear r.aviolat, 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
Repro 6.4+.
*** Bug 140093 has been marked as a duplicate of this bug. ***
Having a hardcopy showing content different from what the user is seeing on screen should not be accepted for about 10 years. Please see my comment to bug 140093#c2
*** Bug 125932 has been marked as a duplicate of this bug. ***
Dear r.aviolat, 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
The bug is still present in LO 7.5.6 in Debian testing. Version: 7.5.6.2 (X86_64) Debian package version: 4:7.5.6-1