[Libreoffice-bugs] [Bug 155842] The font "Avrile" has 18 styles, I installed all successfully, but I can only see and use one.
https://bugs.documentfoundation.org/show_bug.cgi?id=155842 خالد حسني changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||kha...@libreoffice.org --- Comment #2 from خالد حسني --- You should be able to see all styles from the font tab: https://help.libreoffice.org/latest/en-US/text/shared/01/05020100.html If they are not shown there, please provide more information on how to obtain the font. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142692] Python script connecting to LO instance fails
https://bugs.documentfoundation.org/show_bug.cgi?id=142692 --- Comment #8 from Dan658 --- Hi For install uno execute command: sudo apt-get install libreoffice-script-provider-python Sergey -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa
sw/qa/core/text/text.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit db75a6ecdd39f012fd1237da8169ece21f333b21
Author: Andrea Gelmini
AuthorDate: Wed Jun 14 17:48:32 2023 +0200
Commit: Julien Nabet
CommitDate: Thu Jun 15 07:11:44 2023 +0200
Fix typo
Change-Id: Ieadd5121185e9c3a5258336e3bfece23c1efdc73
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153067
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/sw/qa/core/text/text.cxx b/sw/qa/core/text/text.cxx
index c961562b3c9e..6d71cadcf9ea 100644
--- a/sw/qa/core/text/text.cxx
+++ b/sw/qa/core/text/text.cxx
@@ -1312,7 +1312,7 @@ CPPUNIT_TEST_FIXTURE(SwCoreTextTest,
testFloattableOverlap)
CPPUNIT_TEST_FIXTURE(SwCoreTextTest, testTdf89288)
{
// Given a document with 2 paragraphs of mixed Complex and Western text,
-// and 2 other paragrpahs of mixed Western and Asian text:
+// and 2 other paragraphs of mixed Western and Asian text:
createSwDoc("tdf89288.fodt");
// When laying out that document:
[Libreoffice-bugs] [Bug 62421] Comments added to frames or image caption are placed unconditional at the top
https://bugs.documentfoundation.org/show_bug.cgi?id=62421 Diana Vides changed: What|Removed |Added CC||dianavide...@gmail.com --- Comment #12 from Diana Vides --- This bug is still reproducible in versions: \Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (en_US); UI: en-US Calc: threaded version 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e4c611ddc731d6a2ca9c3de61a02d1d4b6eefa9b CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155385] Crash when opening PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=155385 Duck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Duck --- Quack, 7.5.4.2 is now available in Debian unstable and I just tested it and I can no longer reproduce the crash, this is good news :-). Thanks for your help folks. \_o< -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62991] FILEOPEN existing 3.6.6.1 document: Chart data contents in embedded Calc8 spreadsheet object becomes invisible when EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=62991 --- Comment #12 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155809] Insert comment keyboard shortcut (Ctrl+Alt+C) has no effect with BenQ Display Pilot
https://bugs.documentfoundation.org/show_bug.cgi?id=155809 Filipus Klutiero changed: What|Removed |Added Summary|Insert comment keyboard |Insert comment keyboard |shortcut (Ctrl+Alt+C) has |shortcut (Ctrl+Alt+C) has |no effect |no effect with BenQ Display ||Pilot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155809] Insert comment keyboard shortcut (Ctrl+Alt+C) has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=155809 Filipus Klutiero changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Filipus Klutiero --- Thanks to you Stéphane I am using the CSA layout, which does not assign any character to Alt Car + C : https://fr.wikipedia.org/wiki/CAN/CSA_Z243.200-92#/media/Fichier:KB_Canadian_Multilingual_Standard_comment-fr.svg The only other shortcut using Ctrl+Alt which I can see is the one for the extension manager, Ctrl+Alt+E, which also does not work. However, that is because CAN/CSA has the Euro symbol € on level 3 for E. That being said, I figured out that Ctrl+Alt+C did have an effect, ie removing focus from the window. That is because a utility was globally catching that combination. It is BenQ's Display Pilot which uses that shortcut to switch color mode: https://defkey.com/benq-display-pilot-shortcuts For reference, here are other programs which catch Ctrl+Alt+C: https://defkey.com/what-means/ctrl-alt-c I am not sure what can be done with this issue. Hopefully there is a way for LibreOffice to poll which combinations are globally caught and react appropriately. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65807] Line Numbers in Comments printed "after each page" are continuous (and do not restart after each page)
https://bugs.documentfoundation.org/show_bug.cgi?id=65807 Diana Vides changed: What|Removed |Added CC||dianavide...@gmail.com --- Comment #18 from Diana Vides --- This bug is still present in version 7.5.3.2 Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (en_US); UI: en-US Calc: threaded It is also present in the latest master build Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e4c611ddc731d6a2ca9c3de61a02d1d4b6eefa9b CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155546] [RFE] Add Function Wizard feature to Conditional Format dialog for "Formula is" condition
https://bugs.documentfoundation.org/show_bug.cgi?id=155546 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155608] Set default font easily in settings
https://bugs.documentfoundation.org/show_bug.cgi?id=155608 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155546] [RFE] Add Function Wizard feature to Conditional Format dialog for "Formula is" condition
https://bugs.documentfoundation.org/show_bug.cgi?id=155546 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155529] MariaDB direct connection: Trying to insert NULL in NOT NULL fields will automatically changed in empty text or 0
https://bugs.documentfoundation.org/show_bug.cgi?id=155529 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155609] Forced to pick from the existing Impress templates - need to ad a Light and a Dark template
https://bugs.documentfoundation.org/show_bug.cgi?id=155609 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Bug 83946 depends on bug 152042, which changed state. Bug 152042 Summary: auto save conflicts with track changes in writer https://bugs.documentfoundation.org/show_bug.cgi?id=152042 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152042] auto save conflicts with track changes in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152042 --- Comment #5 from QA Administrators --- Dear Taofeek, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 152042, which changed state. Bug 152042 Summary: auto save conflicts with track changes in writer https://bugs.documentfoundation.org/show_bug.cgi?id=152042 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147662] data auto filter disappears sporadically
https://bugs.documentfoundation.org/show_bug.cgi?id=147662 --- Comment #4 from QA Administrators --- Dear ronrobsil...@gmail.com, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147633] Print thousands separator in Liberation Serif on writer
https://bugs.documentfoundation.org/show_bug.cgi?id=147633 --- Comment #7 from QA Administrators --- Dear Totorux, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147606] Multiple index marks before the terms when updating the index that uses a concordance file
https://bugs.documentfoundation.org/show_bug.cgi?id=147606 --- Comment #5 from QA Administrators --- Dear George Acu, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141555] New document has caret in awkward position and paper view is not centered
https://bugs.documentfoundation.org/show_bug.cgi?id=141555 --- Comment #23 from QA Administrators --- Dear Wolfgang Fahl, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95908] Can't turn off AutoCorrect globally in Impress and Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=95908 --- Comment #9 from QA Administrators --- Dear 2460acc, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93975] Toolbar table borders control causes spacing to content issues (see comment #6)
https://bugs.documentfoundation.org/show_bug.cgi?id=93975 --- Comment #15 from QA Administrators --- Dear thanasis57, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62991] FILEOPEN existing 3.6.6.1 document: Chart data contents in embedded Calc8 spreadsheet object becomes invisible when EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=62991 --- Comment #11 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51966] Format brush tool moves selection anchor to a random(?) cell
https://bugs.documentfoundation.org/show_bug.cgi?id=51966 --- Comment #14 from QA Administrators --- Dear OfficeUser, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 79206] inconsistent spell check underlining
https://bugs.documentfoundation.org/show_bug.cgi?id=79206 --- Comment #20 from QA Administrators --- Dear mike.hall, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142833] Print Preview button shouldn't be in LibreOffice Draw's Notebookbar UI
https://bugs.documentfoundation.org/show_bug.cgi?id=142833 --- Comment #4 from QA Administrators --- Dear PJF, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142809] [EMF] SetDIBitsToDevice EMR is not implemented
https://bugs.documentfoundation.org/show_bug.cgi?id=142809 --- Comment #4 from QA Administrators --- Dear Valek Filippov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142777] [EMF+] Path Object is not filled by FillPath MR
https://bugs.documentfoundation.org/show_bug.cgi?id=142777 --- Comment #4 from QA Administrators --- Dear Valek Filippov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142740] [EMF+] Path + SetClip + Brush (PathGradient) + FillRects => no shape visible
https://bugs.documentfoundation.org/show_bug.cgi?id=142740 --- Comment #4 from QA Administrators --- Dear Valek Filippov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142660] [EMF] support SRCAND and SRCPAINT ROPs in StretchDIBits with StretchMode set to HALFTONE
https://bugs.documentfoundation.org/show_bug.cgi?id=142660 --- Comment #5 from QA Administrators --- Dear Valek Filippov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140034] SPELL CHECKING DIALOG: It's not possible to change the size of the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=140034 --- Comment #2 from QA Administrators --- Dear R. Green, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136148] Headless converting XLSX to XLS doesn't take hide grid checkbox
https://bugs.documentfoundation.org/show_bug.cgi?id=136148 --- Comment #7 from QA Administrators --- Dear kirill, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - external/libwebp
external/libwebp/CVE-2023-1999.patch.1 | 52
external/libwebp/UnpackedTarball_libwebp.mk |1
2 files changed, 53 insertions(+)
New commits:
commit 42cdd2c08e083a39eb3c8048ef20c7d31e750497
Author: Caolán McNamara
AuthorDate: Wed Jun 14 10:08:13 2023 +0100
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Thu Jun 15 05:07:32 2023 +0200
backport CVE-2023-1999 libwebp fix
Change-Id: Idce341a78e44af9940d287d2a08b02d2ee9a6dae
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153020
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>
diff --git a/external/libwebp/CVE-2023-1999.patch.1
b/external/libwebp/CVE-2023-1999.patch.1
new file mode 100644
index ..65c2cf75fb79
--- /dev/null
+++ b/external/libwebp/CVE-2023-1999.patch.1
@@ -0,0 +1,52 @@
+From a486d800b60d0af4cc0836bf7ed8f21e12974129 Mon Sep 17 00:00:00 2001
+From: James Zern
+Date: Wed, 22 Feb 2023 22:15:47 -0800
+Subject: [PATCH] EncodeAlphaInternal: clear result->bw on error
+
+This avoids a double free should the function fail prior to
+VP8BitWriterInit() and a previous trial result's buffer carried over.
+Previously in ApplyFiltersAndEncode() trial.bw (with a previous
+iteration's buffer) would be freed, followed by best.bw pointing to the
+same buffer.
+
+Since:
+187d379d add a fallback to ALPHA_NO_COMPRESSION
+
+In addition, check the return value of VP8BitWriterInit() in this
+function.
+
+Bug: webp:603
+Change-Id: Ic258381ee26c8c16bc211d157c8153831c8c6910
+---
+ src/enc/alpha_enc.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/src/enc/alpha_enc.c b/src/enc/alpha_enc.c
+index f7c02690e3..7d205586fe 100644
+--- a/src/enc/alpha_enc.c
b/src/enc/alpha_enc.c
+@@ -13,6 +13,7 @@
+
+ #include
+ #include
++#include
+
+ #include "src/enc/vp8i_enc.h"
+ #include "src/dsp/dsp.h"
+@@ -148,6 +149,7 @@ static int EncodeAlphaInternal(const uint8_t* const data,
int width, int height,
+ }
+ } else {
+ VP8LBitWriterWipeOut(_bw);
++ memset(>bw, 0, sizeof(result->bw));
+ return 0;
+ }
+ }
+@@ -162,7 +164,7 @@ static int EncodeAlphaInternal(const uint8_t* const data,
int width, int height,
+ header = method | (filter << 2);
+ if (reduce_levels) header |= ALPHA_PREPROCESSED_LEVELS << 4;
+
+- VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size);
++ if (!VP8BitWriterInit(>bw, ALPHA_HEADER_LEN + output_size)) ok = 0;
+ ok = ok && VP8BitWriterAppend(>bw, , ALPHA_HEADER_LEN);
+ ok = ok && VP8BitWriterAppend(>bw, output, output_size);
+
diff --git a/external/libwebp/UnpackedTarball_libwebp.mk
b/external/libwebp/UnpackedTarball_libwebp.mk
index 67f797157717..78761793174e 100644
--- a/external/libwebp/UnpackedTarball_libwebp.mk
+++ b/external/libwebp/UnpackedTarball_libwebp.mk
@@ -15,6 +15,7 @@ $(eval $(call gb_UnpackedTarball_set_patchlevel,libwebp,0))
$(eval $(call gb_UnpackedTarball_add_patches,libwebp,\
external/libwebp/Makefile.vc.patch \
+ external/libwebp/CVE-2023-1999.patch.1 \
))
# vim: set noet sw=4 ts=4:
[Libreoffice-bugs] [Bug 132478] Semi-transparent areas have white lines when using newline
https://bugs.documentfoundation.org/show_bug.cgi?id=132478 Diana Vides changed: What|Removed |Added CC||dianavide...@gmail.com --- Comment #11 from Diana Vides --- Unfortunately, the bug is still present in version 7.5.3.2 Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (en_US); UI: en-US Calc: threaded It was also present in the most recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e4c611ddc731d6a2ca9c3de61a02d1d4b6eefa9b CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131851] Ctrl-clicking a hyperlink in shape or text box does not work while editing a different object
https://bugs.documentfoundation.org/show_bug.cgi?id=131851 Diana Vides changed: What|Removed |Added CC||dianavide...@gmail.com --- Comment #3 from Diana Vides --- Unfortunately, the bug is still present in version 7.5.3.2 Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (en_US); UI: en-US Calc: threaded It was also present in a recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e4c611ddc731d6a2ca9c3de61a02d1d4b6eefa9b CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/filter/oox/extlstcontext.cxx | 18 +++---
1 file changed, 15 insertions(+), 3 deletions(-)
New commits:
commit 242de60455e0fc554bb9fb592f8f00d7e5edb918
Author: Henry Castro
AuthorDate: Fri Mar 17 11:07:14 2023 -0400
Commit: Henry Castro
CommitDate: Thu Jun 15 03:55:02 2023 +0200
sc: filter: oox: insert a new entry ScDataBarFormat if Id attribute...
does not exist:
0
1
Signed-off-by: Henry Castro
Change-Id: Ie2c1ba2c85d9eead963f4d9b1684d72b64fe815d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149069
Tested-by: Jenkins CollaboraOffice
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153092
Tested-by: Jenkins
diff --git a/sc/source/filter/oox/extlstcontext.cxx
b/sc/source/filter/oox/extlstcontext.cxx
index 5328accac5c8..3209c846f9ce 100644
--- a/sc/source/filter/oox/extlstcontext.cxx
+++ b/sc/source/filter/oox/extlstcontext.cxx
@@ -165,11 +165,23 @@ ContextHandlerRef
ExtConditionalFormattingContext::onCreateContext(sal_Int32 nEl
if (aType == "dataBar")
{
// an ext entry does not need to have an existing corresponding
entry
+ScDataBarFormatData* pInfo;
ExtLst::const_iterator aExt = getExtLst().find( aId );
-if(aExt == getExtLst().end())
-return nullptr;
+if (aExt == getExtLst().end())
+{
+pInfo = new ScDataBarFormatData();
+if (pInfo)
+{
+auto pFormat =
std::make_unique(());
+pFormat->SetDataBarData(pInfo);
+maEntries.push_back(std::move(pFormat));
+}
+}
+else
+{
+pInfo = aExt->second;
+}
-ScDataBarFormatData* pInfo = aExt->second;
if (!pInfo)
{
return nullptr;
[Libreoffice-commits] core.git: Changes to 'refs/tags/cib-6.4-19'
Tag 'cib-6.4-19' created by Thorsten Behrens at 2023-06-15 01:04 + Release CIB Office cib-6.4-19 -BEGIN PGP SIGNATURE- iNUEABYKAH0WIQRV78SO268/dhkw1IIeB5amgXyR5gUCZIpjnl8UgAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NTVF RkM0OEVEQkFGM0Y3NjE5MzBENDgyMUUwNzk2QTY4MTdDOTFFNgAKCRAeB5amgXyR 5rYtAQDfWp0ef57kjBCTR0Pu49CHviGuC5J/QQPUcrrKhVNYtAD/V6MVend90tCt NK70sx4+HE/y3nGwbliPzWdIQF6sHgQ= =p7Tj -END PGP SIGNATURE- Changes since cib-6.4-18-5: --- 0 files changed ---
[Libreoffice-bugs] [Bug 144634] Data entry into a cell should match cell's configured vertical alignment formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=144634 Concerned User changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #5 from Concerned User --- This behavior persists in the latest build (7.5.4.2, 36ccfdc35048b057fd9854c757a8b67ec53977b6) For clarity, this issue is observed while actively editing the contents of a cell. Once completed, the proper formatting is observed. However, as originally described, the vertical alignment should be respected while actively editing the contents of a cell. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144634] Data entry into a cell should match cell's configured vertical alignment formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=144634 --- Comment #4 from Concerned User --- Created attachment 187919 --> https://bugs.documentfoundation.org/attachment.cgi?id=187919=edit Example image of improper vertical alignment Example image showcasing improper vertical alignment while actively editing the contents of a cell. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155844] New: Calc - file PNG zero size when export a sheet selection
https://bugs.documentfoundation.org/show_bug.cgi?id=155844 Bug ID: 155844 Summary: Calc - file PNG zero size when export a sheet selection Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wilson.pedros...@gmail.com Description: Calc - file PNG zero size when export a sheet selection. JPG type OK Steps to Reproduce: 1.Open calc and create a new sheet 2.select part of this sheet 3.export to PNG file Actual Results: PNG file generated with zero size Expected Results: PNG with sheet selection Reproducible: Always User Profile Reset: No Additional Info: none -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155843] LOOKUP function not working properly
https://bugs.documentfoundation.org/show_bug.cgi?id=155843 --- Comment #2 from Liam M --- (In reply to m.a.riosv from comment #1) > The function works fine, you need to read carefully the help, because the > searched range must be sorted ascending. And column A is not sorted. > file:///C:/Program%20Files/LibreOffice/help/en-US/text/scalc/01/04060109. > html?DbPAR=CALC#bm_id3159273 Oh no! It does indeed say that. That's unfortunate. This really needs to be changed. Libreoffice Calc should definitely have a function that does this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126314] FILEOPEN: DOCX: Incorrect height of line (b/c entire document is superscript)
https://bugs.documentfoundation.org/show_bug.cgi?id=126314 --- Comment #8 from Justin L --- repro 24.2+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 40272] Filesave ODT as DOC: continued instead of restarted numbering (Comment 10 and Comment 16)
https://bugs.documentfoundation.org/show_bug.cgi?id=40272 --- Comment #18 from Justin L --- repro 24.2+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155843] LOOKUP function not working properly
https://bugs.documentfoundation.org/show_bug.cgi?id=155843 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from m.a.riosv --- The function works fine, you need to read carefully the help, because the searched range must be sorted ascending. And column A is not sorted. file:///C:/Program%20Files/LibreOffice/help/en-US/text/scalc/01/04060109.html?DbPAR=CALC#bm_id3159273 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155838] PDF Convertion Removing Dropdown and Checkbox Input
https://bugs.documentfoundation.org/show_bug.cgi?id=155838 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- It uses the same options from the last export, opening LibreOffice. Do one export opening LibreOffice selecting 'Create PDF form' Then it will be used by the command line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'feature/cib_contract891c' - 10 commits - download.lst external/curl external/libtommath external/libxml2 external/libxmlsec external/libxslt external/openssl ex
Rebased ref, commits from common ancestor: commit 4fbe08e56bdbb60289dd18c718b80168b640110f Author: Thorsten Behrens AuthorDate: Wed Jun 14 16:42:21 2023 +0200 Commit: Thorsten Behrens CommitDate: Thu Jun 15 01:32:19 2023 +0200 Build python3 against own openssl This is a bit from https://gerrit.libreoffice.org/c/core/+/98435 which we were missing, due to sticking to Python 3.5.x Change-Id: I3b18d1f540d56cf06fccc4abcb6e45eda8a4ba4b diff --git a/external/python3/python-3.5.4-ssl.patch.1 b/external/python3/python-3.5.4-ssl.patch.1 index beb6fe38882f..837d0053cf5a 100644 --- a/external/python3/python-3.5.4-ssl.patch.1 +++ b/external/python3/python-3.5.4-ssl.patch.1 @@ -34,7 +34,7 @@ diff -ru python3.orig/PCbuild/_ssl.vcxproj python3/PCbuild/_ssl.vcxproj - ws2_32.lib;crypt32.lib;$(OutDir)libeay$(PyDebugExt).lib;$(OutDir)ssleay$(PyDebugExt).lib;%(AdditionalDependencies) -+ ws2_32.lib;crypt32.lib;$(WORKDIR)\UnpackedTarball\openssl\out32dll\libeay32.lib;$(WORKDIR)\UnpackedTarball\openssl\out32dll\ssleay32.lib;%(AdditionalDependencies) ++ ws2_32.lib;crypt32.lib;$(WORKDIR)\UnpackedTarball\openssl\libssl.lib;$(WORKDIR)\UnpackedTarball\openssl\libcrypto.lib;%(AdditionalDependencies) commit a30e264accbec3f6269e89887e4acd2a0538e515 Author: Thorsten Behrens AuthorDate: Wed Jun 14 13:34:52 2023 +0200 Commit: Thorsten Behrens CommitDate: Thu Jun 15 01:32:19 2023 +0200 openssl: upgrade to release 1.1.1t Fixes CVE-2023-0286 CVE-2023-0215 CVE-2022-4450 CVE-2022-4304 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146653 Tested-by: Jenkins Reviewed-by: Thorsten Behrens (cherry picked from commit f9229fdadbd205a8953577efc72a6e43717c764e) (cherry picked from commit ba359c09226756865d3813fee08514384257ae58) Change-Id: I93ce0362b17bd07b0644564a0676daaa56bc8b50 diff --git a/download.lst b/download.lst index 2e8f5b2aea0a..89860176ad77 100644 --- a/download.lst +++ b/download.lst @@ -177,8 +177,8 @@ export OPENCOLLADA_SHA256SUM := 8f25d429237cde289a448c82a0a830791354ccce5ee40d77 export OPENCOLLADA_TARBALL := OpenCOLLADA-master-6509aa13af.tar.bz2 export OPENLDAP_SHA256SUM := 99f37d6747d88206c470067eda624d5e48c1011e943ec0ab217bae8712e22f34 export OPENLDAP_TARBALL := openldap-2.4.59.tgz -export OPENSSL_SHA256SUM := c5ac01e760ee6ff0dab61d6b2bbd30146724d063eb322180c6f18a6f74e4b6aa -export OPENSSL_TARBALL := openssl-1.1.1s.tar.gz +export OPENSSL_SHA256SUM := 8dee9b24bdb1dcbf0c3d1e9b02fb8f6bf22165e807f45adeb7c9677536859d3b +export OPENSSL_TARBALL := openssl-1.1.1t.tar.gz export ORCUS_SHA256SUM := 676b1fedd721f64489650f5e76d7f98b750439914d87cae505b8163d08447908 export ORCUS_TARBALL := liborcus-0.12.1.tar.gz export OWNCLOUD_ANDROID_LIB_SHA256SUM := b18b3e3ef7fae6a79b62f2bb43cc47a5346b6330f6a383dc4be34439aca5e9fb commit 61017fc6146a6162678e7d9218ee0fe4de6527a5 Author: Xisco Fauli AuthorDate: Wed Nov 2 20:29:51 2022 +0100 Commit: Thorsten Behrens CommitDate: Thu Jun 15 01:32:19 2023 +0200 upgrade to openssl-1.1.1s Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142184 Tested-by: Jenkins Reviewed-by: Caolán McNamara (cherry picked from commit 23e6227ab347a00b235fb00892b379ef4e3a0d35) (cherry picked from commit 2c06d55c8e43368920780e55c62e1e65fdefba04) Change-Id: Ic0f1fca7ef73b3a443c24d2bcc7f234be331a05b diff --git a/download.lst b/download.lst index 2c413cd593f8..2e8f5b2aea0a 100644 --- a/download.lst +++ b/download.lst @@ -177,8 +177,8 @@ export OPENCOLLADA_SHA256SUM := 8f25d429237cde289a448c82a0a830791354ccce5ee40d77 export OPENCOLLADA_TARBALL := OpenCOLLADA-master-6509aa13af.tar.bz2 export OPENLDAP_SHA256SUM := 99f37d6747d88206c470067eda624d5e48c1011e943ec0ab217bae8712e22f34 export OPENLDAP_TARBALL := openldap-2.4.59.tgz -export OPENSSL_SHA256SUM := d7939ce614029cdff0b6c20f0e2e5703158a489a72b2507b8bd51bf8c8fd10ca -export OPENSSL_TARBALL := openssl-1.1.1q.tar.gz +export OPENSSL_SHA256SUM := c5ac01e760ee6ff0dab61d6b2bbd30146724d063eb322180c6f18a6f74e4b6aa +export OPENSSL_TARBALL := openssl-1.1.1s.tar.gz export ORCUS_SHA256SUM := 676b1fedd721f64489650f5e76d7f98b750439914d87cae505b8163d08447908 export ORCUS_TARBALL := liborcus-0.12.1.tar.gz export OWNCLOUD_ANDROID_LIB_SHA256SUM := b18b3e3ef7fae6a79b62f2bb43cc47a5346b6330f6a383dc4be34439aca5e9fb commit 858d475f9bc07ad648b4a0d91b5fdedeac6cf307 Author: Taichi Haradaguchi <20001...@ymail.ne.jp> AuthorDate: Tue Sep 6 14:42:20 2022 +0900 Commit: Thorsten Behrens CommitDate: Thu Jun 15 01:32:19 2023 +0200 upgrade openssl-1.1.1q Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139463 Tested-by: Jenkins Reviewed-by: Caolán McNamara (cherry picked from commit 96db5e3d610ede2ed82f1ab7673ac6d1c69fd588) (cherry picked from commit 9da5e4107e74d7590fbf44f5f4f24ed620852f91) Change-Id:
[Libreoffice-bugs] [Bug 155843] New: LOOKUP function not working properly
https://bugs.documentfoundation.org/show_bug.cgi?id=155843 Bug ID: 155843 Summary: LOOKUP function not working properly Product: LibreOffice Version: 7.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: liammcgillivra...@gmail.com Created attachment 187918 --> https://bugs.documentfoundation.org/attachment.cgi?id=187918=edit This bug is apparent on Row 2 of this spreadsheet. The LOOKUP function is not doing what it's supposed to, despite being used exactly as described in the Help section. The search vector & result vector are both one column. But I cannot figure out exactly how it determines the output. For the first many columns of cells I use as the search criterion, the function outputs "#N/A". I confirmed that the spellings do indeed match. But when I use a search criterion value that matches the first cell in the search vector column, I get the correct value. But then using any cells to the right of this one as input gives me the same output; the value of the first cell in the result vector. I don't know what it's doing, but it's not what it's supposed to do. I included the file as an attachment. See cells on the second row where this function is being used. It's supposed to return the 3-letter country code of the cell above. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155434] Several Calc menu commands are available in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155434 --- Comment #2 from Eyal Rozenberg --- Heiko, IIANM, Gabor did not suggest removing these items and menus, but rather "graying them out" - since not everything that should be grayed out, is; especially menus and submenus. I also think more graying-out is in order. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155434] Several Calc menu commands are available in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155434 --- Comment #2 from Eyal Rozenberg --- Heiko, IIANM, Gabor did not suggest removing these items and menus, but rather "graying them out" - since not everything that should be grayed out, is; especially menus and submenus. I also think more graying-out is in order. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155767] Bad rendering of optional hyphen for Arabic/Persian text
https://bugs.documentfoundation.org/show_bug.cgi?id=155767 --- Comment #7 from Eyal Rozenberg --- Created attachment 187917 --> https://bugs.documentfoundation.org/attachment.cgi?id=187917=edit Illustration of behavior with Farsi, Hebrew, English text In this file there are examples not only of 3 languages, but also of secondary issues such as ligature breakage and different behavior of soft hyphen from hard hyphen/minus and upper-hyphen/Maqaf in Hebrew. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143540] EDITING: Keypad decimal character not changed to comma
https://bugs.documentfoundation.org/show_bug.cgi?id=143540 --- Comment #24 from Sébastien P. --- On my side: Key press on widget: <__main__.MyWindow object at 0x7fca59134140 (__main__+MyWindow at 0x55ebd073e2f0)> Modifiers: Key val, name: 46 period Key press on widget: <__main__.MyWindow object at 0x7fca59134140 (__main__+MyWindow at 0x55ebd073e2f0)> Modifiers: Key val, name: 65506 Shift_R Key press on widget: <__main__.MyWindow object at 0x7fca59134140 (__main__+MyWindow at 0x55ebd073e2f0)> Modifiers: Key val, name: 46 period * Both « . » (digit side and letters side) gave me the same key. * Writer and other applications always give me « . » (before and currently). No change. I thought about something: I use a special layout. It may be linked. Here are my X11 options: Option "XkbLayout" "fr" Option "XkbVariant" "oss" Option "XkbOptions" "compose:rwin,compose:lwin" (the keyboard is physically usual) Sorry, I am going on holiday. I will not be able to give more information until my return in 4 weeks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155839] When propmpted about missing hyphenation data - I should be offered a download link
https://bugs.documentfoundation.org/show_bug.cgi?id=155839 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #2 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > LibreOffice only tells you the fact. Notification bars are not about telling me facts; they're about drawing my attention to a problematic situation which I may/should want to address. > It has no way to know that *any* language's hyphenation data is available > from *any* source (third party extension? maybe on OOo/AOO extension site?); > or maybe in another product (MS Word that can generate ODT?). Sure it has. If LO can know when an update is available, it can know whether hyphenation patterns are available. But even if you were to argue it shouldn't actively go look for the hyphenation patterns for the locale(s) you use - it should still do so if you ask it to, i.e. it will tell you you're missing patterns, and when you click, it will either get them for you, or tell you they're missing. Not as great, but better than what we have now. > And it can't do that. And tells. Nothing wrong at all. If this were an _error_ message, that would be a different matter. But it isn't. It leads the user to believe that they can get those hyphenation patterns. > And - well, unless you require that all language modules are installed > unconditionally (which I personally would welcome, but many would hate), > there's no way to even point to downloads, because it may be not > downloadable, but installable - from the MSI on Windows; from packages on > Debian... I'll again make the analogy regarding LO updates. Yes, this may be difficult/impossible/distribution-specific. In those case, we should offer an easy customization point for distributors, plus, we should make some effort to help the user get what they need. That is, depending on how LO was installed and/or what we know about the OS/DE, we should point the user to the closest thing possible to a download link. If it's one of our packages - then it would be to a corresponding package of the same kind for hyphenation patterns; if not - the packagers will change this to something which suits them. Anyway, let's see what the UX design, umm, ad-hoc per-meeting committee thinks about this. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 155839] When propmpted about missing hyphenation data - I should be offered a download link
https://bugs.documentfoundation.org/show_bug.cgi?id=155839 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #2 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > LibreOffice only tells you the fact. Notification bars are not about telling me facts; they're about drawing my attention to a problematic situation which I may/should want to address. > It has no way to know that *any* language's hyphenation data is available > from *any* source (third party extension? maybe on OOo/AOO extension site?); > or maybe in another product (MS Word that can generate ODT?). Sure it has. If LO can know when an update is available, it can know whether hyphenation patterns are available. But even if you were to argue it shouldn't actively go look for the hyphenation patterns for the locale(s) you use - it should still do so if you ask it to, i.e. it will tell you you're missing patterns, and when you click, it will either get them for you, or tell you they're missing. Not as great, but better than what we have now. > And it can't do that. And tells. Nothing wrong at all. If this were an _error_ message, that would be a different matter. But it isn't. It leads the user to believe that they can get those hyphenation patterns. > And - well, unless you require that all language modules are installed > unconditionally (which I personally would welcome, but many would hate), > there's no way to even point to downloads, because it may be not > downloadable, but installable - from the MSI on Windows; from packages on > Debian... I'll again make the analogy regarding LO updates. Yes, this may be difficult/impossible/distribution-specific. In those case, we should offer an easy customization point for distributors, plus, we should make some effort to help the user get what they need. That is, depending on how LO was installed and/or what we know about the OS/DE, we should point the user to the closest thing possible to a download link. If it's one of our packages - then it would be to a corresponding package of the same kind for hyphenation patterns; if not - the packagers will change this to something which suits them. Anyway, let's see what the UX design, umm, ad-hoc per-meeting committee thinks about this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142359] ACCESSIBILITY: Language tagging is lost when merging LO generated PDFs with Acrobat
https://bugs.documentfoundation.org/show_bug.cgi?id=142359 --- Comment #13 from devsepp...@gmail.com --- (In reply to bunkem from comment #11) > Could you also explain the steps how you do the "merge" operation in Acrobat? I don't own Acrobat Pro my self and I won't have access to Acrobat until next week. I will come back to you to explain the steps once I have access to Acrobat, because I can't remember the process accurately enough from the top of my head. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155835] Incorrect display of Cyrillic characters in the text in LO Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155835 --- Comment #4 from randylo...@gmail.com --- I will clarify the initial data a little. I assumed that this file was created in Microsoft Word, but what I know for sure is that it was created in Windows. Then I changed my personal data in this file using LO Writer in Linux and attached a saved file with the same RTF extension to the message. I must have misled you with this. I apologize for this unconscious act. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142359] ACCESSIBILITY: Language tagging is lost when merging LO generated PDFs with Acrobat
https://bugs.documentfoundation.org/show_bug.cgi?id=142359 --- Comment #12 from devsepp...@gmail.com --- (In reply to bunkem from comment #10) > Please confirm I'm looking at the right section. Yes, you are looking at the right section. I should say that I am not aPDF expert, during accessibility checking of documents I just happened to discover that language markings of LibreOffice generated PDF files disappear after merging them with Acrobat Pro. I found out this when JAWS screen reader could no longer dynamically change the reading language according to the content. Then I just started to investigate the issue a little further. I should also mention that there are tools that can merge LO generated PDF files in a way that preserves the language tagging. One such tool is the Foxit PDF editor. https://www.foxit.com/merge-pdf/ This is propably irrelevant, but PDF 1.3 reference manual seems to indicate that in the past there has been even third way of marking the language of text. page 39, https://people.ksp.sk/~vlado/tex/pdfspec.pdf "The text may also contain an escape sequence to indicate the language of the text. This is useful when the language cannot be determined from the character codes used in the text. The escape sequence uses the Unicode hex value U+001B followed by the two ASCII codes for the language identifiers defined by ISO 639 (see Appendix I), optionally followed by the two ASCII codes for country defined by IS0 3166 (see Appendix J), followed by U+001B." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155835] Incorrect display of Cyrillic characters in the text in LO Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155835 --- Comment #3 from randylo...@gmail.com --- Created attachment 187916 --> https://bugs.documentfoundation.org/attachment.cgi?id=187916=edit new file I tried to delete my personal data by another method. I opened this file in Windows 7 using notepad and deleted my personal data and saved it. In LO Writer, the same unreadable characters remain in the footnotes. In Microsoft Word they are displayed in the correct encoding, in Only Office they are also displayed correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155836] The button Help in the Database wizard redirect to a generic page in Ubuntu instead of the wizard page
https://bugs.documentfoundation.org/show_bug.cgi?id=155836 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Stéphane Guillou (stragu) --- *** This bug has been marked as a duplicate of bug 134169 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134169] [UI] Database connection wizard's "Select Database" step does not open right help page
https://bugs.documentfoundation.org/show_bug.cgi?id=134169 Stéphane Guillou (stragu) changed: What|Removed |Added CC||jcs...@libreoffice.org --- Comment #6 from Stéphane Guillou (stragu) --- *** Bug 155836 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64795] [FORMATTING] Add new feature of 'keep with previous paragraph' formatting option for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=64795 --- Comment #7 from sebalis --- I once wrote a comment describing my use case for this feature which I strangely can’t find any more in this or related bugs. Suffice it to say that I find it very sad that this bug has just been set to lowest importance because there are good use cases for this that cannot easily be fulfilled otherwise. Also I don’t think that the lack of a corresponding feature in Word should stop LibreOffice from implementing this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155832] Writer, UI. Paragraph style dropdown should remain visible when Update/Edit Style popup is selected
https://bugs.documentfoundation.org/show_bug.cgi?id=155832 --- Comment #4 from Roberto Salomon --- Repeated test on same system with Wayland instead of X11. Same result. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121227] Wrong optimal height of a cell with Cyrillic Liberation Sans text font 10
https://bugs.documentfoundation.org/show_bug.cgi?id=121227 --- Comment #9 from Stéphane Guillou (stragu) --- Still repro: Version: 7.6.0.0.beta1 (X86_64) / LibreOffice Community Build ID: be55b15d98c5f059483845a183fcb5ea8023d27c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145951] Image anchored as 'as character' non-zero "Vertical BOTTOM to Base line" moves to different spot on ODT->DOCX/DOC/RTF since MSO has no inline vertical positioning
https://bugs.documentfoundation.org/show_bug.cgi?id=145951 Justin L changed: What|Removed |Added Summary|Image anchored as 'as |Image anchored as 'as |character' moves to |character' non-zero |different spot on |"Vertical BOTTOM to Base |DOCX/DOC/RTF export |line" moves to different ||spot on ODT->DOCX/DOC/RTF ||since MSO has no inline ||vertical positioning -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145951] Image anchored as 'as character' moves to different spot on DOCX/DOC/RTF export
https://bugs.documentfoundation.org/show_bug.cgi?id=145951 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||4821 Version|7.4.0.0 alpha0+ |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124821] FILESAVE DOCX: inline (anchored as char) frames moved to end of paragraph on export
https://bugs.documentfoundation.org/show_bug.cgi?id=124821 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5951 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150244] TABLES: Command "Distribute columns evenly" doesn't work for a single row
https://bugs.documentfoundation.org/show_bug.cgi?id=150244 Justin L changed: What|Removed |Added Version|7.2.7.2 release |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of cells with wrapped text is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 Stéphane Guillou (stragu) changed: What|Removed |Added CC||rot_...@yahoo.de --- Comment #14 from Stéphane Guillou (stragu) --- *** Bug 148288 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148288] Row height changed by "Optimal height" is not stored in the file
https://bugs.documentfoundation.org/show_bug.cgi?id=148288 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Stéphane Guillou (stragu) --- *** This bug has been marked as a duplicate of bug 146668 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121227] Wrong optimal height of a cell with Cyrillic Liberation Sans text font 10
https://bugs.documentfoundation.org/show_bug.cgi?id=121227 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |8288| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148139] Row height when text is wrapped is being lost after saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=148139 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |8288| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124098] FILEOPEN: Calc sheet showing multiple "adapt Row Height" responses, slow loading
https://bugs.documentfoundation.org/show_bug.cgi?id=124098 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |8288| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125077] [META] regressions introduced by row height recalculation on document load
https://bugs.documentfoundation.org/show_bug.cgi?id=125077 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|148288 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148288 [Bug 148288] Row height changed by "Optimal height" is not stored in the file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148288] Row height changed by "Optimal height" is not stored in the file
https://bugs.documentfoundation.org/show_bug.cgi?id=148288 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=62 | |268,| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |4098, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |1227, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |8139| Blocks|125077 | --- Comment #3 from Stéphane Guillou (stragu) --- Repro in 6.2.0.3 but not 6.1.0.3, so must be the same regression as bug 146668. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125077 [Bug 125077] [META] regressions introduced by row height recalculation on document load -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136472] FILEOPEN DOCX: be like DOC - import bTitlePage into Default Page Style (as separate first header), not First Page style
https://bugs.documentfoundation.org/show_bug.cgi?id=136472 Justin L changed: What|Removed |Added Summary|Same content on left/right |FILEOPEN DOCX: be like DOC |pages/ Same content on |- import bTitlePage into |first page checked on file |Default Page Style (as |open DOCX |separate first header), not ||First Page style -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of cells with wrapped text is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org, ||vasily.melenc...@cib.de Version|6.1.6.3 release |6.1.4.2 release --- Comment #13 from Stéphane Guillou (stragu) --- CCing Vasily. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107326] [META] Writer style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107326 Bug 107326 depends on bug 154933, which changed state. Bug 154933 Summary: Rename "Text body" to "Body text" https://bugs.documentfoundation.org/show_bug.cgi?id=154933 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - cui/inc cui/source
cui/inc/strings.hrc|1 +
cui/source/options/optlanguagetool.cxx |1 +
2 files changed, 2 insertions(+)
New commits:
commit a32c563fdddf7aa7211df830c037fbb4daf41ae0
Author: Mike Kaganski
AuthorDate: Wed Jun 14 17:01:32 2023 +0300
Commit: Mike Kaganski
CommitDate: Wed Jun 14 22:20:49 2023 +0200
Related: tdf#150494 add placeholder text to the REST protocol field
Change-Id: I8aab941d9dd03e54a3a39ccb643a5a628d6c5be7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153061
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
(cherry picked from commit 7c6c58197a84cf22789ca3dc97e863390c31a2f9)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153074
diff --git a/cui/inc/strings.hrc b/cui/inc/strings.hrc
index 98c6cc50b2d3..84a2c9f859a1 100644
--- a/cui/inc/strings.hrc
+++ b/cui/inc/strings.hrc
@@ -407,6 +407,7 @@
#define RID_CUISTR_OPT_READONLY
NC_("RID_CUISTR_OPT_READONLY", "This property is locked for editing.")
#define RID_LANGUAGETOOL_LEAVE_EMPTY
NC_("RID_LANGUAGETOOL_LEAVE_EMPTY", "Leave this field empty to use the free
version")
+#define RID_LANGUAGETOOL_REST_LEAVE_EMPTY
NC_("RID_LANGUAGETOOL_REST_LEAVE_EMPTY", "Leave this field empty to use
LanguageTool protocol")
// Translatable names of color schemes
#define RID_COLOR_SCHEME_LIBREOFFICE_AUTOMATIC
NC_("RID_COLOR_SCHEME_LIBREOFFICE_AUTOMATIC", "Automatic")
diff --git a/cui/source/options/optlanguagetool.cxx
b/cui/source/options/optlanguagetool.cxx
index 485e8ecb1be6..e1f4806f47f3 100644
--- a/cui/source/options/optlanguagetool.cxx
+++ b/cui/source/options/optlanguagetool.cxx
@@ -45,6 +45,7 @@
OptLanguageToolTabPage::OptLanguageToolTabPage(weld::Container* pPage,
m_xBaseURLED->set_placeholder_text(CuiResId(RID_LANGUAGETOOL_LEAVE_EMPTY));
m_xUsernameED->set_placeholder_text(CuiResId(RID_LANGUAGETOOL_LEAVE_EMPTY));
m_xApiKeyED->set_placeholder_text(CuiResId(RID_LANGUAGETOOL_LEAVE_EMPTY));
+
m_xRestProtocol->set_placeholder_text(CuiResId(RID_LANGUAGETOOL_REST_LEAVE_EMPTY));
}
OptLanguageToolTabPage::~OptLanguageToolTabPage() {}
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 Adolfo Jayme Barrientos changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155838] PDF Convertion Removing Dropdown and Checkbox Input
https://bugs.documentfoundation.org/show_bug.cgi?id=155838 --- Comment #1 from Steph --- Created attachment 187915 --> https://bugs.documentfoundation.org/attachment.cgi?id=187915=edit A document to use while troubleshooting Use this as the newly created document (from step 1), and continue with the step 2 and on with the steps to reproduce. I believe the dropdowns and checkboxes, in this doc, may be from an older version of word (perhaps 2016). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155835] Incorrect display of Cyrillic characters in the text in LO Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155835 --- Comment #2 from Mike Kaganski --- This file is not created in MS Word: it is created in LibreOffice - maybe just opening the original RTF from MS Word in Writer, and re-saving. This created a new file from the data that LibreOffice understood, and destroyed everything. This file can't show and allow to fix the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155842] The font "Avrile" has 18 styles, I installed all successfully, but I can only see and use one.
https://bugs.documentfoundation.org/show_bug.cgi?id=155842 Sonam changed: What|Removed |Added OS|All |macOS (All) --- Comment #1 from Sonam --- All 18 styles are shown, can be chosen, and used, when in "Pages," though. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125077] [META] regressions introduced by row height recalculation on document load
https://bugs.documentfoundation.org/show_bug.cgi?id=125077 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|148139 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148139 [Bug 148139] Row height when text is wrapped is being lost after saving document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148139] Row height when text is wrapped is being lost after saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=148139 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Blocks|125077 | Status|NEW |RESOLVED --- Comment #3 from Stéphane Guillou (stragu) --- Not reproduced in 6.0, so looks like the same regression as bug 146668. *** This bug has been marked as a duplicate of bug 146668 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125077 [Bug 125077] [META] regressions introduced by row height recalculation on document load -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of cells with wrapped text is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 Stéphane Guillou (stragu) changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #12 from Stéphane Guillou (stragu) --- *** Bug 148139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155839] When propmpted about missing hyphenation data - I should be offered a download link
https://bugs.documentfoundation.org/show_bug.cgi?id=155839 --- Comment #1 from Mike Kaganski --- No. LibreOffice only tells you the fact. It has no way to know that *any* language's hyphenation data is available from *any* source (third party extension? maybe on OOo/AOO extension site?); or maybe in another product (MS Word that can generate ODT?). It knows that there is a text marked this language (it may be even not known to LibreOffice, and its name is obtained from the library used internally, given the language tag that some user entered manually), and this text is also has "auto-hyphenation" property. And it can't do that. And tells. Nothing wrong at all. And - well, unless you require that all language modules are installed unconditionally (which I personally would welcome, but many would hate), there's no way to even point to downloads, because it may be not downloadable, but installable - from the MSI on Windows; from packages on Debian... NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: editeng/source include/sfx2 include/svtools sc/source sd/source sfx2/source sw/inc sw/source
editeng/source/editeng/impedit3.cxx | 24
include/sfx2/viewsh.hxx |3 +++
include/svtools/colorcfg.hxx|2 +-
sc/source/ui/inc/tabvwsh.hxx|2 ++
sc/source/ui/view/tabvwshc.cxx | 20
sd/source/ui/inc/ViewShellBase.hxx |2 ++
sd/source/ui/view/ViewShellBase.cxx | 27 +++
sfx2/source/view/viewsh.cxx |6 ++
sw/inc/view.hxx |2 ++
sw/source/uibase/uiview/viewprt.cxx | 27 +++
10 files changed, 110 insertions(+), 5 deletions(-)
New commits:
commit 069c7dc4e9706b40ca12d83d83f90f41cec948f8
Author: Paris Oplopoios
AuthorDate: Tue Jun 13 20:36:48 2023 +0300
Commit: Paris Oplopoios
CommitDate: Wed Jun 14 22:12:21 2023 +0200
Add editengine view separation in tiled rendering
Editengine now gets the background color from the current view instead
from a global variable
Change-Id: I98a0fccf4d0c83f4dabf8e534a9228b8a5e271d7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152996
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Paris Oplopoios
(cherry picked from commit 7baa475342b67c10537e11da37b8862648679b02)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153073
Tested-by: Jenkins
diff --git a/editeng/source/editeng/impedit3.cxx
b/editeng/source/editeng/impedit3.cxx
index bcf0c044872f..e18562d3113f 100644
--- a/editeng/source/editeng/impedit3.cxx
+++ b/editeng/source/editeng/impedit3.cxx
@@ -52,6 +52,7 @@
#include
#include
+#include
#include
#include
@@ -67,6 +68,7 @@
#include
#include
+#include
#include
#include
#include
@@ -4686,15 +4688,29 @@ Reference < i18n::XExtendedInputSequenceChecker > const
& ImpEditEngine::ImplGet
Color ImpEditEngine::GetAutoColor() const
{
-Color aColor = GetColorConfig().GetColorValue(svtools::FONTCOLOR).nColor;
+Color aColor;
-if ( GetBackgroundColor() != COL_AUTO )
+if (comphelper::LibreOfficeKit::isActive() && SfxViewShell::Current())
{
-if ( GetBackgroundColor().IsDark() && aColor.IsDark() )
+// Get document background color from current view instead
+aColor =
SfxViewShell::Current()->GetColorConfigColor(svtools::DOCCOLOR);
+if (aColor.IsDark())
aColor = COL_WHITE;
-else if ( GetBackgroundColor().IsBright() && aColor.IsBright() )
+else
aColor = COL_BLACK;
}
+else
+{
+aColor = GetColorConfig().GetColorValue(svtools::FONTCOLOR).nColor;
+
+if ( GetBackgroundColor() != COL_AUTO )
+{
+if ( GetBackgroundColor().IsDark() && aColor.IsDark() )
+aColor = COL_WHITE;
+else if ( GetBackgroundColor().IsBright() && aColor.IsBright() )
+aColor = COL_BLACK;
+}
+}
return aColor;
}
diff --git a/include/sfx2/viewsh.hxx b/include/sfx2/viewsh.hxx
index b805f1cf99d4..08bc6cecc8cb 100644
--- a/include/sfx2/viewsh.hxx
+++ b/include/sfx2/viewsh.hxx
@@ -74,6 +74,7 @@ namespace com::sun::star::ui { class XContextMenuInterceptor;
}
namespace com::sun::star::ui { struct ContextMenuExecuteEvent; }
namespace com::sun::star::view { class XRenderable; }
namespace tools { class Rectangle; }
+namespace svtools { enum ColorConfigEntry : int; }
enum class SfxPrinterChangeFlags
{
@@ -428,6 +429,8 @@ public:
virtual void afterCallbackRegistered();
/// See OutlinerViewShell::GetEditWindowForActiveOLEObj().
virtual vcl::Window* GetEditWindowForActiveOLEObj() const override;
+/// Get a color config color from this view
+virtual ::Color GetColorConfigColor(svtools::ColorConfigEntry nColorType)
const;
/// Set the LibreOfficeKit language of this view.
void SetLOKLanguageTag(const OUString& rBcp47LanguageTag);
diff --git a/include/svtools/colorcfg.hxx b/include/svtools/colorcfg.hxx
index de16f18eab13..9810aac0393d 100644
--- a/include/svtools/colorcfg.hxx
+++ b/include/svtools/colorcfg.hxx
@@ -27,7 +27,7 @@
namespace svtools{
-enum ColorConfigEntry
+enum ColorConfigEntry : int
{
DOCCOLOR,
DOCBOUNDARIES ,
diff --git a/sc/source/ui/inc/tabvwsh.hxx b/sc/source/ui/inc/tabvwsh.hxx
index a670c4429d53..d8434af53bc6 100644
--- a/sc/source/ui/inc/tabvwsh.hxx
+++ b/sc/source/ui/inc/tabvwsh.hxx
@@ -395,6 +395,8 @@ public:
void afterCallbackRegistered() override;
/// See SfxViewShell::NotifyCursor().
void NotifyCursor(SfxViewShell* pViewShell) const override;
+/// See SfxViewShell::GetColorConfigColor().
+::Color GetColorConfigColor(svtools::ColorConfigEntry nColorType) const
override;
/// Emits a LOK_CALLBACK_INVALIDATE_HEADER for all views whose current tab
is equal to nCurrentTabIndex
static void notifyAllViewsHeaderInvalidation(const SfxViewShell*
pForViewShell, HeaderType eHeaderType, SCTAB nCurrentTabIndex);
static bool
[Libreoffice-bugs] [Bug 155842] New: The font "Avrile" has 18 styles, I installed all successfully, but I can only see and use one.
https://bugs.documentfoundation.org/show_bug.cgi?id=155842 Bug ID: 155842 Summary: The font "Avrile" has 18 styles, I installed all successfully, but I can only see and use one. Product: LibreOffice Version: 7.4.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sonamsp...@gmx.de Description: I use a mac with Chip: Apple M2 and MacOS: Ventura 13.3 I downloaded LibreOffice 7.4.7 for MacOS (Apple Silicon) from https://www.libreoffice.org/download/download-libreoffice/?type=mac-aarch64=7.4.7=de I need to use the font "Avrile" and its 18 styles. All are installed sucessfully, my font managers (Typeface App and anotherone "Schriftsammlung" (German name)) tell me. Why can I only choose one style when in LibreOfficeWriter? Steps to Reproduce: 1.Try to use the style "SemiBold" or any other thatn the regular one of the font "Avrile" in LibreOfficeWriter on a mac with Chip: Apple M2 and MacOS: Ventura 13.3 2. 3. Actual Results: Only the style "Avrile Serif" shows and can be used, none of the other installed styles. Expected Results: I shoud be able to use the 18 installed styles and they should appear in the drop down of the font name bar. Reproducible: Always User Profile Reset: Yes Additional Info: I don't understand what I am supposed to write in this field, sorry. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134062] FILEOPEN DOCX Missing cell padding value imported as 0.12 cm (probably duplicate of smart justify actually)
https://bugs.documentfoundation.org/show_bug.cgi?id=134062 Justin L changed: What|Removed |Added Summary|FILEOPEN DOCX Missing cell |FILEOPEN DOCX Missing cell |padding value imported as |padding value imported as |0.12 cm |0.12 cm (probably duplicate ||of smart justify actually) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140106] ODT->DOCX image partly off page (appears to be broken ODT somehow)
https://bugs.documentfoundation.org/show_bug.cgi?id=140106 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #12 from Regina Henschel --- Problem might be in anchor "to character", when the paragraph does not have any characters. When I insert a non-breakable space in the paragraph, the export is correct. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64795] [FORMATTING] Add new feature of 'keep with previous paragraph' formatting option for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=64795 Justin L changed: What|Removed |Added Priority|medium |lowest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104763] FILESAVE ODT->DOC: image in table anchored to para need to be marked "layout in cell" on export for MSO benefit.
https://bugs.documentfoundation.org/show_bug.cgi?id=104763 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=91 ||632 --- Comment #8 from Justin L --- It is worth noting that MSO has some problems with layout in cell (bug 91632). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91632] msword has some strange "layout in table cell" behaviour
https://bugs.documentfoundation.org/show_bug.cgi?id=91632 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4763 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155809] Insert comment keyboard shortcut (Ctrl+Alt+C) has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=155809 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8269 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71237] insert new comment shortcut (Ctrl+Alt+C) failure
https://bugs.documentfoundation.org/show_bug.cgi?id=71237 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5809 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155809] Insert comment keyboard shortcut (Ctrl+Alt+C) has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=155809 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=71 ||237 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Sounds a lot like bug 38891. Can you please see if: - other Ctrl + Alt shortcuts don't work? - when you use those shortcuts with the cursor on the page (in Writer), do you get some character input, or absolutely nothing happens? See also the meta bug 107244. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126382] Impress/Draw: character Highlight color "No fill" cannot override style highlight on file-open
https://bugs.documentfoundation.org/show_bug.cgi?id=126382 --- Comment #13 from Justin L --- repro 24.2+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119676] CTRL+ALT+E isn't opening the extension dialog but inserts a "é"
https://bugs.documentfoundation.org/show_bug.cgi?id=119676 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=38 ||891 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38891] Ctrl+Alt+? shortcuts don't work on some keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=38891 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||9676 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131173] CRASH: DOC: undoing merge cells
https://bugs.documentfoundation.org/show_bug.cgi?id=131173 Julien Nabet changed: What|Removed |Added Attachment #158458|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
