Created attachment 50410 [details] gives funny result from Print:Selection I first noticed this in LibreOffice delivered with ubuntu-natty (11.04). It is present in the recent ubuntu update, LibreOffice 3.3.3 OOO330m19 (Build:301) tag libreoffice-3.3.3.1, Ubuntu package 1:3.3.3-1ubuntu2 and in my local build from master, commit id aa51fd4. Mike Hall reports <http://listarchives.documentfoundation.org/www/discuss/msg07466.html> that he sees the problem with Lo 1.4.2 under Vista. As the bug entry screen does not offer versions earlier than 3.3.0 Beta 2, I am setting version unspecified and all operating systems for this report. The reported processor x86-64 (AMD64) describes my system. I am running ubuntu-natty (11.04) (32-bit); printing to a HP Laserjet/4 Plus with duplex attachment. To see the problem ... (1) Download and open the attached a.odt. (2) Select text from "So, here is ..." to the end of the page. (3) Take menu options File > Print. Program presents Print dialog offering Range and Copies: Selection. (4) Click the radio button Range and Copies: Selection and then click Print. Program briefly displays Print progress dialog. Observe in the printout that the paragraph starting "So, here is ..." has a bullet and is indented like the following list. I think that that paragraph should be printed at the left margin and without a bullet.
For reference, the old OOo bug: http://openoffice.org/bugzilla/show_bug.cgi?id=66309 (And the related ones: http://openoffice.org/bugzilla/show_bug.cgi?id=47779 http://openoffice.org/bugzilla/show_bug.cgi?id=106308 )
[Reproducible] with reporter's sample and own documents and "LibreOffice 3.4.3 RC2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:302)]", still a problem with Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI [(Build ID:d337f79-a24c961-2865670-9752b71-7f8fd43 2fdd60d-fd28b6a-fd7bf20-aa369cb-28da3fb 6a9633a-931d089-ecd263f-c9b55e9-b31b807 82ff335-599f7e9-bc6a545-1926fdf)]" Also visible with "LibreOffice Portable 3.3.3 - WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:301 Tag 3.3.3.1)]" PDF export shows the same problem. IMHO OOo Heritage due to OOo bug numbers @Cédric: Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Created attachment 50628 [details] Screenshots, See Comment 2
It appears that the "level" of a heading within the selection to be printed becomes the nesting level of the bullet that LibreOffice applies. I shall attach screenshots of the editing window and the print dialog from LibreOffice 3.3.3 OOO330m19 (Build:301) tag libreoffice-3.3.3.1, Ubuntu package 1:3.3.3-1ubuntu2
Created attachment 51811 [details] screenshot of editing window, see comment 4
Created attachment 51812 [details] print dialog; see comment 4
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
reproducible with LO 4.0.2.2 (Win7 Home, 64bit) Result: the line "So, here ..." has no bullet and no indent in the document, but it is printed with a bullet and indent
I still see the problem with my debug build of master commit 692878e, fetched 2014-08-13, built and running on debian-wheezy 64-bit.
The problem is still evident in daily dbgutil bibisect version 2015-08-07: Version: 5.1.0.0.alpha1+ Build ID: 09a9234c021ad98c5adeb493b5814e97b92ee912 Locale: en-CA (en_CA.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 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
In the Print dialog, when I select Range equals Selection (step (4)), the small preview control shows three bullet points in the list. I lack a printer, and my attempt to continue to "Print to File..." runs into tdf#103515 "Assertion failed: SolarMutex not locked when opening database with Base". For now, I am taking it that the bug is still present. I am observing a local build of commit b157b82a, pulled around 2016-12-10 02:45 UTC, configured ... CC=ccache /usr/bin/gcc CXX=ccache /usr/bin/g++ --enable-option-checking=fatal --enable-dbgutil --enable-debug --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --without-package-format built and running on debian-stretch.
I avoided the crash that I mentioned in comment 12 by simply taking defaults. The resulting .ps file shows that the problem persists.
** 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
(In reply to QA Administrators from comment #14) After having read all the message, I was to tired for a useful comment.
I still see the bug in daily Linux dbgutil bibisect repository version 2017-12-13 running on debian-buster. In accord with comments 1 and 2, I am setting version = Inherited From OOo.
(In reply to Rainer Bielefeld Retired from comment #15) > (In reply to QA Administrators from comment #14) > After having read all the message, I was to tired for a useful comment. I can well understand that ;) To me, such a message is a trigger to test again. But maybe a summary at the start - in this case "request for testing in latest version (and possibly more)" - could be helpful. There are other messages requesting for missing information, suggesting that issues will be closed if that is not provided. So a different summary would be needed there.
Dear Terrence Enger, 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 the same in Version: 6.3.0.0.alpha1+ Build ID: b26b6cab5d8147d35f76a21c333719c80840d08d CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-20_23:15:15 Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US Calc: threaded I did some additional tests. Adding an (empty) paragraph at the end of the selection, is a work around.
*** Bug 93760 has been marked as a duplicate of this bug. ***
*** Bug 137476 has been marked as a duplicate of this bug. ***
Dear Terrence Enger, 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
Created attachment 183285 [details] reverse bibisect in linux-64-7.4 repo I see no bug in my local --enable-dbgutil build of commit 53d5f5e1 (2022-10-07), built and running on debian-buster. I am setting bug status VERIFIED FIXED. Reverse bibisect in the 7.4 repository points to commit cdf48e57 "tdf#134759 sw: clear items in SwAttrSet::CopyToModify()". result commit s-h date --------- -------- -------- -------------------- 3 bullets 392efeb7 f3c74dff 2022-06-17 07:18:19 2 bullets 9e277b0e cdf48e57 2022-06-17 07:41:54
(In reply to Terrence Enger from comment #23) > Created attachment 183285 [details] > reverse bibisect in linux-64-7.4 repo > > I see no bug in my local --enable-dbgutil build of commit 53d5f5e1 > (2022-10-07), built and running on debian-buster. I am setting bug > status VERIFIED FIXED. Interesting :) Also in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 100dc387ffd7df84199dae51abd9de35440905f1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: nl-NL (en_US.UTF-8); UI: en-US Calc: threaded the print preview doesn't have the problem any more.