[Libreoffice-bugs] [Bug 154143] New: The explanatory image in Tips of The Day looked blurred and something not professional
https://bugs.documentfoundation.org/show_bug.cgi?id=154143 Bug ID: 154143 Summary: The explanatory image in Tips of The Day looked blurred and something not professional Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: riz...@libreoffice.org Created attachment 185912 --> https://bugs.documentfoundation.org/attachment.cgi?id=185912=edit A merged screenshot of ToTD explanatory images Steps to reproduce 1. Open any LibreOffice module 2. Navigate to Help > Show Tip of The Day 3. Click Next Tip to see all available tips -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151710] Toolbar button for enclosing text in () brackets
https://bugs.documentfoundation.org/show_bug.cgi?id=151710 --- Comment #11 from Jim Raykowski --- The first [3] reference in my previous post [3] https://design.blog.documentfoundation.org/2018/02/28/easyhacking-all-about-terminology/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151710] Toolbar button for enclosing text in () brackets
https://bugs.documentfoundation.org/show_bug.cgi?id=151710 --- Comment #10 from Jim Raykowski --- An article that illustrates how to add an UNO command for Calc[1] Examples of two UNO commands added to Writer[2] officecfg/registry/schema/org/openoffice/Office/UI/Commands.xcs contains information on properties used in the .xcu file. There is also information about commands here[3]. Decide on a name for the command. It probably should be generic to allow other than enclosing selected text with parenthesis. Perhaps something like .uno:EncloseText or .uno:SurroundText. Loop through the cursor ring[3] to get each cursor selection PaM[4] and text. Create an enclosed string by placing the selection text between open and close parenthesis, adding optional enclosures is an advanced hack that can be done for bonus points after implementing the parens request :-), then use the IDocumentContentOperations::ReplaceRange function[5] to replace the text at the PaM with the created enclosure string. [1] https://dev.blog.documentfoundation.org/2022/02/23/adding-a-new-uno-command/ [2] https://gerrit.libreoffice.org/c/core/+/91605 [3] for (SwPaM& rPaM : SwWrtShell::GetCursor()->GetRingContainer()) [4] sw/inc/pam.hxx [5] sw/source/core/view/viewsh.cxx SwViewShell::getIDocumentContentOperations() hint: SwWrtShell is derived from SwViewShell -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144813] Tabbed UI (drop down box) and sidebar options - rapid blinking/flashing when GTK_IM_MODULE=xim
https://bugs.documentfoundation.org/show_bug.cgi?id=144813 Jewgeni changed: What|Removed |Added CC||jewgeni.smir...@mail.ru --- Comment #20 from Jewgeni --- *** Bug 154134 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 154134] Annoying white blinking of welcome screen and some menu elements by moving the mouse (XFCE)
https://bugs.documentfoundation.org/show_bug.cgi?id=154134 Jewgeni changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Jewgeni --- Hello and THANK YOU! I found the file .xinputrc in my home folder and deleted it. After restarting the system, LibreOffice runs without this blinking. Yes, this is a dupe of bug 144813, so I'll change the status accordingly. Cheers! *** This bug has been marked as a duplicate of bug 144813 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 Mike Kaganski changed: What|Removed |Added Resolution|WORKSFORME |INVALID --- Comment #3 from Mike Kaganski --- WORKSFORME is for "there was a problem, but at some point, the problem disappeared as a result of unknown changes". In this case, INVALID fits best, since the issue did not exist, so the bug report told things that weren't true (it told that it's not possible to do A, when it was a user mistake). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153877] vertical Unicode SMP chars not displayed correctly when exported as PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=153877 Dieter changed: What|Removed |Added Component|Writer |Printing and PDF export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153809] Undo action (Ctrl+Z) does not revert changes to table design formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=153809 --- Comment #4 from Maxim Monastirsky --- (In reply to Stéphane Guillou (stragu) from comment #3) > I assume changes to designs should be undoable Absolutely. > just like changes to styles. Note that changes to style are neither undoable. This is a general problem in Impress. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153834] Ajout d'une fonction récepteur "=" dans un dessin "Carré" ou "Rectangle" ou "Zone de texte" dans LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153834 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 153831] Disfonctionnement des animations dans LibreOffice Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153831 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 150314] TABLAS DINAMICAS
https://bugs.documentfoundation.org/show_bug.cgi?id=150314 --- Comment #4 from QA Administrators --- Dear antoniogomezort...@gmail.com, 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 153826] PROBLEM W/ CREATED FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=153826 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 149583] Crash if I open the Printer properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=149583 --- Comment #3 from QA Administrators --- Dear domtour, 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 153815] Removing table jumps to start of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153815 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 150314] TABLAS DINAMICAS
https://bugs.documentfoundation.org/show_bug.cgi?id=150314 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95037] Tabulation in twocolumn mode
https://bugs.documentfoundation.org/show_bug.cgi?id=95037 --- Comment #11 from QA Administrators --- Dear p10, 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 140919] [UI][Configuration]"Add more icon themes via extension" does not work if no document is open
https://bugs.documentfoundation.org/show_bug.cgi?id=140919 --- Comment #3 from QA Administrators --- Dear pierre-yves samyn, 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 88182] Sidebar: Undocked sidebar is an unusable size without resizing, doesn't expand automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=88182 --- Comment #13 from QA Administrators --- Dear tmacalp, 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 140926] Memory usage still high after presentation has ended
https://bugs.documentfoundation.org/show_bug.cgi?id=140926 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135709] Changing as character to 'to character' enabled parallel wrap with ODT and DOCX but wrap through in DOC
https://bugs.documentfoundation.org/show_bug.cgi?id=135709 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116145] Inserting columns using selected (grouped) sheets causes calculation error.
https://bugs.documentfoundation.org/show_bug.cgi?id=116145 --- Comment #7 from QA Administrators --- Dear Julian Morris, 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 135203] gotoEndOfUsedArea doesn't give the correct position number of the Calc cell at the end when its background color is changed from the initial color.
https://bugs.documentfoundation.org/show_bug.cgi?id=135203 --- Comment #4 from QA Administrators --- Dear Nukool Chompuparn, 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 112344] Display of Hyperlinks in Text Boxes and Drawing Objects is Different to Display in Normal Text
https://bugs.documentfoundation.org/show_bug.cgi?id=112344 --- Comment #5 from QA Administrators --- Dear Harald Koester, 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 105503] Tabstoptype in ruler not changeable
https://bugs.documentfoundation.org/show_bug.cgi?id=105503 --- Comment #6 from QA Administrators --- Dear Manfred, 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 154142] Crash in: SfxUndoManager::SetMaxUndoActionCount(unsigned __int64)
https://bugs.documentfoundation.org/show_bug.cgi?id=154142 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please, could you add the step to reproduce the crash. And also, past here the info in Menu/Help/About LibreOffice (there is a button to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90730] support overlay/no-overlay for chart title
https://bugs.documentfoundation.org/show_bug.cgi?id=90730 --- Comment #9 from Ekta --- Hello, I want to work on this. Can someone please let me know how to get started? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154142] New: Crash in: SfxUndoManager::SetMaxUndoActionCount(unsigned __int64)
https://bugs.documentfoundation.org/show_bug.cgi?id=154142 Bug ID: 154142 Summary: Crash in: SfxUndoManager::SetMaxUndoActionCount(unsigned __int64) Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gords...@shaw.ca This bug was filed from the crash reporting server and is br-79a5c643-2e5d-4423-93f1-9f7db94dea4b. = -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 Eike Rathke changed: What|Removed |Added Hardware|Other |All OS|macOS (All) |All CC||er...@redhat.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154120] Need ability to mark characters to be ignored for line height calculation
https://bugs.documentfoundation.org/show_bug.cgi?id=154120 --- Comment #5 from Regina Henschel --- (In reply to Eyal Rozenberg from comment #0) > LibreOffice calculates line height based on aspects of the font(s) used for > the characters on the line. However, occasionally, you may want to keep the > line height uniform despite the line containing a couple of characters in > another language, with the computed line height being different. For that purpose you can set the line space to a fixed value. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154140] Bring back the transparency option
https://bugs.documentfoundation.org/show_bug.cgi?id=154140 --- Comment #2 from Eyal Rozenberg --- What was the rationale for moving it to Expert Options? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154125] INDEX() does not return a vector of an array if that is only a vector, but only the first element
https://bugs.documentfoundation.org/show_bug.cgi?id=154125 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154035] setting tabs in writer not possible from clic on top ruler (GTK3?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154035 raal changed: What|Removed |Added Regression By||Michael Stahl Keywords||bibisected, bisected CC||michael.st...@allotropia.de --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.6. Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? Thanks 134be7c58b05aa3cec939901f66430b2f87b8e4e is the first bad commit commit 134be7c58b05aa3cec939901f66430b2f87b8e4e Author: Jenkins Build User Date: Fri Feb 24 09:15:20 2023 +0100 source sha:db115bec9254417ef7a3faf687478fe5424ab378 147024: tdf#78510 sw,cui: split SvxLRSpaceItem for SwTextNode, SwTextFormatColl | https://gerrit.libreoffice.org/c/core/+/147024 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154141] LO Writer will not print to HP OJ Pro 8610
https://bugs.documentfoundation.org/show_bug.cgi?id=154141 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please paste here your OS and LibreOffice version, Menu/Help/About LibreOffice, there is an icon to copy. If you quit LibreOffice, it stays in the queue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154035] setting tabs in writer not possible from clic on top ruler (GTK3?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154035 raal changed: What|Removed |Added Keywords||regression Ever confirmed|0 |1 CC||r...@post.cz Status|UNCONFIRMED |NEW --- Comment #2 from raal --- Confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 288c0920a8475f9f2c537212e04aa7649192ad8c CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154125] INDEX() does not return a vector of an array if that is only a vector, but only the first element
https://bugs.documentfoundation.org/show_bug.cgi?id=154125
Eike Rathke changed:
What|Removed |Added
CC||mikekagan...@hotmail.com
--- Comment #5 from Eike Rathke ---
@Mike:
Does full (non-online) Excel do vector replication in INDEX()? i.e. with
array-row separator ; semicolon does
=INDEX({1;2};0;2)
return error, or does it return column vector {1;2}? (transform separators to
whatever is correct for your Excel..)
Similar, does
=INDEX({1;2};2;2)
return error, or 2?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg --- Comment #4 from m.a.riosv --- Reproducible Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a179f6c91692076e7e17babf4890638caa398384 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154140] Bring back the transparency option
https://bugs.documentfoundation.org/show_bug.cgi?id=154140 Telesto changed: What|Removed |Added Keywords|needsUXEval | --- Comment #1 from Telesto --- FWIW: The TransparentSelectionPercentage of 75 to high for my taste. To much transparency, making hard to notice the cell selection on my macbook with greenish system colors -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- But such non-volatile functions don't avoid to change with a calculation [F9] or a hard recacl [Ctrl+Shift+F9] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153283] Application crashes when printing in Windows 10 from Writer or Calc (HP Printer)
https://bugs.documentfoundation.org/show_bug.cgi?id=153283 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4141 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154141] LO Writer will not print to HP OJ Pro 8610
https://bugs.documentfoundation.org/show_bug.cgi?id=154141 Dieter changed: What|Removed |Added Component|Writer |Printing and PDF export See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3283 CC||dgp-m...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154140] Bring back the transparency option
https://bugs.documentfoundation.org/show_bug.cgi?id=154140 Telesto changed: What|Removed |Added Keywords||needsUXEval CC||eyalr...@gmx.com, ||heiko.tietze@documentfounda ||tion.org, ||libreoffice-ux-advise@lists ||.freedesktop.org, ||tele...@surfxs.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154035] setting tabs in writer not possible from clic on top ruler (GTK3?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154035 Telesto changed: What|Removed |Added Summary|setting tabs in writer not |setting tabs in writer not |possible from clic on top |possible from clic on top |ruler |ruler (GTK3?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154125] INDEX() does not return a vector of an array if that is only a vector, but only the first element
https://bugs.documentfoundation.org/show_bug.cgi?id=154125
--- Comment #4 from Eike Rathke ---
You are complicating things and just repeating what I gave..
=INDEX({11;21};0;1)
CSE is exactly the column vector case I said is not working as it should.
=INDEX({11|12};1;0)
CSE the same but for row vector.
Fwiw, you can see in the Function Wizard what actually is returned for the
examples; whether the formula is entered as CSE-array or normal only affects
how the final result is displayed, either as full array result (CSE) or just
the single top left element's value (normal).
> in Excel I believe that =INDEX({1,2};2) should had been #REF!
But it isn't, is it?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154134] Annoying white blinking of welcome screen and some menu elements by moving the mouse (XFCE)
https://bugs.documentfoundation.org/show_bug.cgi?id=154134 --- Comment #4 from V Stuart Foote --- see the work up in see also bug 144813 If your GTK_IM_MODULE=xim, rework with an "export GTK_IM_MODULE=ibus", maybe deleting ~/.xinputrc, to see if that resolves. If so, this is a dupe of bug 144813 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154141] New: LO Writer will not print to HP OJ Pro 8610
https://bugs.documentfoundation.org/show_bug.cgi?id=154141 Bug ID: 154141 Summary: LO Writer will not print to HP OJ Pro 8610 Product: LibreOffice Version: 7.5.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ajc...@gmail.com First day using LO Writer. I cannot print a simple document to my HP OffieJet Pro 8610. I can see the document in the queue, but I cannot make it print. It shows "Unknown Status" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154135] Librewriter autocomplete no long working
https://bugs.documentfoundation.org/show_bug.cgi?id=154135 V Stuart Foote changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 --- Comment #2 from Alexander Van den Panhuysen --- Why do you link 154137 to 154136 ? These are two different things! 154136 is about not working shortcuts on an AZERTY keyboard, and 154137 is a request to have two new functions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154135] Librewriter autocomplete no long working
https://bugs.documentfoundation.org/show_bug.cgi?id=154135 ctyou...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #2 from ctyou...@gmail.com --- Thank you that appears to fix it. Thought i had it changed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 Eyal Rozenberg changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=70 | |180 | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70180] Enhance Drop Caps effect to support Raised, Sunken and Dropped initials
https://bugs.documentfoundation.org/show_bug.cgi?id=70180 Eyal Rozenberg changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4139| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 Eyal Rozenberg changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Eyal Rozenberg --- (In reply to RGB from comment #1) > It's already possible to assign character styles to drop caps You're right, sorry. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154140] New: Bring back the transparency option
https://bugs.documentfoundation.org/show_bug.cgi?id=154140 Bug ID: 154140 Summary: Bring back the transparency option Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ville...@t-online.de Description: Old versions had Tools>Options>LibreOffice>View Selection.Transparency on/off and percentage Transparency option is now hidden in the "expert options". My most popular answer on ask.libreoffice.org is this: https://ask.libreoffice.org/t/asked-before-calc-ver-7-3-1-3-highlighted-cell-color/75738/4 Steps to Reproduce: 1. Select any cell or range in Calc. Select any text in any component 2. 3. Actual Results: Selection is highlighted in a color that is set up on system level. A spreadsheet's active cell has a thin coloured border. Expected Results: With org.openoffice.Office.Common.DrawingLayer.TransparentSelection = OFF all selections are highlighted in colors complementary to the highlighted items, borders, text, areas which is very easy to spot even in colorful situations. Reproducible: Always User Profile Reset: No Additional Info: Office suites are used by elderly people who suffer a lot from bad UI design. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4136 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4137 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94763] Changing theme in Design sidebar deck isn't undoable (steps in comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=94763 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3809 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153809] Undo action (Ctrl+Z) does not revert changes to table design formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=153809 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Blocks||100366 CC||momonas...@gmail.com, ||stephane.guillou@libreoffic ||e.org Summary|Undo action (Ctrl+Z) does |Undo action (Ctrl+Z) does |not revert some operations |not revert changes to table ||design formatting Version|7.5.0.3 release |7.5.0.0 alpha1+ Whiteboard| QA:needsComment| Keywords||implementationError See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=94 ||763 Status|UNCONFIRMED |NEW --- Comment #3 from Stéphane Guillou (stragu) --- Reproduced in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 082d009b6a156faa74c9966b0dffc5fa6ce22287 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Maxim, what do you think? I assume changes to designs should be undoable just like changes to styles. I tested at f23d3661ab04601650db95f846081317fc06801d and it was already like that back then. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153809 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153809 [Bug 153809] Undo action (Ctrl+Z) does not revert changes to table design formatting -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 RGB changed: What|Removed |Added CC||rgb.m...@gmail.com --- Comment #1 from RGB --- It's already possible to assign character styles to drop caps, just pick one from the "character style" drop down list under "Contents" when "Display drop caps" is checked. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154125] INDEX() does not return a vector of an array if that is only a vector, but only the first element
https://bugs.documentfoundation.org/show_bug.cgi?id=154125
--- Comment #3 from ady ---
Using LO 7.4.5, here is what I have tested ("|" is column separator, ";" as
both row and argument separators).
In a pre-dynamic formula context, with INDEX() in array form *by itself*:
A_
{ =INDEX({11|12;21|22};0;1) } (with CSE)
=11 (1st row, 1st col)
=21 (2nd row, 1st col)
OK.
B_
=INDEX({11|12;21|22};0;1) (_no_ CSE)
=11 (1st row only)
OK.
C_
{ =INDEX({11;21};0;1) } (with CSE)
=11 (1st row)
NOT OK. We should also get:
=21 (2nd row)
D_
=INDEX({11;21};0;1) (_no_ CSE)
=11 (1st row)
OK, but expected considering result "C" above.
E_
{ =INDEX({11|12};1;0) } (with CSE)
=11 (1st col)
NOT OK. We should also get:
=12 (2nd col)
F_
=INDEX({11|12};1;0) (_no_ CSE)
=11 (1st col)
OK, but expected considering result "E" above.
Considering that those are wrong results already, I have not tested additional
possibilities such as default values when arguments are omitted, or
out-of-scope arguments, or wrong-type arguments.
Please note that these are examples of INDEX() by itself. When INDEX() is used
as lookup_array for MATCH() (as in the example in comment 0), then CSE should
not be required in order to obtain the array to be fed for MATCH().
Once the above examples get to work, I should be able to test them in
combination with MATCH() as in the example in comment 0.
PS: FWIW, in Excel I believe that =INDEX({1,2};2) should had been #REF!, IIUC
(whether with CSE or not).
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154134] Annoying white blinking of welcome screen and some menu elements by moving the mouse (XFCE)
https://bugs.documentfoundation.org/show_bug.cgi?id=154134 --- Comment #3 from Jewgeni --- If I understand your question correctly: I have the xim module. What exactly must be changed? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=70 ||180 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70180] Enhance Drop Caps effect to support Raised, Sunken and Dropped initials
https://bugs.documentfoundation.org/show_bug.cgi?id=70180 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4139 --- Comment #19 from Eyal Rozenberg --- Good idea. Also, perhaps we should support setting a CS for the drop-cap contents. Opening a bug for that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154139] New: Support specifying a character style for drop caps
https://bugs.documentfoundation.org/show_bug.cgi?id=154139 Bug ID: 154139 Summary: Support specifying a character style for drop caps Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Paragraph styles support a "drop cap" of the first character or word. Now, when using drop caps, one often wants to play with aspects of the font, draw a border around the drop cap etc. That can be achieved either with a Character Style. It therefore makes sense to specify a CS to set the drop cap in, which may be different than the paragraph's "own" CS features. Inspired by: Bug 70180. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107661] [META] SIDEBAR: Design (aka Document themes) tab
https://bugs.documentfoundation.org/show_bug.cgi?id=107661 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||94763 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=94763 [Bug 94763] Changing theme in Design sidebar deck isn't undoable (steps in comment 8) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94763] Changing theme in Design sidebar deck isn't undoable (steps in comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=94763 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||107661 CC||stephane.guillou@libreoffic ||e.org Summary|Changing theme in Design|Changing theme in Design |isn't undoable |sidebar deck isn't undoable ||(steps in comment 8) Hardware|Other |All --- Comment #8 from Stéphane Guillou (stragu) --- Still the case in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 082d009b6a156faa74c9966b0dffc5fa6ce22287 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Steps: 1. Tools > Options > Advanced > Enable experimental features > OK (needs a restart) 2. Add a Heading level 1 in document body 3. In the Sidebar, open the Design deck, double-click e.g. the "Modern" style preset, see the heading change 4. Undo Result: applying the style preset can't be undone. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107661 [Bug 107661] [META] SIDEBAR: Design (aka Document themes) tab -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153828] Lagging with GTK
https://bugs.documentfoundation.org/show_bug.cgi?id=153828 Caolán McNamara changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Caolán McNamara --- does SAL_DISABLE_CURSOR_INDICATOR=1 make a difference in performance to you? If so, then this might be a duplicate of bug 148433, which remains a mystery however. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154120] Need ability to mark characters to be ignored for line height calculation
https://bugs.documentfoundation.org/show_bug.cgi?id=154120 --- Comment #4 from Eyal Rozenberg --- (In reply to m.a.riosv from comment #1) > I'm sorry, but I don't like it when every user's idea could become a new > development. 1. This is a disingenuous way to treat bug reports / feature requests. These are opened by a single user, but typically regard usage scenarios encountered by a large number of users. 2. If a user has a good idea, their report should be confirmed. That does not mean developers are supposed to place it high on their priority list - that's a different kind of decision. > Apart from this case seems to be of rather limited use. That's the only relevant argument. But - I disagree. Why do you believe that there is limited use for embedding one/a small number of different-language-group words in a paragraph? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99671] [META] Gallery bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=99671 Bug 99671 depends on bug 132847, which changed state. Bug 132847 Summary: Not all shapes in gallery shown in Detailed View rendered automatically https://bugs.documentfoundation.org/show_bug.cgi?id=132847 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149570] Can't undo removing columns / rows until leaving the table or adding to history stack (steps in comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=149570 Stéphane Guillou (stragu) changed: What|Removed |Added CC||caol...@redhat.com Version|7.4.5.1 release |7.4.0.0 alpha1+ Keywords|bibisectRequest |bibisected, bisected --- Comment #5 from Stéphane Guillou (stragu) --- Bibisected with linux-64-7.4 repo to first bad commit 6510e2270f35e0faffcb66742917c9674de5f5f3 which points to core commit: commit ae0e7e3918284c31a91acca0f733919926ae3a62 author Caolán McNamara Thu Apr 14 11:20:23 2022 +0100 committer Caolán McNamara Thu Apr 14 16:10:20 2022 +0200 treec23d0a76fdf2fdaa73b7c352428d7dd6deb723bb parent 590323f4235e5ec3de2dc6dee28a4f03288ac6d7 tdf#141812 keep focus in an impress table cell when row/col deleted Change-Id: I3b396ba92039bad657ca159002598a271b68a79d First tag is 7.4.0.0.alpha1 Caolán, can you please have a look? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145565] (Enhancement) In Writer, make it easier to align forms to text
https://bugs.documentfoundation.org/show_bug.cgi?id=145565 MarjaE changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #6 from MarjaE --- 1. Open the file. 2. Go to Form > Design Mode. 3. Select a field. 4. Copy it and paste it. If you paste it to an empty line, it will cause the next row to jump up. If you paste it alongside an existing row, it won't have much effect alongside the larger text, but it will increase line spacing alongside the smaller text. 5. Try to resize it to fit the smaller text. It won't. 6. Try to drag-and-drop to compare one form field to another. It won't, and the whole page will be thrown into disarray. Trying to drag it back into place can make it worse. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 --- Comment #1 from ady --- The following tip might help, but it may also need some adjustment. Introducing a static value for DATE and/or TIME can (potentially) be achieved by adequate keyboard shortcuts (when using the classic English USA QUERTY keyboard layout). Insert current date (static): [CTRL]+[;] Insert current time (static, i.e. timestamp): [CTRL]+[SHIFT][;] You can also: 1. Enter edit mode (F2) 2. [CTRL]+[;] 3. [SPACE] bar (for example) 4. [CTRL]+[SHIFT][;] 5. [ENTER] Introducing any of the above in one cell allows you to use it "statically", i.e. it will not get updated unless you change it manually. Then you can use that cell in other formulas. These keyboard shortcuts might not work with other keyboard layouts (bug?), but you can go to menu Tools > Customize > Keyboard and adapt it to your needs. Independently of the requested functions, the correct functionality of the mentioned keyboard shortcuts (or alternative ones) for non-QUERTY(USA) layouts / languages should be checked and corrected if necessary (because it does not always work as users expect). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 --- Comment #6 from Alexander Van den Panhuysen --- Shortcut Command+; to become a Datestamp, is doing nothing either. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154120] Need ability to mark characters to be ignored for line height calculation
https://bugs.documentfoundation.org/show_bug.cgi?id=154120 --- Comment #3 from V Stuart Foote --- (In reply to V Stuart Foote from comment #2) > Can see the utility to this, but not clear ODF can accommodate. > > We're already wrestling with issues like bug 71080 and bug 136448 for Drop > caps handling, seems excluding characters/word text runs within a paragraphs > line height metrics would require similar. > > Kind of complex though, as not just the line height but also the text width > for the span would need to be tracked to avoid overrun and place correctly. > > We currently can place draw shape text boxes to provide this kind of layout > (wrap and anchor). But in-line as "ignored" paragraph text could be of > use--think writing mixed polyglot content in line. s/71080/bug 70180/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154135] Librewriter autocomplete no long working
https://bugs.documentfoundation.org/show_bug.cgi?id=154135 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from V Stuart Foote --- Have you checked enabled Tools -> AutoCorrect -> AutoCorrect Options -> Word Completion 'Enable word completion'? It is disabled by default. When checked enabled entries on the collected words will autocomplete. Checkboxes will also control collection and retention of "collected" words per document as saved to user profile. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154126] Writer: Drawing object not positioned at very bottom of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=154126 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4128 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154128] Writer: Drawing object becomes invisible when flushed to next page
https://bugs.documentfoundation.org/show_bug.cgi?id=154128 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4126 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154128] Writer: Drawing object becomes invisible when flushed to next page
https://bugs.documentfoundation.org/show_bug.cgi?id=154128 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression Version|7.4.5.1 release |6.0.0.3 release --- Comment #2 from Telesto --- Version: 7.0.7.0.0+ (x64) Build ID: 626ea4e62a3e5005fe9825923a1c0c5bdb61cc08 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL Version: 6.2.9.0.0+ (x86) Build ID: 5f01fe15eb2661f1f9ce12d1d99dc2a705b462ee CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL and in Version: 6.0.0.0.alpha0+ Build ID: 9127d1a89cbfba89eb9df6755ea7b9e161cfc67a CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL fine with Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; Locale: nl-NL (nl_NL) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154120] Need ability to mark characters to be ignored for line height calculation
https://bugs.documentfoundation.org/show_bug.cgi?id=154120 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rb.hensc...@t-online.de, ||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- Can see the utility to this, but not clear ODF can accommodate. We're already wrestling with issues like bug 71080 and bug 136448 for Drop caps handling, seems excluding characters/word text runs within a paragraphs line height metrics would require similar. Kind of complex though, as not just the line height but also the text width for the span would need to be tracked to avoid overrun and place correctly. We currently can place draw shape text boxes to provide this kind of layout (wrap and anchor). But in-line as "ignored" paragraph text could be of use--think writing mixed polyglot content in line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107243] [META] Locale keyboard shortcut issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107243 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154136 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154136 [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126888] Ctrl+Shift+; shortcut to insert current time stopped working
https://bugs.documentfoundation.org/show_bug.cgi?id=126888 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4136 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107243] [META] Locale keyboard shortcut issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107243 Bug 107243 depends on bug 154136, which changed state. Bug 154136 Summary: In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing. https://bugs.documentfoundation.org/show_bug.cgi?id=154136 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||107243 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6888 Ever confirmed|1 |0 Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #5 from Stéphane Guillou (stragu) --- My understanding is that it would have the same root cause. I'm happy to set back to unconfirmed until someone else who knows more about keyboard layout detection chimes in. What happens if you use the Date field shortcut, Command + ; ? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107243 [Bug 107243] [META] Locale keyboard shortcut issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 --- Comment #4 from Alexander Van den Panhuysen --- Excuse me? Resolved? Duplicate of bug 129547 ?! I am talking about LibreOffice on MacBook Air which is an Apple computer with a build-in AZERTY keyboard, in the help Tip I read "Command", not "Ctrl". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 raal changed: What|Removed |Added Keywords||bibisected, bisected Regression By||Tomaž Vajngerl CC||qui...@gmail.com --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.5. Adding Cc: to Tomaž Vajngerl ; Could you possibly take a look at this one? Thanks c5d7bc8c3c8241acb4d6913b6038c2da164de170 is the first bad commit commit c5d7bc8c3c8241acb4d6913b6038c2da164de170 Author: Jenkins Build User Date: Sun Sep 11 17:44:07 2022 +0200 source sha:c747486335c089baf440b8f040d3ffdc14aa5049 139683: basegfx: replace typedef with a class B2DSize based on Size2D | https://gerrit.libreoffice.org/c/core/+/139683 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 --- Comment #2 from raal --- Created attachment 185911 --> https://bugs.documentfoundation.org/attachment.cgi?id=185911=edit printscreen -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 --- Comment #1 from raal --- Created attachment 185910 --> https://bugs.documentfoundation.org/attachment.cgi?id=185910=edit test file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 raal changed: What|Removed |Added CC||r...@post.cz Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154138] New: "Change line color" animation effect for rectangle, bottom line
https://bugs.documentfoundation.org/show_bug.cgi?id=154138 Bug ID: 154138 Summary: "Change line color" animation effect for rectangle, bottom line Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: r...@post.cz Description: "Change line color" animation effect for rectangle, bottom line line not colored. It works for fat lines. Steps to Reproduce: 1.apply "Change line color" animation effect for rectangle Actual Results: bottom line not changed Expected Results: all sides of rectangle's lines changed the color Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 288c0920a8475f9f2c537212e04aa7649192ad8c CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded it worked in Version: 6.0.0.0.alpha1+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129547] Default shortcut key for insert current time doesn't work (French)
https://bugs.documentfoundation.org/show_bug.cgi?id=129547 Stéphane Guillou (stragu) changed: What|Removed |Added CC||dralexander_vandenpanhuysen ||@telenet.be --- Comment #32 from Stéphane Guillou (stragu) --- *** Bug 154136 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 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Stéphane Guillou (stragu) --- Thank you, Alexander. That makes your report a duplicate of the older bug 129547. *** This bug has been marked as a duplicate of bug 129547 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154125] INDEX() does not return a vector of an array if that is only a vector, but only the first element
https://bugs.documentfoundation.org/show_bug.cgi?id=154125
--- Comment #2 from Eike Rathke ---
Note that in Excel the cases
=INDEX({1;2};0;0)
=INDEX({1,2};0;0)
=INDEX({1,2;3,4};0;0)
with both row_num=0 and column_num=0 that they document to not work at all and
return error. There is no compelling reason though why it shouldn't and it
works in Calc.
Additionally there is a working case that they do not document, if the array is
a one-dimensional row vector then if column_num is not given then the row_num
argument acts as a column index. E.g.
=INDEX({1,2};2)
returns 2, as does
=INDEX({1,2};0;2)
That is specified by ODFF v1.3 in 6.14.6 INDEX
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html#INDEX
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144813] Tabbed UI (drop down box) and sidebar options - rapid blinking/flashing when GTK_IM_MODULE=xim
https://bugs.documentfoundation.org/show_bug.cgi?id=144813 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4134 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154134] Annoying white blinking of welcome screen and some menu elements by moving the mouse (XFCE)
https://bugs.documentfoundation.org/show_bug.cgi?id=154134 V Stuart Foote changed: What|Removed |Added Summary|Annoying white blinking of |Annoying white blinking of |welcome screen and some |welcome screen and some |menu elements by moving the |menu elements by moving the |mouse |mouse (XFCE) CC||ilmari.lauhakangas@libreoff ||ice.org, ||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4813 --- Comment #2 from V Stuart Foote --- another GTK_IM_MODULE=xim .xinputrc profile issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154124] "Change line color" animation effect for tables doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=154124 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 See Also||https://bz.apache.org/ooo/s ||how_bug.cgi?id=116435 Status|UNCONFIRMED |NEW --- Comment #1 from raal --- Confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 288c0920a8475f9f2c537212e04aa7649192ad8c CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 --- Comment #2 from Alexander Van den Panhuysen --- I am using a AZERTY keyboard which is the normal used keyboard in Belgium for the Dutch people. It works fully correct. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94079] NETWORKDAYS gives error #VALUE! when Holidays range is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=94079 --- Comment #16 from Mike Kaganski --- (In reply to Supriyo Paul from comment #15) > Sorry for the inconvenience I caused. Thank you so much for your > information, I will update the patch as soon as possible.. No need to be sorry, these things happen to all of us. It is reverted, and so is no more a blocker; I am looking forward to see the new unit test commit from you. Looking how the older one was implemented, I suggest you to use fixed dates in ISO format in the calls to ScDocument::SetString, instead of the NOW() spreadsheet function. Thank you for your contribution! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94079] NETWORKDAYS gives error #VALUE! when Holidays range is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=94079 --- Comment #15 from Supriyo Paul --- (In reply to Laurent Balland from comment #13) > (In reply to Commit Notification from comment #12) > > Supriyo Paul committed a patch related to this issue. > > It has been pushed to "master": > > > > https://git.libreoffice.org/core/commit/ > > e9697e315cd382ce14b5c8efc47a07aa06dea30c > > > > tdf#94079 sc_ucalc: Add unit test > > > > It will be available in 7.6.0. > > > > The patch should be included in the daily builds available at > > https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More > > information about daily builds can be found at: > > https://wiki.documentfoundation.org/Testing_Daily_Builds > > > > Affected users are encouraged to test the fix and report feedback. > > This test fails for me if I run it on Saturday or Sunday, but succeeds for > all other days. Please use fixed date for the test. I need to wait till > Monday in order to let Jenkins be happy with my commit :-( Hi Laurent, Sorry for the inconvenience I caused. Thank you so much for your information, I will update the patch as soon as possible.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154136] In Help I found Command+Shift+; to have a timestamp in a Calc cell, but it is doing nothing.
https://bugs.documentfoundation.org/show_bug.cgi?id=154136 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- What keyboard layout do you use? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154129] FILEOPEN DOCX: framePr anchored to text, not page when unspecified
https://bugs.documentfoundation.org/show_bug.cgi?id=154129 Justin L changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94079] NETWORKDAYS gives error #VALUE! when Holidays range is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=94079 --- Comment #14 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2fccec4078f9cdcfa42447c2217d52035dc8fc3e Revert "tdf#94079 sc_ucalc: Add unit test" It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
