[Libreoffice-bugs] [Bug 155734] It takes too long time to open an '.odt' document
https://bugs.documentfoundation.org/show_bug.cgi?id=155734 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Severity|enhancement |normal Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155761] New: [LibreOffice Base] Table data text is black and unreadable in dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=155761 Bug ID: 155761 Summary: [LibreOffice Base] Table data text is black and unreadable in dark theme Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jiri.klete...@gmail.com Description: Table data text in view mode is black and unreadable in dark theme UI Steps to Reproduce: 1. Set Dark theme in settings and restart app 2. Open any database file with some table and data in it 3. Open that table and observe unreadable text Actual Results: Text is unreadable Expected Results: Text should be white/readable Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149270] Writer: Font of watermark is displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=149270 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #7 from BogdanB --- Please retest, looking good to me. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 --- Comment #3 from fab@gmail.com --- Created attachment 187814 --> https://bugs.documentfoundation.org/attachment.cgi?id=187814=edit a sample file to test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 --- Comment #2 from fab@gmail.com --- (In reply to m.a.riosv from comment #1) > Please can you paste the information in Menu/Help/About LibreOffice, there > is an icon to copy. > > And add a sample file to test. Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155417] Mailmerge edit in Libre Writer mailmerge wizard is bugged, doesn't function very well, cannot edit fields`
https://bugs.documentfoundation.org/show_bug.cgi?id=155417 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155519] Shape Text Box Should Be Resizeable
https://bugs.documentfoundation.org/show_bug.cgi?id=155519 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155512] pptx import doesn't import unused master slides
https://bugs.documentfoundation.org/show_bug.cgi?id=155512 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155664] Reopening of calc sheets --off by 1-- size increase
https://bugs.documentfoundation.org/show_bug.cgi?id=155664 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155664] Reopening of calc sheets --off by 1-- size increase
https://bugs.documentfoundation.org/show_bug.cgi?id=155664 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151967] Printing handouts on Impress requires Portrait/Landscape option
https://bugs.documentfoundation.org/show_bug.cgi?id=151967 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151967] Printing handouts on Impress requires Portrait/Landscape option
https://bugs.documentfoundation.org/show_bug.cgi?id=151967 --- Comment #3 from QA Administrators --- Dear dmchatterton, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151964] Can't print to 3x5 paper
https://bugs.documentfoundation.org/show_bug.cgi?id=151964 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151743] Software crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=151743 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151743] Software crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=151743 --- Comment #4 from QA Administrators --- Dear Iverson, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151964] Can't print to 3x5 paper
https://bugs.documentfoundation.org/show_bug.cgi?id=151964 --- Comment #5 from QA Administrators --- Dear David Zokaites, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97801] Writer (X)HTML export: missing page numbers in Table of Contents
https://bugs.documentfoundation.org/show_bug.cgi?id=97801 --- Comment #11 from QA Administrators --- Dear Martin Nathansen, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97007] ODF does not allow presentation:master-element as attribute of anim:set
https://bugs.documentfoundation.org/show_bug.cgi?id=97007 --- Comment #10 from QA Administrators --- Dear Regina Henschel, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91595] UI Escaping dialog Format Comments doesn't bring focus back to document
https://bugs.documentfoundation.org/show_bug.cgi?id=91595 --- Comment #9 from QA Administrators --- Dear Juanjo, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74574] EDITING: Crop dialogue shows rotated image un-rotated
https://bugs.documentfoundation.org/show_bug.cgi?id=74574 --- Comment #10 from QA Administrators --- Dear James Murray, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67320] EDITING: Paragraph ends at about 64 cm although the page width is much wider
https://bugs.documentfoundation.org/show_bug.cgi?id=67320 --- Comment #9 from QA Administrators --- Dear paris, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65944] punctuation after inline formula may go to the next line
https://bugs.documentfoundation.org/show_bug.cgi?id=65944 --- Comment #14 from QA Administrators --- Dear Yury, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59353] Running spell check with 'Check words with numbers' inserts unwanted character
https://bugs.documentfoundation.org/show_bug.cgi?id=59353 --- Comment #10 from QA Administrators --- Dear Ed, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42471] Undo of cell style background formatting does not work when cell is in edit mode / undo stack of cell editing is sort of separated..
https://bugs.documentfoundation.org/show_bug.cgi?id=42471 --- Comment #14 from QA Administrators --- Dear Michal Suchanek, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136754] FILEOPEN: CHART: incorrect background
https://bugs.documentfoundation.org/show_bug.cgi?id=136754 --- Comment #5 from QA Administrators --- Dear Xisco Faulí, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125704] PDF export of embedded PDF outputs PDF that looks different
https://bugs.documentfoundation.org/show_bug.cgi?id=125704 --- Comment #13 from QA Administrators --- Dear philipp.kloke, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139700] UI: no hoover over effect page size picker in tabbed mode
https://bugs.documentfoundation.org/show_bug.cgi?id=139700 --- Comment #2 from QA Administrators --- Dear Telesto, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124689] Moving the scrollbar of the slides pane after having opened a presentation makes the file dirty
https://bugs.documentfoundation.org/show_bug.cgi?id=124689 --- Comment #8 from QA Administrators --- Dear sergio.callegari, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121166] TRACK CHANGES: linked files changes are not shown in the master document
https://bugs.documentfoundation.org/show_bug.cgi?id=121166 --- Comment #18 from QA Administrators --- Dear Emanuele Gissi, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120702] PPTX import: shape text with multiple columns not the same as in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=120702 --- Comment #6 from QA Administrators --- Dear Timur, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117516] Linked table in Writer can't be reduced to a smaller size when reducing range
https://bugs.documentfoundation.org/show_bug.cgi?id=117516 --- Comment #4 from QA Administrators --- Dear Aron Budea, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118558] doesn't change format of page to 2 columns for Endnote page style
https://bugs.documentfoundation.org/show_bug.cgi?id=118558 --- Comment #6 from QA Administrators --- Dear Roman Kuznetsov, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113095] Dialog tab labels dont have sufficient padding on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=113095 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please can you paste the information in Menu/Help/About LibreOffice, there is an icon to copy. And add a sample file to test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155758] FUNCTION: suggestion for SUM.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155758 m.a.riosv changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- I think SUM.IFS() that let's add several criteria, do what you need. https://help.libreoffice.org/latest/en-US/text/scalc/01/func_sumifs.html?DbPAR=CALC#bm_id658066580665806 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw/Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Bug 111450 depends on bug 155479, which changed state. Bug 155479 Summary: MCGR: clumsy export of linear gradient to SVG https://bugs.documentfoundation.org/show_bug.cgi?id=155479 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155760] New: Recent Documents disappears after updates
https://bugs.documentfoundation.org/show_bug.cgi?id=155760 Bug ID: 155760 Summary: Recent Documents disappears after updates Product: LibreOffice Version: 4.1 all versions Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tfrogg...@yahoo.com Description: First off, thank you very much for all of your work on this excellent software; I get a lot of good use out of it. The issue is as follows: Every time a new update is installed, the list of Recent Documents disappears. I find Recent Documents very useful, because I am working on numerous documents at any given time; because of this issue, I have refrained from installing new updates for quite a while. If this could be corrected that would be fantastic. Thank you very much. Steps to Reproduce: 1. Click on notification that new updates are available 2. Install update 3. Actual Results: When the update installs, the Recent Documents list has been cleared. Expected Results: Recent Documents should be left untouched, to make these documents easier to find. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155742] FILESAVE: Table in fromwriterdocument.html looks totally damaged when opened in Internet Browsers (but ok in LibO)
https://bugs.documentfoundation.org/show_bug.cgi?id=155742 --- Comment #7 from Alexander Kurakin --- Rainer, thanks! (In reply to Rainer Bielefeld Retired from comment #6) > c) But I can't tell whether it is possible to code such a table in html4 >And so I don`t know whether this is a real bug. Why, exactly? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107326] [META] Writer style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107326 Bug 107326 depends on bug 154933, which changed state. Bug 154933 Summary: Rename "Text body" to "Body text" https://bugs.documentfoundation.org/show_bug.cgi?id=154933 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 Olivier Hallot changed: What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- --- Comment #10 from Olivier Hallot --- More strings to fix in user interface: https://translations.documentfoundation.org/languages/pt_BR/libo_ui-master/search/?offset=1=+source%3A%22Text+Body%22+_by=-priority%2Cposition= -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155759] New: Blurry text in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155759 Bug ID: 155759 Summary: Blurry text in LibreOffice Writer Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aaron.bus...@gmail.com Description: Same issue in the following URL: https://www.reddit.com/r/libreoffice/comments/f2wlsy/blurry_text_in_libreoffice_writer/ I am using Fedora 38 and the following version of LibreOffice: 7.5.4.2 (Flatpak) Steps to Reproduce: 1. Use Calibri font 2. Use any zoom less than 120% 3. All text is blurry/pixelated Actual Results: All text is blurry/pixelated Expected Results: Not produced blurry/pixelated text Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 12; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7822 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137822] LAYOUT DOCX: Text boxes with parallel wrap have inline tables slip underneath them (bad), while optimal wrap does not (workaround)
https://bugs.documentfoundation.org/show_bug.cgi?id=137822 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||0262 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 --- Comment #9 from Justin L --- This document looks to be designed pretty much identically to the minimal reproducer in bug 137822 comment 5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 ady changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from ady --- In Filter by Color, I see the name of the colors, not the content; but comment 0 is not clear to me. Perhaps attaching a screenshot of what you see as incorrect would help? Additionally, attachment 187811 from comment 1 mentions the following (which is not the same as comment 0): " test dark orange 4 -cell 11 background color color not present in color selector if cell is empty background color items not always present in standard filter " Such behavior depends on how you select the autofilter area: * If you just click on cell A1 and then Autofilter, the autofilter goes as far as the first empty cell in the column. * If, instead, you first select the relevant area (A1:A18, or the entire column A:A), then all the values and all the respective colors will be included in the autofilter list. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94774] [META] DOCX (OOXML) object fill bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=94774 Bug 94774 depends on bug 128648, which changed state. Bug 128648 Summary: FILESAVE DOCX Linear gradient direction mirrored on saving https://bugs.documentfoundation.org/show_bug.cgi?id=128648 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104442] [META] OOXML shape (DrawingML and VML) related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104442 Bug 104442 depends on bug 128648, which changed state. Bug 128648 Summary: FILESAVE DOCX Linear gradient direction mirrored on saving https://bugs.documentfoundation.org/show_bug.cgi?id=128648 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128648] FILESAVE DOCX Linear gradient direction mirrored on saving
https://bugs.documentfoundation.org/show_bug.cgi?id=128648 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #15 from Buovjaga --- Let's close per the previous comment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95662] XHTML-Export: Export to html produces wrong decimalseparator together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=95662 --- Comment #34 from Svante Schubert --- I would appreciate if someone could enhance the test document having multiple list levels and all possible features with different numbers for testing: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#property-text_list-level-position-and-space-mode Created an external issue that might be mapped later to bugzilla: https://github.com/oasis-tcs/odf-tc/pull/50 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108152] Diacritic positioning at beginning of paragraph not working with Graphite font
https://bugs.documentfoundation.org/show_bug.cgi?id=108152 --- Comment #16 from Buovjaga --- (In reply to Sophie Sipasseuth from comment #15) > Hi Ilmari, > > Thanks for your comment, I checked the installation of the GodaGr font on my > computer and the screenshot "no repro bug graphite font". > I don't understand where is my mistake. > Could you explain to me where is it, please? > And I could better manage the installation of a font in the future. In your screenshot, the font name is shown in italics. This means the font is not available and has been substituted. If the installation was ok, the only reason I can think of is that you had LibreOffice running and did not close and reopen it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155452] When pasting image from Firefox in Calc, pasted image is not visible (only paste frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=155452 --- Comment #11 from Regis Perdreau --- tested in Version: 7.6.0.0.beta1+ (X86_64) / LibreOffice Community Build ID: a0ce0d4418ad92dd0e3a70cf698c549b544d6084 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded the paste action in paste special with bmp format is working now.( we have not the empty paste frame described previously) But not the direct ctrl-v paste action. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155736] Fileopen DOCX:Page numbers (from field of course, but inside a nested block SDT) are missing in the footer for a particular file
https://bugs.documentfoundation.org/show_bug.cgi?id=155736 --- Comment #9 from Justin L --- (In reply to Justin L from comment #8) > IIUC, this is a lot of hacky stuff, so it all could be dreadfully wrong. I > believe there was a lot of code changes/research into this area recently See bug 154478 which replaces a similar fix made for bug 154481. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #3 from Michel COLLET --- @ Eike Rathke waouh, so great! I don't have this description in my french documentation. Thanks a lot Eike -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #2 from Eike Rathke --- That wouldn't deliver a single return value though like SUMIF() (note it's not SUM.IF() that was probably because in French it's SOMME.SI()) but an array/matrix and that can already be accomplished by entering =range1*range2*condition as array formula, i.e. closing it with Shift+Ctrl+Enter instead of Enter. Example: =A1:A5*B1:B5*(C1:C5<>23) multiplies cells of A1:B5 with cells of B1:B5 if the corresponding value in C1:C5 does not equal 23; returns an array of 5 values, 0 if condition is not met. If in comment 0 you meant to multiply all values of a range for a condition, that can be accomplished similar using =PRODUCT(IF(C1:C5<>23;A1:A5;"")) as array formula (French PRODUIT()). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155758] New: FUNCTION: suggestion for SUM.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155758 Bug ID: 155758 Summary: FUNCTION: suggestion for SUM.IF() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mco_documentfoundation.org_UnimailQeWEbOBj39z8Xb@dclic .fr Created attachment 187812 --> https://bugs.documentfoundation.org/attachment.cgi?id=187812=edit example for the suggestion for SUM.IF() I suggest accepting functions in the "criteria" parameter. Examples: > SUM.IF(E6:M6;AND(>0;<100);E7:M7) > SUM.IF(E6:M6;OR(AND(>0;<100);AND(>200;<300));E7:M7) A detailed example is joined. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013)
https://bugs.documentfoundation.org/show_bug.cgi?id=76022 Justin L changed: What|Removed |Added Blocks||155040 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155040 [Bug 155040] FILEOPEN RTF Floating table is overlapped by subsequent non-floating ones -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155040] FILEOPEN RTF Floating table is overlapped by subsequent non-floating ones
https://bugs.documentfoundation.org/show_bug.cgi?id=155040 Justin L changed: What|Removed |Added Depends on||76022 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=76022 [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155045] [META] RTF Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=155045 Justin L changed: What|Removed |Added Depends on||126449 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126449 [Bug 126449] Tables in DOC document are overlapping (one floating multipage table-in-fr-table) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126449] Tables in DOC document are overlapping (one floating multipage table-in-fr-table)
https://bugs.documentfoundation.org/show_bug.cgi?id=126449 Justin L changed: What|Removed |Added Summary|Tables in DOC document are |Tables in DOC document are |overlapping (one floating |overlapping (one floating |multipage table-in-table) |multipage ||table-in-fr-table) Blocks||155045 --- Comment #5 from Justin L --- repro 24.2 (very early in development) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155045 [Bug 155045] [META] RTF Floating table related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155045] [META] RTF Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=155045 Justin L changed: What|Removed |Added Depends on||120262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120262 [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013)
https://bugs.documentfoundation.org/show_bug.cgi?id=76022 Justin L changed: What|Removed |Added Blocks||120262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120262 [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 Justin L changed: What|Removed |Added Depends on||76022 Blocks||155045 Summary|Fileopen DOC: tables|Fileopen DOC: floating |imported with reduced width |tables piled on top of each |if too close to the|other - probably due to |floating rectangle |in-line tables not wrapping ||around flies --- Comment #8 from Justin L --- I assume at this point this is just a duplicate of bug 76022 - marking it as a dependency. The problem of "first table shrunk in width to parallel wrapped around fly" was solved in 7.6. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=76022 [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013) https://bugs.documentfoundation.org/show_bug.cgi?id=155045 [Bug 155045] [META] RTF Floating table related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104763] FILESAVE ODT->DOC: image in table anchored to para need to be marked "layout in cell" on export for MSO benefit.
https://bugs.documentfoundation.org/show_bug.cgi?id=104763 Justin L changed: What|Removed |Added Summary|FILESAVE DOC: image in |FILESAVE ODT->DOC: image in |table anchored to para need |table anchored to para need |to be marked "layout in |to be marked "layout in |cell" on export for MSO |cell" on export for MSO |benefit.|benefit. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95623] FILEOPEN DOC Placement of images and frames wrong (multi-fly wrap ignored)
https://bugs.documentfoundation.org/show_bug.cgi?id=95623 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=80 ||206 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80206] FILESAVE/LAYOUT ODT->DOC/X: misplaces graphs, even when opened in the same version of LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=80206 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||623 Summary|FILESAVE: Save as .doc or |FILESAVE/LAYOUT ODT->DOC/X: |.docx misplaces graphs, |misplaces graphs, even when |even when opened in the |opened in the same version |same version of LibreOffice |of LibreOffice --- Comment #16 from Justin L --- This is a poster child for layout issues. I assume one big aspect at play here is bug 95623 (dealing with multiple flies affecting layout of a single paragraph). For DOC, it doesn't seem like a FILESAVE problem. It looks pretty good in MS Word 2010 (other than the caption switched from being at the bottom, to being at the top - also happens in LO). DOCX is a total disaster from both MSO and LO perspective. There is not much point in working on this bug report specifically. Too many variables. We can keep it open and celebrate when the pieces get fixed one by one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 --- Comment #1 from Regis Perdreau --- Created attachment 187811 --> https://bugs.documentfoundation.org/attachment.cgi?id=187811=edit test-file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] New: Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 Bug ID: 155757 Summary: Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field. Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: regis.perdr...@gmail.com Description: Color filter choice is missing in filter field. Steps to Reproduce: 1.load test file 2.open autofilter dialog 3.open standard filter 4. in the first line of filter dialogue "color", select in second field "background" 5. in the third field you should see a choice of different color, you'll cell content instead Actual Results: - cell contents Expected Results: - a set of background color Reproducible: Always User Profile Reset: No Additional Info: tested in Version: 7.6.0.0.beta1+ (X86_64) / LibreOffice Community Build ID: a0ce0d4418ad92dd0e3a70cf698c549b544d6084 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108799] [META] HTML and XHTML export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108799 Bug 108799 depends on bug 155244, which changed state. Bug 155244 Summary: Blue background when exporting spreadsheet as XHTML https://bugs.documentfoundation.org/show_bug.cgi?id=155244 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142076 Bug 142076 depends on bug 143103, which changed state. Bug 143103 Summary: Support Color Filter in "Standard Filter" dialog https://bugs.documentfoundation.org/show_bug.cgi?id=143103 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155756] New: UI Properties sidebar not displaying height over 100 and can't modify field over 100
https://bugs.documentfoundation.org/show_bug.cgi?id=155756 Bug ID: 155756 Summary: UI Properties sidebar not displaying height over 100 and can't modify field over 100 Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ralph...@gmail.com Created attachment 187810 --> https://bugs.documentfoundation.org/attachment.cgi?id=187810=edit Object height discrepancy between dialog and sidebar Properties sidebar seems to max out the height at 100.00. Scale is set to 1:16. I've tried 1:20 scale and it is the same issue. Dialog does display properly and does allow modification over 100. This is a good workaround. Steps to reproduce: 1) Open Draw using US Letter size page, inches units. 2) Draw a tall rectangle most of the height of the page. 3) Set scale to 1:16. Note "Height" of 100.00" in Properties tray. 5) Try to enter 105.00" and enter. It will ignore that and go back to 100.00". 4) Open "Position and Size" dialog and note the true height of the rectangle object. It allows modification to 105.00" here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #1 from Michel COLLET --- an improvement could be in the specification of a multiplier area and a multiplicand area. The multiplier area and the multiplicand area must have: the same size, either be in column or in line, or one could be in column and the other in line and vice versa. Each cell in the multiplier area have to be multiplied by the corresponding cell in the multiplicand area. Corresponding cells are: first cell of the multiplier area with the first cell of the multiplicand area, second one with the second one, etc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142076 Bug 142076 depends on bug 143103, which changed state. Bug 143103 Summary: Support Color Filter in "Standard Filter" dialog https://bugs.documentfoundation.org/show_bug.cgi?id=143103 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125876] More centralized endnote/footnote settings
https://bugs.documentfoundation.org/show_bug.cgi?id=125876 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] New: FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 Bug ID: 155755 Summary: FUNCTION: suggestion for MULTIPLY.IF() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mco_documentfoundation.org_UnimailQeWEbOBj39z8Xb@dclic .fr I suggest the new function MUTIPLY.IF() identical to SUM.IF() with a multiplication instead of an addition, and with the same parameters -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95662] XHTML-Export: Export to html produces wrong decimalseparator together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=95662 --- Comment #33 from Svante Schubert --- In Robert's ODT all XML uses correctly a dot '.' and not ',' therefore the ',' are added later and there are some possibilites of the culpit: I would like to provide some guidance to narraow down the possibilites! 1. I have checked the latest XSLT filter and could not view any ',' being added. By using his input document locally without LibreOffice (LO) the XSLT spreadsheet could be sorted out (for the latest sources). We (Michael Stahl and I) have a little test enviornment for the OASIS ODF TC that runs on Linux for the ODF2HTML XSLT, see https://github.com/oasis-tcs/odf-tc - especially the readme at: https://github.com/oasis-tcs/odf-tc/#odf2html-transformation-not-yet-automated-regression-tests 2. Be aware that not the ODT but a single XML is being provided to the ODT XSLT stylesheets by LibreOffice. To check the final flat file format, add an XSLT filter using the IDENT (identicall) transformation: https://github.com/oasis-tcs/odf-tc/blob/master/src/test/resources/odf1.4/tools/ident.xsl for instance using the fodt suffix as import/export filter, by this simply save to fodt format :-) NOTE: We added some QA guidance on how to add a stand-lone LO office, Configuration and pretty printing for ODF file XML in the ODF TC docu: https://github.com/oasis-tcs/odf-tc/#odf-editing-tool (just use the office you like) 3. Most likely the XSLT processor adds some localizied decimal-separator. Those who have the problem might want to install the XSLT 2.0 extension (see above docu as well that uses Saxon processor instead - but do not forget to fill thbe check-box using XSLT 2.0 at the XSLT filter configuration). Last but not least, I had been started writing this XSLT filter in my junior days early 2000 where HTML 4.0 was not fully implemented by browsers. When I look at the ODF of the test document using https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#property-text_list-level-position-and-space-mode I realized that nowadays CSS text-indent might be used: https://caniuse.com/?search=text-indent Helpful and efficient is to get into inspect mode (mouse context on selected HTML or press F12 on keyboard) and alter the HTML/CSS to watch if this might work. I consider doing some hack-fest on HTML XSLT at our next LibreOffice Conference in Bucharest, fixing the given test document.. :-) Sorry, close to no spare pro-bono time ahead (already quite booked).. ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155754] New: Underlining at start of new paragraph if the previous paragraph started with an underline
https://bugs.documentfoundation.org/show_bug.cgi?id=155754 Bug ID: 155754 Summary: Underlining at start of new paragraph if the previous paragraph started with an underline Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: peterphilipp...@gmail.com Description: If I am writing a LibreOffice Writer document and the previous paragraph starts with an underline, the next paragraph starts with underline set. Steps to Reproduce: 1.Start a paragraph with underlined words then turn off underline 2.Insert a to start a new paragraph Actual Results: Underline is on Expected Results: Underline not on. Reproducible: Always User Profile Reset: No Additional Info: Kept the underline status to what was last used. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155736] Fileopen DOCX:Page numbers (from field of course, but inside a nested block SDT) are missing in the footer for a particular file
https://bugs.documentfoundation.org/show_bug.cgi?id=155736 --- Comment #8 from Justin L --- (In reply to SATYA SRINIVAS K from comment #7) > Please let me know, if you have a direct answer or guess. IIUC, this is a lot of hacky stuff, so it all could be dreadfully wrong. I believe there was a lot of code changes/research into this area recently, and some of it dealt with exceptions. So, it will take a fair amount of work to try and wrap your mind around what the code is doing here. I suggest adding SAL_WARN statements when TOC starts and stops, when Push/PopPageHeaderFooter, at Push/PopSdt, and when CloseSectionGroup so that you get a feel for the flow of the code. In general, we have a LOT of problems in writerfilter because we don't have a stack. For example, you may be working in a paragraph, and then begin a content control (which also has its own paragraph) which contains a shape (which also has its own paragraph). So now, which of the writerfilter properties can you believe? You can't trust the "this is the first paragraph in the section" or pretty much any other property. Likely the same thing is true for m_bStartTOC. I tried to create stack properties once, but failed because RTF format doesn't track closely enough with DOCX (and they both share the same code). But in this case you can probably say "since I am in a footer, I can ignore any TOC flags because obviously I am not building a TOC right now". You will find lots of IsInHeaderFooter() examples similar to this in writerfilter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112313] FILESAVE ODT->DOCX: Text below image moves up next to it (optimal wrap) when file saved as DOCX (ODT 2cm wrap, DOCX ~1cm wrap; comment 14)
https://bugs.documentfoundation.org/show_bug.cgi?id=112313 Justin L changed: What|Removed |Added Summary|FILESAVE Text below image |FILESAVE ODT->DOCX: Text |moves up next to it when|below image moves up next |file saved as DOCX (ODT 2cm |to it (optimal wrap) when |wrap, DOCX ~1cm wrap; |file saved as DOCX (ODT 2cm |comment 14) |wrap, DOCX ~1cm wrap; ||comment 14) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94322] Unable to properly resize or hide the sidebar in chart edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=94322 --- Comment #18 from medmedin2014 --- Still repro on 7.5.4.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75350] [UI] overall presentation progress bar
https://bugs.documentfoundation.org/show_bug.cgi?id=75350 --- Comment #10 from robertjace --- First time visit this site and I learnt a lot of knowledge. I am a website visitor and get information from many website. I got knowledge from here. so that I thanks to you for this kind information. I visited a site there watched a stylish and fashionable San Francisco 49ers Starter Jacket Gold https://www.victoriajacket.com/product/san-francisco-49ers-starter-gold-jacket/. I order It. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Bug 107830 depends on bug 152046, which changed state. Bug 152046 Summary: DOCX Incorrect document layout https://bugs.documentfoundation.org/show_bug.cgi?id=152046 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152046] DOCX Incorrect document layout
https://bugs.documentfoundation.org/show_bug.cgi?id=152046 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104522] [META] DOCX (OOXML) header & footer-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104522 Bug 104522 depends on bug 100680, which changed state. Bug 100680 Summary: FILEOPEN DOCX Image anchored as character + long word wrapped differently https://bugs.documentfoundation.org/show_bug.cgi?id=100680 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120466] [META] DOCX (OOXML) anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120466 Bug 120466 depends on bug 100680, which changed state. Bug 100680 Summary: FILEOPEN DOCX Image anchored as character + long word wrapped differently https://bugs.documentfoundation.org/show_bug.cgi?id=100680 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71437] Dead keys not working (workaround: comment 3 or comment 6 or comment 19 or comment 30)
https://bugs.documentfoundation.org/show_bug.cgi?id=71437 --- Comment #47 from Tristan Miller --- (In reply to gweberbh from comment #46) > Sorry to disappoint, I am still having this problem. My keyboard is pt-BR > when I try to type an accent a quote is generated and my cursor is sent to a > new paragraph. Does the problem occur only when you type a dead key at the end of a paragraph, or does it also occur when typing a dead key in the middle of a paragraph? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105605] [META] Digital signatures bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105605 Heiko Tietze changed: What|Removed |Added Depends on||155665 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155665 [Bug 155665] Rembering GPG Certificates for Digital Signatures on Each Save -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155753] In Impress, the size of the pasted image will change if the computer screen setting is changed.
https://bugs.documentfoundation.org/show_bug.cgi?id=155753 --- Comment #4 from NISZ LibreOffice Team --- Created attachment 187807 --> https://bugs.documentfoundation.org/attachment.cgi?id=187807=edit Screenshot_Scale and Layout 150% -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155753] In Impress, the size of the pasted image will change if the computer screen setting is changed.
https://bugs.documentfoundation.org/show_bug.cgi?id=155753 --- Comment #3 from NISZ LibreOffice Team --- Created attachment 187806 --> https://bugs.documentfoundation.org/attachment.cgi?id=187806=edit Screenshot_Scale and Layout 100% -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155753] In Impress, the size of the pasted image will change if the computer screen setting is changed.
https://bugs.documentfoundation.org/show_bug.cgi?id=155753 --- Comment #2 from NISZ LibreOffice Team --- Created attachment 187805 --> https://bugs.documentfoundation.org/attachment.cgi?id=187805=edit Sample document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155753] In Impress, the size of the pasted image will change if the computer screen setting is changed.
https://bugs.documentfoundation.org/show_bug.cgi?id=155753 --- Comment #1 from NISZ LibreOffice Team --- Created attachment 187804 --> https://bugs.documentfoundation.org/attachment.cgi?id=187804=edit Sample image to insert -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155753] New: In Impress, the size of the pasted image will change if the computer screen setting is changed.
https://bugs.documentfoundation.org/show_bug.cgi?id=155753 Bug ID: 155753 Summary: In Impress, the size of the pasted image will change if the computer screen setting is changed. Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@nisz.hu Description: In Impress, the size of the pasted image will change if the computer screen setting is changed. Steps to Reproduce: 1. Open LO Impress. 2. Insert -> Image. 3. Save the document. 4. Close the LO. 5. Right click on the computer screen -> screen settings -> Scale and Layout -> Change the settings. 6. Open LO. 7. Open the saved document. 8. insert the same image. Actual Results: Changing the screen setting will then resize the inserted image. Expected Results: The inserted image will not be resized after the screen settings have been changed. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 389a8d52d9961f89c0b2847b30ee1ca59a8fdc80 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155730] Wrong Anchor item in dropdown field of the Control Properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=155730 Heiko Tietze changed: What|Removed |Added Component|Calc|UI CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Hardware|x86-64 (AMD64) |All Keywords|needsUXEval | OS|Windows (All) |All Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Heiko Tietze --- (In reply to Heiko Tietze from comment #3) > > (c) Remove the 'Anchor' item in the Control Properties dialog. > My first choice would be c)... (In reply to Regina Henschel from comment #4) > That would speak for removing it there. Seems we are in agreement - and no one else hollered in. Let's remove the anchoring from the object properties and keep it only at the (general) object attributes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155752] New: updating don't preserve option settings
https://bugs.documentfoundation.org/show_bug.cgi?id=155752 Bug ID: 155752 Summary: updating don't preserve option settings Product: LibreOffice Version: unspecified Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mco_documentfoundation.org_UnimailQeWEbOBj39z8Xb@dclic .fr Options set in "Tools/options" and "Tools/AutoCorrection" are not preserved when LibreOffice is updated. I suggest: > choice 1 (my prefered): always preserve the options which are compatible with > the new version (in case of options are not preserved, signal it and list > them to the user) > choice 2: give the choice (preservation or not) to the user in the > preparation phase of the updating process > choice 3: a mix of choices 1 and 2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155729] Set paragraph style drop down is able to create new styles, which is unconventional (and not fitting the label)
https://bugs.documentfoundation.org/show_bug.cgi?id=155729 --- Comment #4 from Eyal Rozenberg --- (In reply to Telesto from comment #3) > B) Why should the new style be a child of heading 2? Only because heading 2 > was applied prior to this? Yes. You had Heading 2, you made some changes, you create a new style - that style is modified-Heading-2. Makes sense to me. > You can't even tell this being the case, without > the style sidebar open (or the edit style dialog) Well, that's because the toolbar is a compact interface. It's a way to do something while accepting the defaults when the full interface is not in view. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155729] Set paragraph style drop down is able to create new styles, which is unconventional (and not fitting the label)
https://bugs.documentfoundation.org/show_bug.cgi?id=155729 --- Comment #3 from Telesto --- (In reply to Eyal Rozenberg from comment #2) > (In reply to Telesto from comment #0) > If you got prompted when this happens, "Create a new style named 'footnote'? > Y/N" - would that be better in your view? I think I would be fine with that. It's an improvement.. I have no strong opinion. I'm more or less questioning the design, because it surprised me. Are you supposed to 'manage' styles with the toolbar, or only 'set' - read apply - a style, as the label suggests. A) If I create a style - under in this case - heading 2 I expect it to be different from heading 2. The edit style dialog should probably open? B) Why should the new style be a child of heading 2? Only because heading 2 was applied prior to this? You can't even tell this being the case, without the style sidebar open (or the edit style dialog) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155736] Fileopen DOCX:Page numbers (from field of course, but inside a nested block SDT) are missing in the footer for a particular file
https://bugs.documentfoundation.org/show_bug.cgi?id=155736 --- Comment #7 from SATYA SRINIVAS K --- Justin, It looks like the commit you pointed out is the culprit. Page numbers are displaying as expected if I comment this line m_bStartTOC = true; in DomainMapper_Impl::handleToc method. I still need to track down how this member m_bStartTOC is causing this issue when set to true. Please let me know, if you have a direct answer or guess. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115546] Mirrored Page Headers do not respect "Same Content on Both Sides" setting wrt spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=115546 --- Comment #6 from Sebi --- This bug is still present in 7.5.2.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155664] Reopening of calc sheets --off by 1-- size increase
https://bugs.documentfoundation.org/show_bug.cgi?id=155664 Przemysław changed: What|Removed |Added CC||pp.the.vera...@yandex.com --- Comment #4 from Przemysław --- Created attachment 187803 --> https://bugs.documentfoundation.org/attachment.cgi?id=187803=edit explanation + imgs Hi, You cannot understand how deeply I abhor using this CRAP bugzilla, I've tried to answer to Adam664 via Yandex Mail, but it way bounced back. Here it doesn't accept small images. I HATE it. But I must. The "hate" increases to square! -- I've checked it further. There's no need for the script(s). You can repeat it manually - from LO basic soffice program window or directly from console $ /opt/libreoffice/program/scalc file, ANY spreadsheet file shows the bug, new empty one too. You may run it from IceWM menu prog "LOff Office" libreoffice-main /opt/libreoffice/program/soffice prog "LOff Writer" libreoffice-writer /opt/libreoffice/program/swriter prog "LOff Spreadsheet" libreoffice-calc /opt/libreoffice/program/scalc prog "LOff Draw" libreoffice-draw /opt/libreoffice/program/sdraw prog "LOff Impress" libreoffice-impress /opt/libreoffice/program/simpress (etc) /here img/ 1) I can hurdle the bug using IceWM options. You can run a script to open any number of calc files in any number of Desktops, e.g. 3 in D1, 4 in D2, 3 in D3 (pay attention numbering in IceWM) # WS: 0 1 2 3 4 5 6 7 8 9 10 11 -> WorkSpaces # DT: 1 2 3 4 5 6 7 8 9 10 11 12 -> DeskTops Then you have to focus opened calc window in toolbar, click right context then Tile -> Left/Right Half. It sets windows in correct sizes. But ANY other method does not works. /here img - IT CANNOT BE ATTACHED! Oh, God! Why I'm using such CRAPs as LibreOffice and the f***g bugzilla?! I've had to be in despair.../ Even WM_CLASS applied to $ ~/.icewm/winoptions (find using xprop) fails: # LibreOffice libreoffice.libreoffice-calc.geometry: 950x1025+0+0 LO is so bitchy that the bug has been going on for many, many years. It has been appearing out from search efforts with dates back from 2010 up to 2022. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155751] New: dBase: BETWEEN won't include first and last value in queries
https://bugs.documentfoundation.org/show_bug.cgi?id=155751 Bug ID: 155751 Summary: dBase: BETWEEN won't include first and last value in queries Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 187802 --> https://bugs.documentfoundation.org/attachment.cgi?id=187802=edit Extract the *.zip and start the database file … Download the attached *.zip-file. Extract and start the database file. Hope the connection to the dBase-file will work. Start the query. It will show "ID" starting with 2, ending with 9. Close the query, open the query for editing (will only work opening in SQL-mode). Have a look at the code: SELECT "ID" FROM "table" WHERE "ID" BETWEEN '1' AND '10' BETWEEN should start with '1' and end with '10'. If you execute BETWEEN in internal HSQLDB and Firebird it will do so. For dBase connections it will exclude start value and end value. BETWEEN should give the same result as SELECT "ID" FROM "table" WHERE "ID" >= 1 AND "ID" <= 10 This bug appears on all LO-versions here (oldest here: LO 5.1.5.2). It appears also on AOO 4.1.8. Think it has been inherited from OOo. See also: https://ask.libreoffice.org/t/base-query-not-reading-table-with-between-statement/92299 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw/Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Bug 111450 depends on bug 155479, which changed state. Bug 155479 Summary: MCGR: clumsy export of linear gradient to SVG https://bugs.documentfoundation.org/show_bug.cgi?id=155479 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
