[Libreoffice-bugs] [Bug 117576] Image inserted as PDF initialy is stored as both PDF and PNG, but later is stored as two identical PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=117576 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #15 from opensuse.lietuviu.ka...@gmail.com --- I still can reproduce in Version: 6.0.6.0.0+ Build ID: 4aaf958cdad2a19be49dbd5f9ca661753f8a94ab CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-0, Time: 2018-06-11_22:35:54 Locale: lt-LT (lt_LT.UTF-8); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117576] Image inserted as PDF initialy is stored as both PDF and PNG, but later is stored as two identical PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=117576 --- Comment #14 from opensuse.lietuviu.ka...@gmail.com --- I also can not reproduce in Version: 6.2.0.0.alpha0+ Build ID: 90e4c55d01637178418c33ffe818263114a53374 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-06-12_00:10:12 Locale: lt-LT (lt_LT.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118176] Show the Unicode in wrong size...
https://bugs.documentfoundation.org/show_bug.cgi?id=118176 --- Comment #2 from Mike Kaganski --- This is not a proper bug description; in this state, it's a kind of quest "try to guess what I'm talking about; see how inventive I am". For instance, I don't see anything special in Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: ru-RU (ru_RU); Calc: CL, using Liberation Mono, and increasing the size. Is it because it is Linux-only? or just because OP didn't tell what to look at, and what are the pre-requisites, like browser (which might in theory affect what is copied to clipboard), fonts, and specific sizes? Please provide the information in understandable and reproducible way (with clear steps, like "1. Create a new text document; 2. Paste the string copied from the comment 0; 3. Ansure that the font is XXX, and size is Y; 4. Change size to Z; 5. Observe ABC at right/left/top/bottom of page/line/whatever..."). It sometimes helps to attach documents you created to show the problem (in which you know the problem os observable); and/or screenshots. Please set the status back to UNCONFIRMED after you've provided the necessary info. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117576] Image inserted as PDF initialy is stored as both PDF and PNG, but later is stored as two identical PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=117576 --- Comment #13 from opensuse.lietuviu.ka...@gmail.com --- I can not reproduce this bug in LibreOffice version: 6.1.0.0.beta1 ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 threads: 4; OS:Linux 4.4; GUI: GL; VCL: gtk2; Locale: lt-LT (lt_LT.UTF-8); Calc: group Thus bug is fixed in LO 6.1, but we need to backport fix into LO 6.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113117] [META] Windows installer/uninstaller bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113117 Adolfo Jayme changed: What|Removed |Added Depends on||99891 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99891 [Bug 99891] Update installer fonts to match newer versions of Windows -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99891] Update installer fonts to match newer versions of Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=99891 Adolfo Jayme changed: What|Removed |Added Blocks||113117 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113117 [Bug 113117] [META] Windows installer/uninstaller bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118092] improvement suggestion: easy Language
https://bugs.documentfoundation.org/show_bug.cgi?id=118092 Adolfo Jayme changed: What|Removed |Added Component|BASIC |Documentation CC||olivier.hallot@documentfoun ||dation.org -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118176] Show the Unicode in wrong size...
https://bugs.documentfoundation.org/show_bug.cgi?id=118176 Adolfo Jayme changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Adolfo Jayme --- Do you have any valid, *specific* problem to report? There is no sample reproducer document, screenshot, steps to reproduce, etc. https://www.chiark.greenend.org.uk/~sgtatham/bugs.html However… > Show the Unicode in wrong size... > And change the size and fonts type... have fun... You realize that these characters are emoji, so are likely to be supported only in fonts with “Emoji” in their name? If a character isn’t supported in a typeface, how can you expect LO (or any other program whatsoever) to assign specific character formatting that will look as you expect? (Not that it makes sense to apply any formatting to *emoji* that isn’t font size, but…) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79627] EDITING: Can edit charts in locked files
https://bugs.documentfoundation.org/show_bug.cgi?id=79627 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86584] Chart is hidden, if data separated by split/freeze limit of the window
https://bugs.documentfoundation.org/show_bug.cgi?id=86584 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95038] Chart: Add Arrow support to Line Charts
https://bugs.documentfoundation.org/show_bug.cgi?id=95038 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 93005] Chart / Unable to save as .odc file
https://bugs.documentfoundation.org/show_bug.cgi?id=93005 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106986] Graph corrupt when saving to DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=106986 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99025] [FORMATTING, FILESAVE] Column breaks are not properly exported as .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=99025 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105236] Chart Axis Number Format not display correctly in XLS but ODS is working
https://bugs.documentfoundation.org/show_bug.cgi?id=105236 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90096] Lines in a multilateral flowchart in Draw change on the pages that are not in the focus
https://bugs.documentfoundation.org/show_bug.cgi?id=90096 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45269] Presentation does not Look the same on Linux and Windows if Hardware acceleration enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=45269 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 73483] FORMATTING: manual pagebreak is lost after clear direct formatting and save the file / and format of paragraphs Text block changes to Default
https://bugs.documentfoundation.org/show_bug.cgi?id=73483 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96124] Chart's Text Flow:break doesn't work with Date or Time formatted Cell
https://bugs.documentfoundation.org/show_bug.cgi?id=96124 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 61185] Calc Charts: Non-contiguous category ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=61185 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100084] VIEWING: charts not displayed in .xlsx reports generated from ibm cognos
https://bugs.documentfoundation.org/show_bug.cgi?id=100084 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 82684] TABLE: Table shows fake border lines on page breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=82684 --- Comment #9 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 44626] Copying a XY (scatter) chart with first row as label leads to incoherent data range
https://bugs.documentfoundation.org/show_bug.cgi?id=44626 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83310] FILEOPEN: Images missing in cognos 10.1 generated .xlsx charts
https://bugs.documentfoundation.org/show_bug.cgi?id=83310 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 49466] Page break blue line misplaced
https://bugs.documentfoundation.org/show_bug.cgi?id=49466 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107748] When resizing window after inserting chart and remaining in the chart mode, there are UI glitches
https://bugs.documentfoundation.org/show_bug.cgi?id=107748 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107052] PAGE FOOTER: manual column is ignored/does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=107052 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 93696] Row Break Across Pages and Columns menu entry doesnt work correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=93696 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108478] bar chart is not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=108478 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103390] Charts series from comma-labeled sheets in Calc are empty after copying in other LibO app
https://bugs.documentfoundation.org/show_bug.cgi?id=103390 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68419] FORMATTING: Paragraph borders are not merged between two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=68419 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96672] Outgoing mail server password in clear text inside the registrymodifications.xcu file
https://bugs.documentfoundation.org/show_bug.cgi?id=96672 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98275] PNG image with alpha channel pasted from clipboard has black background
https://bugs.documentfoundation.org/show_bug.cgi?id=98275 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100481] Hiding Page Breaks Hides Footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=100481 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 93790] Insert "Page break" before Summary
https://bugs.documentfoundation.org/show_bug.cgi?id=93790 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106067] A chart in a duplicated sheet sometimes loses its data range
https://bugs.documentfoundation.org/show_bug.cgi?id=106067 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105955] Problem with setting background fill to a normal piechart data series
https://bugs.documentfoundation.org/show_bug.cgi?id=105955 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 87409] Inserting manual page break does not work with bullets and numbering with the cursor at the very beginning of the line
https://bugs.documentfoundation.org/show_bug.cgi?id=87409 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105505] Changes at y-axis of a chart created with Calc when pasting it in a Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=105505 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100490] FILEOPEN: docx graphic import does not honor char color
https://bugs.documentfoundation.org/show_bug.cgi?id=100490 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107481] EDITING: Text behind frame after undoing page break
https://bugs.documentfoundation.org/show_bug.cgi?id=107481 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 89863] Wrong display of chart with long captions
https://bugs.documentfoundation.org/show_bug.cgi?id=89863 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 87274] CONDITIONAL FORMATTING: Option for reunify ranges with same conditions
https://bugs.documentfoundation.org/show_bug.cgi?id=87274 --- Comment #21 from Mike Kaganski --- (In reply to m.a.riosv from comment #20) > Sample for test > > Sorry, I can't see it working with attached document, maybe it's not on Well - for some reason, it doesn't work with your sample, really. Sigh; Tor's commit looked hoghly relevant to this issue. OTOH, a fix for bug 95295 does work on that file: if you copy the range B5:D5, and then paste it back, it will re-join with the outer range, making one single conditional format with solid range. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117962] FILESAVE one touche [save filter]
https://bugs.documentfoundation.org/show_bug.cgi?id=117962 --- Comment #3 from thinkedsfoxe --- and we tried macro recorder. but libreoffice and libreoffice dev is can't macro record. toolbar icon can't click. and can't record. we don't know why can't it. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117962] FILESAVE one touche [save filter]
https://bugs.documentfoundation.org/show_bug.cgi?id=117962 thinkedsfoxe changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from thinkedsfoxe --- (In reply to Jean-Baptiste Faure from comment #1) > Your request is not clear for me. > > > want other filter. > > which one ? > > > make macro? > > difficult. > > Did you try macro recording? > > Status set to NEEDINFO, please set it back to UNCONFIRMED once requested > informations are provided. > > Best regards. JBF sorry. we made your confused. we say meaning. want other filter. = we want other filter. with not default selected extension. what extension = png we tired to repeat select and click. export for png. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'feature/print_revamp' - vcl/inc vcl/source vcl/uiconfig
vcl/inc/printdlg.hxx | 23 + vcl/source/window/printdlg.cxx | 616 - vcl/uiconfig/ui/printdialog.ui | 15 3 files changed, 641 insertions(+), 13 deletions(-) New commits: commit e0c9aaf19bed5a38ecb2748008d02b5c88a7ff26 Author: Daniel Date: Fri Jun 8 00:26:21 2018 -0300 Reinserts optional UI options into print dialog Change-Id: I9ee0e250ea476aa546b842cbd45fff8ea208cfe5 Reviewed-on: https://gerrit.libreoffice.org/55450 Tested-by: Jenkins Reviewed-by: Daniel Silva diff --git a/vcl/inc/printdlg.hxx b/vcl/inc/printdlg.hxx index 03e01b840003..2baa21dc53d3 100644 --- a/vcl/inc/printdlg.hxx +++ b/vcl/inc/printdlg.hxx @@ -28,6 +28,7 @@ #include #include #include +#include #include #include #include @@ -104,9 +105,12 @@ namespace vcl private: +std::unique_ptr mpCustomOptionsUIBuilder; + std::shared_ptr maPController; VclPtr mpTabCtrl; +VclPtrmpPageLayoutFrame; VclPtr mpPrinters; VclPtr mpStatusTxt; VclPtr mpSetupButton; @@ -165,30 +169,47 @@ namespace vcl /// border around each page VclPtrmpBorderCB; -std::map< VclPtr, OUString > maControlToPropertyMap; +std::map< VclPtr, OUString > +maControlToPropertyMap; +std::map< OUString, std::vector< VclPtr > > +maPropertyToWindowMap; +std::map< VclPtr, sal_Int32 > +maControlToNumValMap; +std::set< OUString >maReverseDependencySet; SizemaNupPortraitSize; SizemaNupLandscapeSize; /// internal, used for automatic Nup-Portrait/landscape SizemaFirstPageSize; +boolmbShowLayoutFrame; + DECL_LINK( ClickHdl, Button*, void ); DECL_LINK( SelectHdl, ListBox&, void ); DECL_LINK( ModifyHdl, Edit&, void ); DECL_LINK( ToggleHdl, CheckBox&, void ); DECL_LINK( ToggleRadioHdl, RadioButton&, void ); +DECL_LINK( UIOption_CheckHdl, CheckBox&, void ); +DECL_LINK( UIOption_RadioHdl, RadioButton&, void ); +DECL_LINK( UIOption_SelectHdl, ListBox&, void ); +DECL_LINK( UIOption_ModifyHdl, Edit&, void ); + css::beans::PropertyValue* getValueForWindow( vcl::Window* ) const; void preparePreview( bool i_bPrintChanged = true, bool i_bMayUseCache = false ); void setPreviewText(); void updatePrinterText(); void checkControlDependencies(); +void checkOptionalControlDependencies(); +void makeEnabled( vcl::Window* ); +void updateWindowFromProperty( const OUString& ); void initFromMultiPageSetup( const vcl::PrinterController::MultiPageSetup& ); void showAdvancedControls( bool ); void updateNup(); void updateNupFromPages(); void enableNupControls( bool bEnable ); +void setupOptionalUI(); Size const & getJobPageSize(); }; diff --git a/vcl/source/window/printdlg.cxx b/vcl/source/window/printdlg.cxx index 06f3ed8470f0..967b88335b09 100644 --- a/vcl/source/window/printdlg.cxx +++ b/vcl/source/window/printdlg.cxx @@ -482,8 +482,8 @@ Size const & PrintDialog::getJobPageSize() } PrintDialog::PrintDialog(vcl::Window* i_pWindow, const std::shared_ptr& i_rController) - : ModalDialog(i_pWindow, "PrintDialog", "vcl/ui/printdialog.ui") +, mpCustomOptionsUIBuilder(nullptr) , maPController( i_rController ) , maPrintToFileText( VclResId( SV_PRINT_TOFILE_TXT ) ) , maDefPrtText( VclResId( SV_PRINT_DEFPRT_TXT ) ) @@ -494,11 +494,14 @@ PrintDialog::PrintDialog(vcl::Window* i_pWindow, const std::shared_ptrgetMultipage() ); +// setup optional UI options set by application +setupOptionalUI(); + +// hide layout frame if unwanted +mpPageLayoutFrame->Show( mbShowLayoutFrame ); + // setup click hdl mpOKButton->SetClickHdl(LINK(this, PrintDialog, ClickHdl)); mpCancelButton->SetClickHdl(LINK(this, PrintDialog, ClickHdl)); @@ -618,7 +627,6 @@ PrintDialog::PrintDialog(vcl::Window* i_pWindow, const std::shared_ptrSetToggleHdl( LINK( this, PrintDialog, ToggleHdl ) ); mpCollateBox->SetToggleHdl( LINK( this, PrintDialog, ToggleHdl ) ); mpPagesBtn->SetToggleHdl( LINK( this, PrintDialog, ToggleRadioHdl ) ); -mpBrochureBtn->SetToggleHdl( LINK( this, PrintDialog, ToggleRadioHdl ) ); // setup select hdl mpPrinters->SetSelectHdl( LINK( this, PrintDialog, SelectHdl ) ); @@ -643,8 +651,9 @@ PrintDialog::~PrintDialog() void
[Libreoffice-bugs] [Bug 117937] EDITING crash. fit text to a frame and add to groupe
https://bugs.documentfoundation.org/show_bug.cgi?id=117937 thinkedsfoxe 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117937] EDITING crash. fit text to a frame and add to groupe
https://bugs.documentfoundation.org/show_bug.cgi?id=117937 --- Comment #16 from thinkedsfoxe --- and this is crash with libreoffice dev draw too. we used many time, but we researched. so, this bug with other distro to crash too? answer, yes. searched proviso is only kde desktop. kde neon = maui plasma 5 = ubuntu studio + plasma desktop if customize toolbar use, is crash in all cases. we not now use text to fit. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117937] EDITING crash. fit text to a frame and add to groupe
https://bugs.documentfoundation.org/show_bug.cgi?id=117937 --- Comment #15 from thinkedsfoxe --- Created attachment 142762 --> https://bugs.documentfoundation.org/attachment.cgi?id=142762=edit crash-sample-libredraw.m4v exsample crash with libre customize toolbar. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117937] EDITING crash. fit text to a frame and add to groupe
https://bugs.documentfoundation.org/show_bug.cgi?id=117937 --- Comment #14 from thinkedsfoxe --- sorry to use many time. we made example movie. atatthed. crash-sample-libredraw.m4v -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118088] Installing SmART extension is aborted
https://bugs.documentfoundation.org/show_bug.cgi?id=118088 --- Comment #8 from Volga --- (In reply to Timur from comment #6) > https://wiki.documentfoundation.org/Extensions/SmART_Gallery: > Please remove all previous version of Diagram and SmART gallery. They cause > compatibility problems > Or please reset the profile. > This is for Draw and Impress only. > > Extension page is not availble: http://ooop.sf.net/ Yes, I reset the profile, but the icon become gray after I install this extension. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118088] Installing SmART extension is aborted
https://bugs.documentfoundation.org/show_bug.cgi?id=118088 --- Comment #7 from Volga --- (In reply to Timur from comment #6) > https://wiki.documentfoundation.org/Extensions/SmART_Gallery: > Please remove all previous version of Diagram and SmART gallery. They cause > compatibility problems > Or please reset the profile. > This is for Draw and Impress only. > > Extension page is not availble: http://ooop.sf.net/ Yes, I reset the profile, but the icon become gray. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Bug 108253 depends on bug 91801, which changed state. Bug 91801 Summary: Calculations in tables with variables would cut off part of the calculation upon print https://bugs.documentfoundation.org/show_bug.cgi?id=91801 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118176] New: Show the Unicode in wrong size...
https://bugs.documentfoundation.org/show_bug.cgi?id=118176 Bug ID: 118176 Summary: Show the Unicode in wrong size... Product: LibreOffice Version: 5.4.7.1 rc Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rmbe...@gmail.com Use this strings: And change the size and fonts type... have fun... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/uiwriter/data/tdf91801.fodt | 21 +
sw/qa/extras/uiwriter/uiwriter.cxx | 11 +++
sw/source/core/bastyp/calc.cxx |2 ++
3 files changed, 34 insertions(+)
New commits:
commit 82fc1fdebc622507d4220fefa72b9b4bda0f55d8
Author: Mike Kaganski
Date: Thu Jun 14 20:25:26 2018 +1000
tdf#91801: also restore command (formula) string on validating value
SwUserFieldType::GetValue calls SwCalc::Calculate on this object, which
resets own m_sCommand to the variable name being verified. Restore it
after calculations, like other values.
Change-Id: I1582fa2d356064e6e951063fa8479cd615a6591a
Reviewed-on: https://gerrit.libreoffice.org/55789
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/qa/extras/uiwriter/data/tdf91801.fodt
b/sw/qa/extras/uiwriter/data/tdf91801.fodt
new file mode 100755
index ..4d5486f71bbb
--- /dev/null
+++ b/sw/qa/extras/uiwriter/data/tdf91801.fodt
@@ -0,0 +1,21 @@
+
+
+http://openoffice.org/2004/writer; office:version="1.2"
office:mimetype="application/vnd.oasis.opendocument.text">
+
+
+
+
+
+
+
+
+
+
+ 111
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/sw/qa/extras/uiwriter/uiwriter.cxx
b/sw/qa/extras/uiwriter/uiwriter.cxx
index 924ff04f6911..d2086048ad94 100644
--- a/sw/qa/extras/uiwriter/uiwriter.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter.cxx
@@ -342,6 +342,7 @@ public:
void testHtmlCopyImages();
void testTdf116789();
void testTdf117225();
+void testTdf91801();
CPPUNIT_TEST_SUITE(SwUiWriterTest);
CPPUNIT_TEST(testReplaceForward);
@@ -535,6 +536,7 @@ public:
CPPUNIT_TEST(testHtmlCopyImages);
CPPUNIT_TEST(testTdf116789);
CPPUNIT_TEST(testTdf117225);
+CPPUNIT_TEST(testTdf91801);
CPPUNIT_TEST_SUITE_END();
private:
@@ -6232,6 +6234,15 @@ void SwUiWriterTest::testTdf117225()
CPPUNIT_ASSERT_EQUAL(nExpected, nActual);
}
+void SwUiWriterTest::testTdf91801()
+{
+// Tests calculation with several user field variables without prior user
fields
+createDoc("tdf91801.fodt");
+uno::Reference xTable(getParagraphOrTable(1),
uno::UNO_QUERY);
+uno::Reference xCell(xTable->getCellByName("A1"));
+CPPUNIT_ASSERT_EQUAL(555.0, xCell->getValue());
+}
+
CPPUNIT_TEST_SUITE_REGISTRATION(SwUiWriterTest);
CPPUNIT_PLUGIN_IMPLEMENT();
diff --git a/sw/source/core/bastyp/calc.cxx b/sw/source/core/bastyp/calc.cxx
index 30a1ca83a5ab..1e407f8a0225 100644
--- a/sw/source/core/bastyp/calc.cxx
+++ b/sw/source/core/bastyp/calc.cxx
@@ -449,6 +449,7 @@ SwCalcExp* SwCalc::VarLook( const OUString& rStr, bool bIns
)
sal_Int32 nCommandPos = m_nCommandPos;
SwCalcOper eCurrOper = m_eCurrOper;
SwCalcOper eCurrListOper = m_eCurrListOper;
+OUString sCurrCommand = m_sCommand;
pFnd->nValue.PutDouble( pUField->GetValue( *this ) );
@@ -459,6 +460,7 @@ SwCalcExp* SwCalc::VarLook( const OUString& rStr, bool bIns
)
m_nCommandPos = nCommandPos;
m_eCurrOper = eCurrOper;
m_eCurrListOper = eCurrListOper;
+m_sCommand = sCurrCommand;
}
else
{
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 108660] [META] Formula bar (input line) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108660 Thomas Lendo changed: What|Removed |Added Depends on||90698 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=90698 [Bug 90698] CALC: EDITING: formula: tries to guess what I meant without saying it's editing it -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 90698] CALC: EDITING: formula: tries to guess what I meant without saying it's editing it
https://bugs.documentfoundation.org/show_bug.cgi?id=90698 Thomas Lendo changed: What|Removed |Added Blocks||108660 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108660 [Bug 108660] [META] Formula bar (input line) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Thomas Lendo changed: What|Removed |Added Depends on||99769 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99769 [Bug 99769] export to SVG drops some text -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99769] export to SVG drops some text
https://bugs.documentfoundation.org/show_bug.cgi?id=99769 Thomas Lendo changed: What|Removed |Added Blocks||111450 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=111450 [Bug 111450] [META] SVG fileSave filter (Draw) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118020] long unresponsive time
https://bugs.documentfoundation.org/show_bug.cgi?id=118020 --- Comment #4 from mbagb...@gmail.com --- It sounds like I either have to risk loosing all the words added to the spell check dictionary to revert to an earlier version that didn't have the delay or go back to Open Office - is that correct? Or is there some other way I can get Lebre Office to work and not have to wait so long? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117572] Ubuntu upgrade to 18.04 adversely affecting some Libreoffice programs
https://bugs.documentfoundation.org/show_bug.cgi?id=117572 Roger Jarvis changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #6 from Roger Jarvis --- The problem behaviour is exactly the same in safe mode as in normal mode - the WIKI guidance says this means the problem is not caused by the profile, so I did not reset anything. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108542] [META] Chart label bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108542 Thomas Lendo changed: What|Removed |Added Depends on||117992 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=117992 [Bug 117992] Chart labels truncated if chart area resized and then container resized -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117992] Chart labels truncated if chart area resized and then container resized
https://bugs.documentfoundation.org/show_bug.cgi?id=117992 Thomas Lendo changed: What|Removed |Added Blocks||108542 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108542 [Bug 108542] [META] Chart label bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113300] [META] Language detection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113300 Thomas Lendo changed: What|Removed |Added Depends on||117540 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=117540 [Bug 117540] Updating language of an ods file is not possible -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117540] Updating language of an ods file is not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=117540 Thomas Lendo changed: What|Removed |Added Blocks||113300 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113300 [Bug 113300] [META] Language detection bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99672] Replace All with format in search and empty replace text does not replace.
https://bugs.documentfoundation.org/show_bug.cgi?id=99672 Thomas Lendo changed: What|Removed |Added Blocks||102847 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 Thomas Lendo changed: What|Removed |Added Depends on||99672 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99672 [Bug 99672] Replace All with format in search and empty replace text does not replace. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118174] Replace All doesn't work with an empty string/blank and formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=118174 Thomas Lendo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lendo --- Thanks for your report, David. Seems to be a duplicate of an already filed bug. *** This bug has been marked as a duplicate of bug 99672 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99672] Replace All with format in search and empty replace text does not replace.
https://bugs.documentfoundation.org/show_bug.cgi?id=99672 Thomas Lendo changed: What|Removed |Added CC||davidkbol...@gmail.com --- Comment #3 from Thomas Lendo --- *** Bug 118174 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106340] Buttons overlap other buttons when assigning Format options in Find & Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=106340 Thomas Lendo changed: What|Removed |Added CC||davidkbol...@gmail.com --- Comment #7 from Thomas Lendo --- *** Bug 118175 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118175] UI: Buttons overlap in replace dialog if you add formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=118175 Thomas Lendo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thomas Lendo --- Thanks for your report. *** This bug has been marked as a duplicate of bug 106340 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] online.git: Changes to 'feature/anonymization-cd'
New branch 'feature/anonymization-cd' available with the following commits: commit ebad920342ccf7bee44f6d71ed9475a3772e742f Author: Ashod Nakashian Date: Sun Jun 10 22:40:32 2018 -0400 wsd: anonymize saveas Change-Id: I58e349781952a97c3251b0e52e26abb34d44e9c0 commit 43d4381f72d45fd3a0b0f2752ad0fbbc48e04b92 Author: Ashod Nakashian Date: Sun Jun 10 22:30:42 2018 -0400 wsd: anonymize downloadas Change-Id: I6dff7189d78d339f1f5db7afef2b62da4df23759 commit b659c346533192d213e6b4229fe5ba275ac62029 Author: Ashod Nakashian Date: Sun Jun 10 20:55:52 2018 -0400 wsd: anonymize document saving Change-Id: Ic819883e39a544ec16d6ac144a08ed9f9f568cc0 commit 69a3304e214f7d51d4e9050687cf1e63cc39de1a Author: Ashod Nakashian Date: Sun Jun 10 20:24:04 2018 -0400 wsd: anonymize jailed filename Change-Id: I0af46ae6779caf9851e3142889940e4f774f9eb9 commit 6b0534341453d50b03bb3eab4a9cf08fe9e5c984 Author: Ashod Nakashian Date: Sun Jun 10 14:02:02 2018 -0400 kit: anonymize usernames and filenames in Kit Change-Id: Id7928136db71ded7bf6b1a5e8e387db7251f8a35 commit a56785820a240348105dabc95754b93b3b76fbe1 Author: Ashod Nakashian Date: Sun Jun 10 11:42:15 2018 -0400 wsd: anonymize WOPI::CheckFileInfo Change-Id: I2c23e9f159456176ae85967cc49ec876b1e4ecf4 commit a4bcc514abc9a0b5d719b820041c33a0f0a3299f Author: Ashod Nakashian Date: Sun Jun 10 13:53:39 2018 -0400 kit: parse anonymized tokens in doc options Also optimize the parsing in general. Change-Id: Id1f5b5c12e867c98e523d1e32397853d7d4a6ee4 commit f3e8ee4d98e7f2d011026759eb2336cfe84b8a07 Author: Ashod Nakashian Date: Sun Jun 10 11:41:17 2018 -0400 wsd: anonymize load command sent to Kit Change-Id: Ic509ceb5c38bc50152f1d00bd5718089fe664ac1 commit 563c4336dfd01aa351fdc90fa49b2d8c67181c61 Author: Ashod Nakashian Date: Sun Jun 10 11:35:59 2018 -0400 wsd: add anonymization helpers Change-Id: Ic479218ab1b6e580c288a984f35795e1d0d6e8ad commit 7b32abe4cc0d4fd2dc7ced2b83537acbc1a9017d Author: Ashod Nakashian Date: Wed Jun 6 21:34:51 2018 -0400 wsd: demote socket write logs to trace level They are only informative when the actual data is also logged, which is on the trace-level only. Change-Id: I7e45f2a4f14638783a65cb3a4eb132438d9125b8 commit b402d051826c4bc6c35475f812b1ab6e80db6a96 Author: Ashod Nakashian Date: Sun Jun 3 21:01:47 2018 -0400 wsd: disable tracing after initialization The first child had tracing enabled even after initial startup is completed. This would leak user details when anonymization is enabled. Change-Id: I5325e02d1a1078bff6640af85f5672b556c00aeb commit a5f388be538b132f5e4bfd6d6a1c02d411c1dece Author: Ashod Nakashian Date: Sun Jun 3 18:17:33 2018 -0400 wsd: support anonymization settings Check and fail to start if anonymization is enabled and trace-level logging is requested. Since trace may include data packets, which is hard to anonymize and is likely to impact performance if attempted, it is best to prevent tracing altogether. Also, sort the default settings for better readability. Change-Id: Ic83f1f2fda15e2146a5d970f03617fa460d9cbc7 commit a2e7d9b4da1f84765348d9a674a410d23c1e7bc7 Author: Ashod Nakashian Date: Sun Jun 3 14:02:44 2018 -0400 wsd: anonymization config and settings for username/filename Change-Id: I9d7ce87b5f7d204b503d467959de008326b3411c commit 47b36481b5d5bf340262e351ef1dadab70b7547e Author: Ashod Nakashian Date: Mon Jun 4 16:47:39 2018 -0400 wsd: always use signal-safe calls The async-signal-safe functions to get thread-id and thread-name, which cache the results, are faster, cleaner, and signal-safe. No reason why we shouldn't always use them. Especially since it appears the logic was inverted in Log::prefix, such that the signal un-safe calls were made during signal-handling, and the safe ones were called otherwise! Instead of passing the signal-safe flag to Log::prefix, we pass the buffer size, for improved security. Furthermore, reduce header dependencies and reduce clutter. Change-Id: I697689b2f0a290b6d8cce4babc3ac1e576141da6 commit 6368fb97429c0d161dc7884b374df41fa886895d Author: Ashod Nakashian Date: Mon Jun 4 10:23:58 2018 -0400 wsd: clang-format logging macros and pass logger explicitly Change-Id: I37e7f4b5687b64b36e0985942627a4b84a8249eb commit cf3797be20d1134315af81f20c135910a6673eab Author: Ashod Nakashian Date: Sun Feb 11 15:40:28 2018 -0500 kit: makeRenderParams now static Change-Id: I1c79991a73044a91ed9f8389e23ccffd8b2bcbce Reviewed-on: https://gerrit.libreoffice.org/49572 Reviewed-by: Ashod Nakashian Tested-by: Ashod Nakashian commit 1cb04cc5f8f7f72562f5d31c01d6cd53a96a06c7 Author: Ashod Nakashian
[Libreoffice-bugs] [Bug 118159] Entering a unicode code point crashes calc
https://bugs.documentfoundation.org/show_bug.cgi?id=118159 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #9 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I don't reproduce the crash. I just noticed these kind of logs on console: warn:svx:19691:19691:svx/source/accessibility/AccessibleTextHelper.cxx:1403: DBG_UNHANDLED_EXCEPTION in virtual void accessibility::AccessibleTextHelper_Impl::Notify(SfxBroadcaster&, const SfxHint&) type: com.sun.star.uno.RuntimeException message: Text forwarder is invalid, model might be dead context: ScAccessibleEditObject Do you use accessibility tools or did you enable some of them? (eg: Orca) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118175] New: UI: Buttons overlap in replace dialog if you add formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=118175 Bug ID: 118175 Summary: UI: Buttons overlap in replace dialog if you add formatting Product: LibreOffice Version: 6.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: davidkbol...@gmail.com Created attachment 142761 --> https://bugs.documentfoundation.org/attachment.cgi?id=142761=edit Shows the buttons overlapping in Find and Replace dialog Steps to reproduce: 1. Open Writer 2. Choose Edit > Find & Replace 3. Choose Other options > Format > Italic > OK Expected behavior: None of the buttons should overlap Actual behavior: The "Attributes" and "No Format" buttons overlap with the buttons below them. (I'm on Windows 10 Pro) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118022] Crash when searching record in a form of an external MySQL-database (JDBC-connection)
https://bugs.documentfoundation.org/show_bug.cgi?id=118022 Julien Nabet changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED --- Comment #22 from Julien Nabet --- I submitted this patch for review: https://gerrit.libreoffice.org/#/c/55836/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118174] New: Replace All doesn't work with an empty string/blank and formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=118174
Bug ID: 118174
Summary: Replace All doesn't work with an empty string/blank
and formatting
Product: LibreOffice
Version: 6.0.0.3 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: davidkbol...@gmail.com
Steps to reproduce
1. Copy the sample text into a new Writer document
2. Format some of the sample lines italic
3. Choose Edit > Find & Replace
4. Under Find type: 3
5. Choose Other Options > Format... > Italic > OK
6. Choose Replace All
Expected behavior:
It should delete all the matching 3's
Actual behavior:
It highlights the 3's but doesn't delete ("replace") them
Sample text:
23ruh
2436
34g
h3
34h
35
h2q3
3h54
(I'm on version 6.0.0.3, Windows 10)
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 101736] standard keyboard shortcut to increase / decrease indent on macOS (macOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=101736 eisa01 changed: What|Removed |Added CC||eis...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Severity|normal |enhancement --- Comment #3 from eisa01 --- I guess this feature request needs input from the UX team? I had a look on the Shortcut keys help file, and there doesn't seem to be any support for this on other platforms either https://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 101736] standard keyboard shortcut to increase / decrease indent on macOS (macOS only)
https://bugs.documentfoundation.org/show_bug.cgi?id=101736 eisa01 changed: What|Removed |Added CC||eis...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Severity|normal |enhancement --- Comment #3 from eisa01 --- I guess this feature request needs input from the UX team? I had a look on the Shortcut keys help file, and there doesn't seem to be any support for this on other platforms either https://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-commits] online.git: TODO
TODO |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit b88b7d3aff12f6de5e592cd9e03889f5835ce718 Author: Andras Timar Date: Thu Jun 14 23:35:53 2018 +0200 typo fix Change-Id: I6a7cc26ff19ece8e2711062bd9a732ebab7b764f diff --git a/TODO b/TODO index 0c993315b..3fdb40423 100644 --- a/TODO +++ b/TODO @@ -2,7 +2,7 @@ - Add a document part number parameter to the protocol where appropriate. Needed at least for the key, mouse, selecttext and - selectgrahic client->server messages. Probably also the LOK + selectgraphic client->server messages. Probably also the LOK callback server->client messages. - Have MasterProcessSession::dispatchChild() wait for a child process ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 118159] Entering a unicode code point crashes calc
https://bugs.documentfoundation.org/show_bug.cgi?id=118159 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu --- Comment #8 from V Stuart Foote --- The Ctrl+Shift+U[unicodepoint] is a gtk+ control (see GtkIMContext), is there an input method conflict with the gtk3? Otherwise as implemented for bug 73691 LibreOffice's default cross platform entry method for the Unicode string toggle is +x, That is 1. focus in cell 2. type U+00d7 leaving cursor at end of string entry 3. type +x a second +x will toggle back to the input string. Any glyph in text can be toggled in all LO modules. Some adjustments of the +x toggle were made for keyboard needs of several locales +c to toggle, and macOS required a different three key -- CMD+Option+x (aka X_MOD1_MOD2) toggle. Does +x toggle crash? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 99520, which changed state. Bug 99520 Summary: 5.0.5.2 Crashed on saving "Untitled 1" documents and they're gone https://bugs.documentfoundation.org/show_bug.cgi?id=99520 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99520] 5.0.5.2 Crashed on saving "Untitled 1" documents and they're gone
https://bugs.documentfoundation.org/show_bug.cgi?id=99520 eisa01 changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #5 from eisa01 --- I can save unnamed documents, and also recover unsaved document in latest master Resolving as works for me Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118022] Crash when searching record in a form of an external MySQL-database (JDBC-connection)
https://bugs.documentfoundation.org/show_bug.cgi?id=118022 --- Comment #21 from Julien Nabet --- Created attachment 142760 --> https://bugs.documentfoundation.org/attachment.cgi?id=142760=edit bt with debug symbols It seems there are 2 throws of SQLException, the first one is dealt not the second one. Here's the second one. (if I well understood) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 64980] ordered list with subbullets does an unexpected indentation to the left when moving text
https://bugs.documentfoundation.org/show_bug.cgi?id=64980 Preben Ellebye changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #13 from Preben Ellebye --- On windows 10 LibreOffice 6.0.4.2 (x64) the bug is not present. Build-ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU-tråde: 4; Styresystem: Windows 10.0; Gengiver af brugergrænseflade: Standard; Lokalitet: da-DK (da_DK); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 82293] Cancelling input method pre-editing and then undoing breaks the input method and/or crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=82293 eisa01 changed: What|Removed |Added Hardware|Other |x86-64 (AMD64) Priority|medium |low Severity|normal |trivial Version|4.3.0.4 release |Inherited From OOo --- Comment #7 from eisa01 --- This is still present, but I'm not seeing any crash. Tested with Hiragana input method Note, on step 3, press Esc twice to cancel the Japanese input Lowering importance as this is quite an edge case, I can not remember ever trying something similar while writing English. Was also present on LO 3.3, so inherited Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] online.git: Branch 'feature/latency' - loleaflet/src
loleaflet/src/layer/tile/GridLayer.js |6 --
1 file changed, 6 deletions(-)
New commits:
commit 73d16b87675b3290ddbe13f5201b3f5dff646421
Author: Tamás Zolnai
Date: Thu Jun 14 23:13:37 2018 +0200
Remove these unneccessary updates
Change-Id: Idfe0c99036741c0e5f2bdda84ac71a47ae3229f6
diff --git a/loleaflet/src/layer/tile/GridLayer.js
b/loleaflet/src/layer/tile/GridLayer.js
index 660d2c297..8b613b631 100644
--- a/loleaflet/src/layer/tile/GridLayer.js
+++ b/loleaflet/src/layer/tile/GridLayer.js
@@ -687,12 +687,6 @@ L.GridLayer = L.Layer.extend({
this._level.el.appendChild(fragment);
}
-
- this._invalidateClientVisibleArea();
- this._sendClientVisibleArea();
-
- this._updateClientZoom();
- this._sendClientZoom();
},
_invalidateClientVisibleArea: function() {
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: svgio/source sw/qa
svgio/source/svgreader/svgstyleattributes.cxx |6 +++---
svgio/source/svgreader/svgsvgnode.cxx |2 +-
sw/qa/uitest/writer_tests/wordCount.py|6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
New commits:
commit 213a644a121a1b4145f5abe35c9b2f10ea00ac89
Author: Andrea Gelmini
Date: Wed Jun 13 23:58:06 2018 +0200
Fix typos
Change-Id: I69b4f139be269ff58acd9d74ce0c7897e84a9419
Reviewed-on: https://gerrit.libreoffice.org/55774
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/svgio/source/svgreader/svgstyleattributes.cxx
b/svgio/source/svgreader/svgstyleattributes.cxx
index 2d96cfb9d022..7cc0a05b 100644
--- a/svgio/source/svgreader/svgstyleattributes.cxx
+++ b/svgio/source/svgreader/svgstyleattributes.cxx
@@ -2255,14 +2255,14 @@ namespace svgio
// Visibility correction/exception for self-exported SVGs:
// When Impress exports single or multi-page SVGs, it puts the
// single slides into . Not sure why
-// whis happens, but this leads (correctly) to empty imported
+// this happens, but this leads (correctly) to empty imported
// Graphics.
// Thus, if Visibility_hidden is active and owner is a SVGTokenG
// and it's parent is also a SVGTokenG and it has a Class
'SlideGroup'
// set, check if we are an Impress export.
// We are an Impress export if an SVG-Node titled 'ooo:meta_slides'
// exists.
-// All togehter gives:
+// All together gives:
if(Visibility_hidden == maVisibility
&& SVGTokenG == mrOwner.getType()
&& nullptr !=
mrOwner.getDocument().findSvgNodeById("ooo:meta_slides"))
@@ -2276,7 +2276,7 @@ namespace svgio
if("SlideGroup" == aClass)
{
// if we detect this exception,
-// ovverride Visibility_hidden -> Visibility_visible
+// override Visibility_hidden -> Visibility_visible
return Visibility_visible;
}
}
diff --git a/svgio/source/svgreader/svgsvgnode.cxx
b/svgio/source/svgreader/svgsvgnode.cxx
index 524e6d360030..be2bc31ced09 100644
--- a/svgio/source/svgreader/svgsvgnode.cxx
+++ b/svgio/source/svgreader/svgsvgnode.cxx
@@ -675,7 +675,7 @@ namespace svgio
// If no Width/Height is set (usually done in
// )
which
// is the case for own-Impress-exports, assume that
-// the Units are alrteady 100ThMM.
+// the Units are already 100ThMM.
// Maybe only for own-Impress-exports, thus may
need to be
// & with
getDocument().findSvgNodeById("ooo:meta_slides"),
// but does not need to be.
diff --git a/sw/qa/uitest/writer_tests/wordCount.py
b/sw/qa/uitest/writer_tests/wordCount.py
index da0dedbcc000..a546e78cfbf5 100644
--- a/sw/qa/uitest/writer_tests/wordCount.py
+++ b/sw/qa/uitest/writer_tests/wordCount.py
@@ -198,7 +198,7 @@ class writerWordCount(UITestCase):
xWriterEdit.executeAction("SELECT", mkPropertyValues({"START_POS":
"9", "END_POS": "10"}))
#5. Replace selection by a non-breaking space by pressing
Shift+Ctrl+Space. Don't move the cursor.
self.xUITest.executeCommand(".uno:InsertNonBreakingSpace")
-# Word count in dialogue shows 4 words, wheras in the status line it
shows 5 words.
+# Word count in dialogue shows 4 words, whereas in the status line
it shows 5 words.
self.ui_test.execute_modeless_dialog_through_command(".uno:WordCountDialog")
xDialog = self.xUITest.getTopFocusWindow()
@@ -283,7 +283,7 @@ class writerWordCount(UITestCase):
##4. Click after "At nunc" then
#self.xUITest.executeCommand(".uno:StartOfParaSel")
#sleep(3) #need to wait, because Word count dialog is already open
and it takes time to refresh the counter
-##Expected result : Words 2 & Characters 7 & excludind space 6
#Actual result : Words 0 & Characters 0
+##Expected result : Words 2 & Characters 7 & excluding space 6
#Actual result : Words 0 & Characters 0
#self.assertEqual(get_state_as_dict(xselectwords)["Text"], "2")
#self.assertEqual(get_state_as_dict(xselectchars)["Text"], "7")
#self.assertEqual(get_state_as_dict(xselectcharsnospaces)["Text"], "6")
@@ -291,4 +291,4 @@ class writerWordCount(UITestCase):
#xCloseBtn = xDialog.getChild("close")
#self.ui_test.close_dialog_through_button(xCloseBtn)
#self.ui_test.close_doc()
-# vim: set shiftwidth=4 softtabstop=4 expandtab:
\ No newline at end of file
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
[Libreoffice-commits] core.git: Branch 'libreoffice-6-0' - sc/source
sc/source/core/tool/interpr6.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 32bcda269b07a88cecbb5a2fde10d4b4d7ce7538
Author: Eike Rathke
Date: Thu Jun 14 15:00:14 2018 +0200
Resolves: tdf#118161 use ScCellIterator::isEmpty() for COUNTA()
... instead of hasEmptyData() that considers inherited svEmptyCell
as well.
Effectively a regression from
commit 0e9e3be6f51436c1e5bf1481a434a85e334c09ea
CommitDate: Tue Mar 26 01:41:17 2013 -0400
More on ScCellIterator usage migration.
that started to include mpCurFormula->IsEmpty() in
ScCellIterator::isEmpty() which later was renamed to
ScCellIterator::hasEmptyData() and isEmpty() introduced for real
empty.
Change-Id: Iec97d58080016c28bc9a7e47d056e4d301263928
(cherry picked from commit cfe2e4eb835c06b24adabd60c7a3fddbd3f4dbc9)
Reviewed-on: https://gerrit.libreoffice.org/55804
Tested-by: Jenkins
Reviewed-by: Kohei Yoshida
diff --git a/sc/source/core/tool/interpr6.cxx b/sc/source/core/tool/interpr6.cxx
index 449375638cb5..c93511e23444 100644
--- a/sc/source/core/tool/interpr6.cxx
+++ b/sc/source/core/tool/interpr6.cxx
@@ -809,7 +809,7 @@ void ScInterpreter::IterateParameters( ScIterFunc eFunc,
bool bTextAsZero )
ScCellIterator aIter( pDok, aRange, mnSubTotalFlags );
for (bool bHas = aIter.first(); bHas; bHas = aIter.next())
{
-if ( !aIter.hasEmptyData() )
+if ( !aIter.isEmpty() )
{
++nCount;
}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 59163] FILESAVE: Mac proxy icon isn't displayed after first saving a document
https://bugs.documentfoundation.org/show_bug.cgi?id=59163 eisa01 changed: What|Removed |Added Hardware|Other |x86-64 (AMD64) Priority|medium |low Severity|normal |trivial Version|3.6.4.3 release |Inherited From OOo --- Comment #7 from eisa01 --- This is still present, also inherited Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on OS X
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Bug 42082 depends on bug 63094, which changed state. Bug 63094 Summary: EDITING: Pasting text copied from MS Word (Mac) inserts text plus multiple comments containing XML https://bugs.documentfoundation.org/show_bug.cgi?id=63094 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 63094] EDITING: Pasting text copied from MS Word (Mac) inserts text plus multiple comments containing XML
https://bugs.documentfoundation.org/show_bug.cgi?id=63094 eisa01 changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #12 from eisa01 --- This works for me now Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 62621] Synonyms do not show up for words that have a period at the end.
https://bugs.documentfoundation.org/show_bug.cgi?id=62621 eisa01 changed: What|Removed |Added Priority|medium |low Severity|minor |trivial --- Comment #13 from eisa01 --- Still present. Functionality was not in LO 3.3 Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79460] EDITING: OSX - Select all shortcut jumps to beginning of footer paragraph in particular Word document
https://bugs.documentfoundation.org/show_bug.cgi?id=79460 eisa01 changed: What|Removed |Added Version|4.2.4.2 release |Inherited From OOo --- Comment #18 from eisa01 --- This is still present, also inherited from OOo Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116846] Colour profile issues with edit view and PDF export compared to Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=116846 --- Comment #23 from eisa01 --- Created attachment 142759 --> https://bugs.documentfoundation.org/attachment.cgi?id=142759=edit Screenshot LO vs print PDF vs Preview png vs Pages -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116846] Colour profile issues with edit view and PDF export compared to Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=116846 eisa01 changed: What|Removed |Added Ever confirmed|0 |1 Version|6.0.3.2 release |Inherited From OOo Summary|colour profile issues with |Colour profile issues with |edit view and PDF export|edit view and PDF export |compared|compared to Preview Status|UNCONFIRMED |NEW --- Comment #22 from eisa01 --- I can confirm this. The image is not rendered with the same colors if I export as PDF. If I choose print and save as PDF using the in-built macOS system, it is the same color though. Aside, if I do the test on Word I have the exact same behavior. The Word save as PDF produces an oversaturated image as well. However, if I open the png image in Preview, make a Pages document with the image, open the LO odt with the image, open the LO print pdf export, take a screenshot, compare using the color picker in GIMP then LO and the print export does not render the same colors as Preview and Pages Given Apple's history with color profiles I would trust them to have this correct. Does LO have support for color profiles? Looks to be rendered in same colors on LO 3.3 Tested on Lenovo L220x monitor Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en_US.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] online.git: Branch 'distro/collabora/collabora-online-3' - loleaflet/dist scripts/locorestrings.py
loleaflet/dist/l10n/locore/af.json |1 + loleaflet/dist/l10n/locore/am.json |1 + loleaflet/dist/l10n/locore/ar.json |1 + loleaflet/dist/l10n/locore/as.json |1 + loleaflet/dist/l10n/locore/ast.json |1 + loleaflet/dist/l10n/locore/bg.json |1 + loleaflet/dist/l10n/locore/bn-IN.json |1 + loleaflet/dist/l10n/locore/bn.json |1 + loleaflet/dist/l10n/locore/bo.json |1 + loleaflet/dist/l10n/locore/br.json |1 + loleaflet/dist/l10n/locore/brx.json |1 + loleaflet/dist/l10n/locore/bs.json |1 + loleaflet/dist/l10n/locore/ca-valencia.json |1 + loleaflet/dist/l10n/locore/ca.json |1 + loleaflet/dist/l10n/locore/cs.json |1 + loleaflet/dist/l10n/locore/cy.json |1 + loleaflet/dist/l10n/locore/da.json |1 + loleaflet/dist/l10n/locore/de.json |1 + loleaflet/dist/l10n/locore/dgo.json |1 + loleaflet/dist/l10n/locore/dz.json |1 + loleaflet/dist/l10n/locore/el.json |1 + loleaflet/dist/l10n/locore/en-GB.json |1 + loleaflet/dist/l10n/locore/en-ZA.json |1 + loleaflet/dist/l10n/locore/eo.json |1 + loleaflet/dist/l10n/locore/es.json |1 + loleaflet/dist/l10n/locore/et.json |1 + loleaflet/dist/l10n/locore/eu.json |1 + loleaflet/dist/l10n/locore/fa.json |1 + loleaflet/dist/l10n/locore/fi.json |1 + loleaflet/dist/l10n/locore/fr.json |1 + loleaflet/dist/l10n/locore/ga.json |1 + loleaflet/dist/l10n/locore/gd.json |1 + loleaflet/dist/l10n/locore/gl.json |1 + loleaflet/dist/l10n/locore/gu.json |1 + loleaflet/dist/l10n/locore/gug.json |1 + loleaflet/dist/l10n/locore/he.json |1 + loleaflet/dist/l10n/locore/hi.json |1 + loleaflet/dist/l10n/locore/hr.json |1 + loleaflet/dist/l10n/locore/hu.json |1 + loleaflet/dist/l10n/locore/id.json |1 + loleaflet/dist/l10n/locore/is.json |1 + loleaflet/dist/l10n/locore/it.json |1 + loleaflet/dist/l10n/locore/ja.json |1 + loleaflet/dist/l10n/locore/ka.json |1 + loleaflet/dist/l10n/locore/kk.json |1 + loleaflet/dist/l10n/locore/km.json |1 + loleaflet/dist/l10n/locore/kmr-Latn.json|1 + loleaflet/dist/l10n/locore/kn.json |1 + loleaflet/dist/l10n/locore/ko.json |1 + loleaflet/dist/l10n/locore/kok.json |1 + loleaflet/dist/l10n/locore/ks.json |1 + loleaflet/dist/l10n/locore/lb.json |1 + loleaflet/dist/l10n/locore/lo.json |1 + loleaflet/dist/l10n/locore/lt.json |1 + loleaflet/dist/l10n/locore/lv.json |1 + loleaflet/dist/l10n/locore/mai.json |1 + loleaflet/dist/l10n/locore/mk.json |1 + loleaflet/dist/l10n/locore/ml.json |1 + loleaflet/dist/l10n/locore/mn.json |1 + loleaflet/dist/l10n/locore/mni.json |1 + loleaflet/dist/l10n/locore/mr.json |1 + loleaflet/dist/l10n/locore/my.json |1 + loleaflet/dist/l10n/locore/nb.json |1 + loleaflet/dist/l10n/locore/ne.json |1 + loleaflet/dist/l10n/locore/nl.json |1 + loleaflet/dist/l10n/locore/nn.json |1 + loleaflet/dist/l10n/locore/oc.json |1 + loleaflet/dist/l10n/locore/om.json |1 + loleaflet/dist/l10n/locore/or.json |1 + loleaflet/dist/l10n/locore/pa-IN.json |1 + loleaflet/dist/l10n/locore/pl.json |1 + loleaflet/dist/l10n/locore/pt-BR.json |1 + loleaflet/dist/l10n/locore/pt.json |1 + loleaflet/dist/l10n/locore/ro.json |1 + loleaflet/dist/l10n/locore/ru.json |1 + loleaflet/dist/l10n/locore/rw.json |1 + loleaflet/dist/l10n/locore/sa-IN.json |1 + loleaflet/dist/l10n/locore/sat.json |1 + loleaflet/dist/l10n/locore/sd.json |1 + loleaflet/dist/l10n/locore/si.json |1 + loleaflet/dist/l10n/locore/sid.json |1 + loleaflet/dist/l10n/locore/sk.json |1 + loleaflet/dist/l10n/locore/sl.json |1 + loleaflet/dist/l10n/locore/sq.json |1 + loleaflet/dist/l10n/locore/sv.json |1 + loleaflet/dist/l10n/locore/sw-TZ.json |1 + loleaflet/dist/l10n/locore/ta.json |1 + loleaflet/dist/l10n/locore/te.json |1 + loleaflet/dist/l10n/locore/tg.json |1 + loleaflet/dist/l10n/locore/th.json |1 + loleaflet/dist/l10n/locore/tr.json |1 + loleaflet/dist/l10n/locore/ug.json |1 +
Crash test update
New crashtest update available at http://dev-builds.libreoffice.org/crashtest/cc46e7b9c75ddbcaaefde5f396ba76b0b866fa58/ exportCrashes.csv Description: Binary data importCrash.csv Description: Binary data validationErrors.csv Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 118162] Add time limits for spell checking and spelling suggestions
https://bugs.documentfoundation.org/show_bug.cgi?id=118162 László Németh changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |nem...@numbertext.org |desktop.org | Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117608] Unbearable slow layout/UI refresh
https://bugs.documentfoundation.org/show_bug.cgi?id=117608 Telesto 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118173] Text document contains invalid sections, cannot be saved.
https://bugs.documentfoundation.org/show_bug.cgi?id=118173 Dieter Praas changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||dgp-m...@gmx.de --- Comment #2 from Dieter Praas --- Thank you for reporting the bug. Please - could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? - attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version and the requested document is provided.(Please note that the attachment will be public, remove any sensitive information before attaching it) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
