[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 Adrian Thewlis changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #8 from Adrian Thewlis --- Great questions! 1. It is not deleted, but no longer displayed. 2. I am not familiar with "safe mode". 3. Doesn't happen with a new document! Copy-pasted a chunk of the problem document into a new document, and the problem did not show. Loaded a backed-up version of the document from about 10 days ago, and it didn't display the problem. Since the document is a work-diary, all changes are additions, so I copied all new text from the problem document onto the end of the old copy with no problem, and it still has no problem. So I am back to a full document without the issue. So some sort of document-global setting (not application or profile) was altering the way the hiliting was being rendered across the whole document. Whether the setting change/corruption occured when I upgraded, or if it was some accidental key sequence that switched it, I don't know. Either way, thanks for the questions, that got me on the path back to a happy document! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sd/Library_sd.mk sd/source
sd/Library_sd.mk |1 sd/source/core/ThemeColorChanger.cxx | 19 ++-- sd/source/ui/dlg/UndoThemeChange.cxx | 55 +++ sd/source/ui/inc/UndoThemeChange.hxx | 39 4 files changed, 111 insertions(+), 3 deletions(-) New commits: commit d3b06d044fafec0b31ada9ecbaf60f396555fb12 Author: Tomaž Vajngerl AuthorDate: Sun Aug 27 22:34:13 2023 +0200 Commit: Tomaž Vajngerl CommitDate: Mon Aug 28 07:08:46 2023 +0200 sd: add undo/redo action for changing the model::ColorSet And add the undo action when changing the theme colors in the ThemeColorChanger. Change-Id: Ibeee8aeff420b42fd961e0abd630569e74075585 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156178 Tested-by: Jenkins Reviewed-by: Tomaž Vajngerl diff --git a/sd/Library_sd.mk b/sd/Library_sd.mk index 62a1579dc6aa..3d20e14f0ddd 100644 --- a/sd/Library_sd.mk +++ b/sd/Library_sd.mk @@ -249,6 +249,7 @@ $(eval $(call gb_Library_add_exception_objects,sd,\ sd/source/ui/dlg/sdtreelb \ sd/source/ui/dlg/titledockwin \ sd/source/ui/dlg/unchss \ + sd/source/ui/dlg/UndoThemeChange \ sd/source/ui/docshell/docshel2 \ sd/source/ui/docshell/docshel3 \ sd/source/ui/docshell/docshel4 \ diff --git a/sd/source/core/ThemeColorChanger.cxx b/sd/source/core/ThemeColorChanger.cxx index 020bc1455f6c..adfacb6a47ac 100644 --- a/sd/source/core/ThemeColorChanger.cxx +++ b/sd/source/core/ThemeColorChanger.cxx @@ -24,6 +24,8 @@ #include #include #include +#include +#include using namespace css; @@ -39,7 +41,8 @@ ThemeColorChanger::~ThemeColorChanger() = default; namespace { -void changeTheTheme(SdrPage* pMasterPage, std::shared_ptr const& pColorSet) +void changeThemeColors(sd::DrawDocShell* pDocShell, SdrPage* pMasterPage, + std::shared_ptr const& pNewColorSet) { auto pTheme = pMasterPage->getSdrPageProperties().getTheme(); if (!pTheme) @@ -47,7 +50,17 @@ void changeTheTheme(SdrPage* pMasterPage, std::shared_ptr const pTheme = std::make_shared("Office"); pMasterPage->getSdrPageProperties().setTheme(pTheme); } -pTheme->setColorSet(pColorSet); + +std::shared_ptr const& pOldColorSet = pTheme->getColorSet(); + +auto* pUndoManager = pDocShell->GetUndoManager(); +if (pUndoManager) +{ +pUndoManager->AddUndoAction(std::make_unique( +pDocShell->GetDoc(), pMasterPage, pOldColorSet, pNewColorSet)); +} + +pTheme->setColorSet(pNewColorSet); } bool changeStyle(sd::DrawDocShell* pDocShell, SdStyleSheet* pStyle, @@ -164,7 +177,7 @@ void ThemeColorChanger::apply(std::shared_ptr const& pColorSet) } } -changeTheTheme(mpMasterPage, pColorSet); +changeThemeColors(mpDocShell, mpMasterPage, pColorSet); pUndoManager->LeaveListAction(); } diff --git a/sd/source/ui/dlg/UndoThemeChange.cxx b/sd/source/ui/dlg/UndoThemeChange.cxx new file mode 100644 index ..1270dc06cab7 --- /dev/null +++ b/sd/source/ui/dlg/UndoThemeChange.cxx @@ -0,0 +1,55 @@ +/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ +/* + * This file is part of the LibreOffice project. + * + * This Source Code Form is subject to the terms of the Mozilla Public + * License, v. 2.0. If a copy of the MPL was not distributed with this + * file, You can obtain one at http://mozilla.org/MPL/2.0/. + */ + +#include +#include +#include + +namespace sd +{ +UndoThemeChange::UndoThemeChange(SdDrawDocument* pDocument, SdrPage* pMasterPage, + std::shared_ptr const& pOldColorSet, + std::shared_ptr const& pNewColorSet) +: SdUndoAction(pDocument) +, mpMasterPage(pMasterPage) +, mpOldColorSet(pOldColorSet) +, mpNewColorSet(pNewColorSet) +{ +SetComment(SvxResId(RID_SVXSTR_UNDO_THEME_COLOR_CHANGE)); +} + +namespace +{ +std::shared_ptr getTheme(SdrPage* pMasterPage) +{ +auto pTheme = pMasterPage->getSdrPageProperties().getTheme(); +if (!pTheme) +{ +pTheme = std::make_shared("Office"); +pMasterPage->getSdrPageProperties().setTheme(pTheme); +} +return pTheme; +} +} + +void UndoThemeChange::Undo() +{ +auto pTheme = getTheme(mpMasterPage); +pTheme->setColorSet(mpOldColorSet); +} + +void UndoThemeChange::Redo() +{ +auto pTheme = getTheme(mpMasterPage); +pTheme->setColorSet(mpNewColorSet); +} + +} // end sd namespace + +/* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sd/source/ui/inc/UndoThemeChange.hxx b/sd/source/ui/inc/UndoThemeChange.hxx new file mode 100644 index ..798f2adb50bf --- /dev/null +++ b/sd/source/ui/inc/UndoThemeChange.hxx @@ -0,0 +1,39 @@ +/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ +/* + * This file is part of the LibreOffice project. + * + * This Source Code Form
[Libreoffice-bugs] [Bug 135292] Enabling/disabling (un)ordered list not included in track changes record
https://bugs.documentfoundation.org/show_bug.cgi?id=135292 --- Comment #4 from Telesto --- Still present Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- 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 135292, which changed state. Bug 135292 Summary: Enabling/disabling (un)ordered list not included in track changes record https://bugs.documentfoundation.org/show_bug.cgi?id=135292 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135292] Enabling/disabling (un)ordered list not included in track changes record
https://bugs.documentfoundation.org/show_bug.cgi?id=135292 Telesto changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|NEW Summary|First bullet not included |Enabling/disabling |in track changes|(un)ordered list not ||included in track changes ||record -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156855] Applying to light/dark from LibreOffice -> Preferences > View doesn't properly refresh the UI until restart. (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156855 Telesto changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from Telesto --- Mo need for a sample document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139369] UI Inconsistent screen refresh for conditional Data Bar formatting depending on sort criteria and data values
https://bugs.documentfoundation.org/show_bug.cgi?id=139369 --- Comment #7 from Colin --- (In reply to QA Administrators from comment #6) > > > 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. > Did that - See comment 5 Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128233] macOS: Can't save or open files using Finder dialog on Standard accounts (see comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=128233 greg.diehl@gmail.com changed: What|Removed |Added CC||muddyland...@gmail.com --- Comment #87 from greg.diehl@gmail.com --- *** Bug 154997 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 154997] macOS: infinite spinning wheel when saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=154997 greg.diehl@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from greg.diehl@gmail.com --- Hello Bruce, Thank you for reporting the bug. I see you already mentioned this is a duplicate, so this bug will be resolved as a duplicate of the earlier report. You will automatically be added to the CC list of the other bug. *** This bug has been marked as a duplicate of bug 128233 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156855] Applying to light/dark from LibreOffice -> Preferences > View doesn't properly refresh the UI until restart. (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156855 greg.diehl@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from greg.diehl@gmail.com --- Hello Telesto, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156760] Having a search dialog open makes window keep focus after alt+tab
https://bugs.documentfoundation.org/show_bug.cgi?id=156760 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 153252] Last pages of my writer documents disappear from time to time since the last app update
https://bugs.documentfoundation.org/show_bug.cgi?id=153252 --- Comment #3 from QA Administrators --- Dear Lisa, 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 153252] Last pages of my writer documents disappear from time to time since the last app update
https://bugs.documentfoundation.org/show_bug.cgi?id=153252 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 152402] Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152402] Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 --- Comment #6 from QA Administrators --- Dear nopainenogain12, 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 146543] LibreOffice 7.x hangs on macOS Monterey
https://bugs.documentfoundation.org/show_bug.cgi?id=146543 --- Comment #10 from QA Administrators --- Dear Helmut Seidel M.A., 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 153603] Heading outline shows two heading numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=153603 --- Comment #2 from QA Administrators --- Dear Hemant, 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 153886] Feature request: entry in calc format cells dialogue to change a text field to a formula
https://bugs.documentfoundation.org/show_bug.cgi?id=153886 --- Comment #2 from QA Administrators --- Dear mike.hall, 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 151983] ZWNJ is lost in the fields with dropdown content control
https://bugs.documentfoundation.org/show_bug.cgi?id=151983 --- Comment #2 from QA Administrators --- Dear Hossein, 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 151732] LibreOffice 7.3.6 (Writer & Calc at least) freeze shortly after document is opened
https://bugs.documentfoundation.org/show_bug.cgi?id=151732 --- Comment #5 from QA Administrators --- Dear klpatricio+BZ, 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 73515] EDITING: Legend information disappears after document reload
https://bugs.documentfoundation.org/show_bug.cgi?id=73515 --- Comment #13 from QA Administrators --- Dear opensuse.lietuviu.kalba, 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 72985] EDITING: mismanagement of the "Object with no fill and no line" Images style
https://bugs.documentfoundation.org/show_bug.cgi?id=72985 --- Comment #9 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 69217] When modified Basic code, closing LibreOffice does not ask for confirmation, nor to save modified code
https://bugs.documentfoundation.org/show_bug.cgi?id=69217 --- Comment #12 from QA Administrators --- Dear Lionel Elie Mamane, 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 63799] FORMATTING: Distorted stencil on copy & Paste from Visio 2010
https://bugs.documentfoundation.org/show_bug.cgi?id=63799 --- Comment #8 from QA Administrators --- Dear Malte S. Stretz, 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 139369] UI Inconsistent screen refresh for conditional Data Bar formatting depending on sort criteria and data values
https://bugs.documentfoundation.org/show_bug.cgi?id=139369 --- Comment #6 from QA Administrators --- Dear Colin, 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 142784] FILEOPEN DOCX Hidden first page header cannot be enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=142784 --- Comment #6 from QA Administrators --- Dear NISZ LibreOffice Team, 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 125739] Bullets and Numbering's Linked graphics no longer links to the external file, embeds it into odt instead
https://bugs.documentfoundation.org/show_bug.cgi?id=125739 --- Comment #4 from QA Administrators --- Dear Stephan Bergmann, 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 149254] Make the selection behavior when double-clicking a word a user preference.
https://bugs.documentfoundation.org/show_bug.cgi?id=149254 s5t1e3v4e3...@hotmail.com changed: What|Removed |Added CC||s5t1e3v4e3...@hotmail.com --- Comment #15 from s5t1e3v4e3...@hotmail.com --- May I ask what the compatibility option "Word-compatible trailing blanks" does? I didn't notice any difference and there is no help for that. (see Bug 131235 - Add help for trailing blanks gimmick and other missing compatibility options) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156946] FILEOPEN - csv file import confused between decimal and thousands seperator
https://bugs.documentfoundation.org/show_bug.cgi?id=156946 ady changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from ady --- This report, ATM, is not completely clear. Unless we have a detailed description of which exact parameters are used (ON and OFF) when importing the csv file, the actual result is unknown (and cannot be reproduced by anyone). Additionally, the current subject title of the report reads (in part): " csv file import confused between decimal and thousands separator " which, together with the complete description in comment 0, is mixing field separator, decimal separator and thousand separator. I am tempted to set this report as invalid, but let's give the reporter a chance to clarify by requesting more info > NEEDINFO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Bug 71732 depends on bug 156646, which changed state. Bug 156646 Summary: When using fonts other than pure English fonts, the font height appears to be an unintended height https://bugs.documentfoundation.org/show_bug.cgi?id=156646 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156646] When using fonts other than pure English fonts, the font height appears to be an unintended height
https://bugs.documentfoundation.org/show_bug.cgi?id=156646 خالد حسني changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #8 from خالد حسني --- The font has (Malgun Gothic) has inconsistent line metrics data. It is a complicated issue and there is no way to get it right for all fonts. MS one set of line metrics and LibreOffice chooses another, unfortunately no matter how we change this, some font will break, so we have settled on a heuristic and we are not touching it again. If the default settings are not satisfactory, I suggest manually setting line spacing and not depend on the font’s default. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156955] FILEOPEN PPTX: multiline text with left aligned and right aligned mixed fails to render properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156955 --- Comment #1 from Gerald Pfeifer --- Created attachment 189188 --> https://bugs.documentfoundation.org/attachment.cgi?id=189188=edit Visual comparison PowerPoint (left) vs Impress (right) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153524] FILEOPEN PPTX: wrong text direction and spacing of RTL text in left align text box
https://bugs.documentfoundation.org/show_bug.cgi?id=153524 Gerald Pfeifer changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6955 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156955] New: FILEOPEN PPTX: multiline text with left aligned and right aligned mixed fails to render properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156955 Bug ID: 156955 Summary: FILEOPEN PPTX: multiline text with left aligned and right aligned mixed fails to render properly Product: LibreOffice Version: 6.4 all versions Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ger...@pfeifer.com Created attachment 189187 --> https://bugs.documentfoundation.org/attachment.cgi?id=189187=edit Sample slide (PPTX) Comparing the sample document between PowerPoint and Impress the latter - left aligns all text (instead of right aligning some of it), - uses significantly more vertical space between lines/paragraphs. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e15bf7363adb20c77aee51e09b6f2604d741619b CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US ...and back to (at least) 6.4 all the way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 thesmall...@protonmail.com changed: What|Removed |Added Whiteboard||Bug affects KDE plasma, not ||reproducable on GNOME. Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #10 from thesmall...@protonmail.com --- (In reply to third="Beedell", first="Roke" from comment #9) > Can you confirm that the behaviour is actually different to the version I > quoted? I can't easily test anything newer than what I'm using currently. If > the listed version is indeed as I describe, and the newer version as you > describe, set this as resolved. Better defaults would be a separate issue. Okay, so (on GNOME): LO versions 7.3.4.2 and 7.4.7.2: If I turn on dark theme in my OS, nothing in LO changes. UI stays like it does in light mode, page doesn't change. However, if I go to tools > options > application colors and choose "Libreoffice Dark" in "Scheme", then the page changes to black (and black text is displayed white). UI doesn't change, no matter what I do. In LO version 24.2.0.0.alpha0+ it works as intended (after changing the setting as described). LO will apply the appropriate theme (ui and page) and you don't have to change anything yourself once you changed that setting I described in comment #8. So yes: I can confirm that the behavior is different than on your system. However, I also downloaded KDE Plasma (5.27.5 under wayland) with debian 12, since you mentioned you use it: LO version 7.3.4.2: If your plasma is set to dark (settings > appearance > global theme > breeze dark) LO ui changes to black as well as the page. Works exactly as intended. LO version 7.4.7.2: Page goes black, ui stays like it would in light mode. LO version 24.2.0.0.alpha0+: UI changes accordingly, page *only* if manually set to dark, else it stays white. However, ui changes according to the system if I turn on / off dark mode. (tested with KDE plasma in X11 and same happens) I noticed warnings in the terminal if I execute LO 24.2.0.0.alpha0+ (with KDE) regarding VCL. Seems like it fails to load icons and images but I don't know how that's related to the page display. I also set SAL_USE_VCLPLUGIN=gen and opened LO 24.2.0.0.alpha0+ with the terminal again. Now neither the page nor the ui change to dark mode (SAL_USE_VCLPLUGIN=gtk is the default). I'll change the status to NEW, since it seems to be an KDE plasma related bug. Also, it's NOT RESLOVED for KDE plasma. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 thesmall...@protonmail.com changed: What|Removed |Added Whiteboard||Bug affects KDE plasma, not ||reproducable on GNOME. Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #10 from thesmall...@protonmail.com --- (In reply to third="Beedell", first="Roke" from comment #9) > Can you confirm that the behaviour is actually different to the version I > quoted? I can't easily test anything newer than what I'm using currently. If > the listed version is indeed as I describe, and the newer version as you > describe, set this as resolved. Better defaults would be a separate issue. Okay, so (on GNOME): LO versions 7.3.4.2 and 7.4.7.2: If I turn on dark theme in my OS, nothing in LO changes. UI stays like it does in light mode, page doesn't change. However, if I go to tools > options > application colors and choose "Libreoffice Dark" in "Scheme", then the page changes to black (and black text is displayed white). UI doesn't change, no matter what I do. In LO version 24.2.0.0.alpha0+ it works as intended (after changing the setting as described). LO will apply the appropriate theme (ui and page) and you don't have to change anything yourself once you changed that setting I described in comment #8. So yes: I can confirm that the behavior is different than on your system. However, I also downloaded KDE Plasma (5.27.5 under wayland) with debian 12, since you mentioned you use it: LO version 7.3.4.2: If your plasma is set to dark (settings > appearance > global theme > breeze dark) LO ui changes to black as well as the page. Works exactly as intended. LO version 7.4.7.2: Page goes black, ui stays like it would in light mode. LO version 24.2.0.0.alpha0+: UI changes accordingly, page *only* if manually set to dark, else it stays white. However, ui changes according to the system if I turn on / off dark mode. (tested with KDE plasma in X11 and same happens) I noticed warnings in the terminal if I execute LO 24.2.0.0.alpha0+ (with KDE) regarding VCL. Seems like it fails to load icons and images but I don't know how that's related to the page display. I also set SAL_USE_VCLPLUGIN=gen and opened LO 24.2.0.0.alpha0+ with the terminal again. Now neither the page nor the ui change to dark mode (SAL_USE_VCLPLUGIN=gtk is the default). I'll change the status to NEW, since it seems to be an KDE plasma related bug. Also, it's NOT RESLOVED for KDE plasma. -- You are receiving this mail because: You are on the CC list 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 135292, which changed state. Bug 135292 Summary: First bullet not included in track changes https://bugs.documentfoundation.org/show_bug.cgi?id=135292 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135292] First bullet not included in track changes
https://bugs.documentfoundation.org/show_bug.cgi?id=135292 Aaron changed: What|Removed |Added Resolution|--- |WORKSFORME CC||aaronth...@gmail.com Status|NEW |RESOLVED --- Comment #3 from Aaron --- This bug is no longer reproducible in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded Changing status to RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156842] Export to PDF that includes PDF images are incorrect in size (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 Patrick Luby changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from Patrick Luby --- I see this bug in my local master builds with all Skia/Metal, Skia/Raster, and Skia disabled. I will see if I can isolate where the scaling is occurring in the code. I will post an update when I have any news. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38194] Style indicator in document margin
https://bugs.documentfoundation.org/show_bug.cgi?id=38194 --- Comment #71 from Brian Westlake --- https://help.libreoffice.org/latest/en-US/text/swriter/01/spotlight_styles.html Well, that is, most certainly, a thing of joy and beauty to behold, in LibreOffice v7.6.0 Writer. Thank you very much to all of the developers involved. Best regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well
https://bugs.documentfoundation.org/show_bug.cgi?id=156943 --- Comment #6 from Nadie Nada Nunca --- It's the same in Safe Mode, only the text of the comment is drawn with a white background instead of the regular yellow of the rest of the comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93973] Inconsistent treatment of array formulas if imported, inserted or entered as text using the curly brackets
https://bugs.documentfoundation.org/show_bug.cgi?id=93973 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109236] [META] CSV import bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109236 Bug 109236 depends on bug 93973, which changed state. Bug 93973 Summary: Inconsistent treatment of array formulas if imported, inserted or entered as text using the curly brackets https://bugs.documentfoundation.org/show_bug.cgi?id=93973 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93973] Inconsistent treatment of array formulas if imported, inserted or entered as text using the curly brackets
https://bugs.documentfoundation.org/show_bug.cgi?id=93973 Eike Rathke changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #22 from Eike Rathke --- Array formulas can't be created by text import that way. Period. Not a bug. Won't fix. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156883] The background color of text with trailing spaces is no longer drawn correctly.
https://bugs.documentfoundation.org/show_bug.cgi?id=156883 LeroyG changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #7 from LeroyG --- (In reply to Adrian Thewlis from comment #0) > The space after "Testing " is no longer displayed hilited. 1. Is no longer displayed or is deleted? If it is deleted, choose menu Tools - AutoCorrect - AutoCorrect Options - Options tab, and see if "Delete spaces and tabs at beginning and end of paragraph" and "Apply Styles" are checked. That is not the most probable, unless character style with highlighting is applied. (In reply to Adrian Thewlis from comment #0) > User Profile Reset: No 2. Have you tested in safe mode? 3. The same happens with a new document? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #10 from Piotr Osada --- Created attachment 189186 --> https://bugs.documentfoundation.org/attachment.cgi?id=189186=edit Print all Labels.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #9 from Piotr Osada --- Created attachment 189185 --> https://bugs.documentfoundation.org/attachment.cgi?id=189185=edit Print all Labels by Microsoft Print to PDF.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #8 from Piotr Osada --- Created attachment 189184 --> https://bugs.documentfoundation.org/attachment.cgi?id=189184=edit Narzędzia0.odb -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #7 from Piotr Osada --- Created attachment 189183 --> https://bugs.documentfoundation.org/attachment.cgi?id=189183=edit Etykiety (labels mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #6 from Piotr Osada --- Similar behavior we have in "Labels" mode. When printing all labels into single document via MS Print to PDF (I have not checked printing on paper). Attachments: Etykiety.odt Narzędzia0.odb Print all Labels by Microsoft Print to PDF.png Print all Labels.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #9 from third="Beedell", first="Roke" --- Can you confirm that the behaviour is actually different to the version I quoted? I can't easily test anything newer than what I'm using currently. If the listed version is indeed as I describe, and the newer version as you describe, set this as resolved. Better defaults would be a separate issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #9 from third="Beedell", first="Roke" --- Can you confirm that the behaviour is actually different to the version I quoted? I can't easily test anything newer than what I'm using currently. If the listed version is indeed as I describe, and the newer version as you describe, set this as resolved. Better defaults would be a separate issue. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 139895] [META] PPTX Character formatting issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139895 Bug 139895 depends on bug 150610, which changed state. Bug 150610 Summary: FILEOPEN PPTX: text shows very light instead of dark green (low contrast) https://bugs.documentfoundation.org/show_bug.cgi?id=150610 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156954] implement robust data recovery for lost work (autosave on interval, etc.)
https://bugs.documentfoundation.org/show_bug.cgi?id=156954 --- Comment #1 from libreoff...@caseyconnor.org --- ...and of course a simpler/possibly-more-logical idea would be File->Versions->"[x] autosave a new version every X minutes", possibly incorporating some of the options described for managing number of versions, etc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90796] [META] HiDPI / Retina bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=90796 Bug 90796 depends on bug 155200, which changed state. Bug 155200 Summary: As of version LO 7.4.x.x large branding icon in the thumbnails of the last used documents. https://bugs.documentfoundation.org/show_bug.cgi?id=155200 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Bug 61914 depends on bug 155200, which changed state. Bug 155200 Summary: As of version LO 7.4.x.x large branding icon in the thumbnails of the last used documents. https://bugs.documentfoundation.org/show_bug.cgi?id=155200 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156953] save new file version on close doesn't work if "Don't Save" is clicked when closing
https://bugs.documentfoundation.org/show_bug.cgi?id=156953 libreoff...@caseyconnor.org changed: What|Removed |Added Summary|save new file version on|save new file version on |close even if "Don't Save" |close doesn't work if |is clicked when closing |"Don't Save" is clicked ||when closing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156954] New: implement robust data recovery for lost work (autosave on interval, etc.)
https://bugs.documentfoundation.org/show_bug.cgi?id=156954 Bug ID: 156954 Summary: implement robust data recovery for lost work (autosave on interval, etc.) Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: framework Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@caseyconnor.org I have "save autorecovery info" set to 2 minutes, and "always create backup copy", and File-Versions->"Always save a new version on closing" enabled, but it is still too easy to lose work by accidentally deleting sections and not noticing, or by accidentally clicking "don't save" in the dialog that appears when you close a document, especially when you have multiple documents open, especially if your window manager places Save/Don't Save dialogs in the wrong place, etc. It seems like File->Versions->"Always save a new version on closing" does not save a version when closing if the user does not decide to save changes at the closing dialog. (I filed bug #156953 for that). If that bug is fixed (or I am mistaken), it would help a lot with this. Another potential option would be something like "[x] keep autorecovery information on document close even if crash doesn't happen" and to allow autorecovery to be manually instigated at any time (as long as you do it before the next autorecovery save happens, I suppose) But it would be nice to have more robust mechanisms for recovering older versions of files, lost data, etc. Specifically, an "autosave" function... here's the deluxe dream version for me: [x] automatically save backup copies every X minutes [ ] save backups in same directory as original [ ] prune backup copies in original directory to [ ] maximum age of __ days/hours/minutes [ ] minimum number of backup files to keep: _ [ ] maximum number of files: [ ] maximum total disk usage of backups of a given file (minimum one backup): _ [x] use this centralized directory for all autosave copies: [x] prune backup copies in centralized directory to [x] maximum age of __ days/hours/minutes [x] minimum number of backup files to keep: _3___ [ ] maximum number of files: [ ] maximum total disk usage of backups directory (minimum one backup): _ [x] also save a backup copy when manually saving [x] save a backup copy on exit, whether or not changes are saved on exit [x] attempt to save a backup copy when program crashes ...this is distinct from autorecovery as these copies are accessible whether or not the program crashes, they persist (according to settings), and they are always available. This could also incorporate the timestamp and file metadata ideas in bug #154109. I know there are million things to consider about it (filename collisions, UX details to work out, etc.) It just feels frustrating that in this day and age we should still be able to so easily lose data, especially when editing a little 10k text file. Thanks for considering! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cppcanvas/source include/vcl vcl/source
cppcanvas/source/mtfrenderer/transparencygroupaction.cxx | 67 --- include/vcl/outdev.hxx |5 + vcl/source/outdev/transparent.cxx| 28 +- 3 files changed, 86 insertions(+), 14 deletions(-) New commits: commit e7496f41562b75ea9732ca48f9aa0c07b69e424f Author: Patrick Luby AuthorDate: Fri Aug 25 08:39:46 2023 -0400 Commit: Patrick Luby CommitDate: Sun Aug 27 23:11:29 2023 +0200 tdf#150610 fix broken rendering of text meta actions Even when drawing to a VirtualDevice where antialiasing is disabled, text will still be drawn with some antialiased pixels on HiDPI displays. So, expand the size of the VirtualDevice slightly to capture any of the pixles drawn past the edges of the destination bounds. Change-Id: Ibcba8234708d8784c12f984289ec0a8fcad6694e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156098 Tested-by: Jenkins Reviewed-by: Mike Kaganski Reviewed-by: Patrick Luby diff --git a/cppcanvas/source/mtfrenderer/transparencygroupaction.cxx b/cppcanvas/source/mtfrenderer/transparencygroupaction.cxx index b8350a8f3944..e0caeaa7cf2a 100644 --- a/cppcanvas/source/mtfrenderer/transparencygroupaction.cxx +++ b/cppcanvas/source/mtfrenderer/transparencygroupaction.cxx @@ -205,6 +205,8 @@ namespace cppcanvas::internal return false; } +::Point aMtfOffsetPoint; + // if there's no buffer bitmap, or as soon as the // total transformation changes, we've got to // re-render the bitmap @@ -215,15 +217,59 @@ namespace cppcanvas::internal { DBG_TESTSOLARMUTEX(); +// tdf#150610 fix broken rendering of text meta actions +// Even when drawing to a VirtualDevice where antialiasing +// is disabled, text will still be drawn with some +// antialiased pixels on HiDPI displays. So, expand the +// size of the VirtualDevice slightly to capture any of +// the pixles drawn past the edges of the destination +// bounds. +boolbHasTextActions = false; +MetaAction* pCurrAct; +int nCurrActionIndex; +for( nCurrActionIndex=0, pCurrAct=mpGroupMtf->FirstAction(); + pCurrAct && !bHasTextActions; + ++nCurrActionIndex, pCurrAct = mpGroupMtf->NextAction() ) +{ +switch( pCurrAct->GetType() ) +{ +case MetaActionType::TEXT: +case MetaActionType::TEXTARRAY: +case MetaActionType::STRETCHTEXT: +case MetaActionType::TEXTRECT: +if( ( rSubset.mnSubsetBegin == 0 && rSubset.mnSubsetEnd == -1 ) || ( rSubset.mnSubsetBegin <= nCurrActionIndex && rSubset.mnSubsetEnd > nCurrActionIndex ) ) +bHasTextActions = true; +break; +default: +break; +} +} + // output size of metafile ::Size aOutputSizePixel( ::basegfx::fround( aScale.getX() * maDstSize.getWidth() ), ::basegfx::fround( aScale.getY() * maDstSize.getHeight() ) ); -// pixel size of cache bitmap: round up to nearest int -::Size aBitmapSizePixel( static_cast( aScale.getX() * maDstSize.getWidth() )+1, - static_cast( aScale.getY() * maDstSize.getHeight() )+1 ); +sal_Int32 nBitmapExtra; +if ( bHasTextActions ) +{ +nBitmapExtra = 10; +aMtfOffsetPoint = ::Point( nBitmapExtra / 2, nBitmapExtra / 2 ); +} +else +{ +// Related tdf#150610 assume antialiasing is enabled +// Although antialiasing is normally disabled in the +// VirtualDevice, lines in tdf#150610 will draw past +// the edge of the VirtualDevice when running a +// slideshow so always add an extra pixel on the +// right and bottom edges. +nBitmapExtra = 1; +} -::Point aEmptyPoint; +// pixel size of cache bitmap: round up to nearest int +::Point aBitmapPoint; +::Size aBitmapSizePixel( static_cast(
[Libreoffice-bugs] [Bug 156953] New: save new file version on close even if "Don't Save" is clicked when closing
https://bugs.documentfoundation.org/show_bug.cgi?id=156953 Bug ID: 156953 Summary: save new file version on close even if "Don't Save" is clicked when closing Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: framework Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@caseyconnor.org If enabled, File->Versions->"Always save a new version on closing" does not save a new version if, when closing a file that has changes, you click "Don't Save". My understanding from this: https://help.libreoffice.org/latest/en-US/text/shared/01/0119.html?=SHARED=UNIX ...is that it should do so. If that's not the case, I believe it should do so (in cases where "Don't Save" is clicked by accident, as I recently did and lost a lot of work.) Tested in LibreOffice Writer on Kubuntu 23.04, v7.5.5.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #8 from thesmall...@protonmail.com --- Created attachment 189182 --> https://bugs.documentfoundation.org/attachment.cgi?id=189182=edit LO with light theme applied. (also see dark mode in picture above) Since the pictures provided by some users show a problem regarding dark theme on linux, I want to post here that it had been RESOLVED in the current daily build (maybe earlier too). For reference, here's my post from ask.libreoffice.org: https://ask.libreoffice.org/t/how-to-make-writer-page-adhere-to-system-lo-theme/95069/13?u=thesmallest I downloaded the daily build from 2023-Aug-27 here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb99-TDF/2023-08-27_04.31.13/LibreOfficeDev_24.2.0.0.alpha0_Linux_x86-64_deb.tar.gz. System info (inside virtualbox): OS: Debian GNU/Linux 12 (bookworm) 64-bit Windowing system: Wayland DE: Gnome Libreoffice version (help > about): Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e16e84c44fc7517529c8a183fbd8f97c0c3e380e CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I had to go and change "automatic" from "light" (default) to "system theme" in options > application colors first. Also if I change gnome from light to dark (and vice versa) while the above mentioned libreoffice is still opened, the theme gets applied immediatly and correctly. Not sure if I should set the status to RESOLVED here. See attachments for screenshots. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #8 from thesmall...@protonmail.com --- Created attachment 189182 --> https://bugs.documentfoundation.org/attachment.cgi?id=189182=edit LO with light theme applied. (also see dark mode in picture above) Since the pictures provided by some users show a problem regarding dark theme on linux, I want to post here that it had been RESOLVED in the current daily build (maybe earlier too). For reference, here's my post from ask.libreoffice.org: https://ask.libreoffice.org/t/how-to-make-writer-page-adhere-to-system-lo-theme/95069/13?u=thesmallest I downloaded the daily build from 2023-Aug-27 here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb99-TDF/2023-08-27_04.31.13/LibreOfficeDev_24.2.0.0.alpha0_Linux_x86-64_deb.tar.gz. System info (inside virtualbox): OS: Debian GNU/Linux 12 (bookworm) 64-bit Windowing system: Wayland DE: Gnome Libreoffice version (help > about): Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e16e84c44fc7517529c8a183fbd8f97c0c3e380e CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I had to go and change "automatic" from "light" (default) to "system theme" in options > application colors first. Also if I change gnome from light to dark (and vice versa) while the above mentioned libreoffice is still opened, the theme gets applied immediatly and correctly. Not sure if I should set the status to RESOLVED here. See attachments for screenshots. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #7 from thesmall...@protonmail.com --- Created attachment 189181 --> https://bugs.documentfoundation.org/attachment.cgi?id=189181=edit LO with dark theme applied -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #7 from thesmall...@protonmail.com --- Created attachment 189181 --> https://bugs.documentfoundation.org/attachment.cgi?id=189181=edit LO with dark theme applied -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156951] Recent file list is cluttered. Suggest to filter this by word or calc etc, depending op module
https://bugs.documentfoundation.org/show_bug.cgi?id=156951 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from m.a.riosv --- It is from 7.5 version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #5 from Piotr Osada --- Created attachment 189180 --> https://bugs.documentfoundation.org/attachment.cgi?id=189180=edit One of individual docs Unwanted additional page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #4 from Piotr Osada --- Created attachment 189179 --> https://bugs.documentfoundation.org/attachment.cgi?id=189179=edit Single doc Single doc is clear. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Piotr Osada changed: What|Removed |Added Depends on||156952 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156952 [Bug 156952] Mail merge puts extra page at save as individual documents -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 Piotr Osada changed: What|Removed |Added Blocks||102998 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102998 [Bug 102998] [META] Mail merge bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156950] JAVA JDK not recognised as installed
https://bugs.documentfoundation.org/show_bug.cgi?id=156950 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Maybe an errant question, are both JDK and LibreOffice 32 or 64 bits. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #3 from Piotr Osada --- Created attachment 189178 --> https://bugs.documentfoundation.org/attachment.cgi?id=189178=edit 2_Single_vs_separate_PDFs Actual result and system information: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #2 from Piotr Osada --- Created attachment 189177 --> https://bugs.documentfoundation.org/attachment.cgi?id=189177=edit bug_156952-1_save_merged_documents.png Steps to reproduce. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156946] FILEOPEN - csv file import confused between decimal and thousands seperator
https://bugs.documentfoundation.org/show_bug.cgi?id=156946 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Created attachment 189176 --> https://bugs.documentfoundation.org/attachment.cgi?id=189176=edit Screenshot with option to import properly. See, in the attached screenshot, options to import fine the data, I think. With csv, always it's matter of select the right options. Specially for decimal separator, selecting an adequate locale. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 --- Comment #1 from Piotr Osada --- Created attachment 189175 --> https://bugs.documentfoundation.org/attachment.cgi?id=189175=edit List.ods Spreadsheet of names and addresses. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156952] New: Mail merge puts extra page at save as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=156952 Bug ID: 156952 Summary: Mail merge puts extra page at save as individual documents Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: piotr.os...@gmail.com Created attachment 189174 --> https://bugs.documentfoundation.org/attachment.cgi?id=189174=edit CV Using attached files: CV.odt and List.ods in mail merge mode: Save Merged Documents → Save as a single document. No mater if we choose PDF or ODT, unwanted extra additional page will be inserted at the end of the document. This does not happen with a single large document, as it supposed to be, as well for individual documents. This does not happen with a single large document, as it should also with single documents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156923] The FORMATTING for Hyperlinks extends beyond the Hyperlink Text
https://bugs.documentfoundation.org/show_bug.cgi?id=156923 provisioneer...@gmail.com changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156923] The FORMATTING for Hyperlinks extends beyond the Hyperlink Text
https://bugs.documentfoundation.org/show_bug.cgi?id=156923 --- Comment #2 from provisioneer...@gmail.com --- Created attachment 189173 --> https://bugs.documentfoundation.org/attachment.cgi?id=189173=edit Sample File I'll save it in a different format if that will help or matter. tks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156948] all Sheets have the same scaling settings
https://bugs.documentfoundation.org/show_bug.cgi?id=156948 LeroyG changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from LeroyG --- Can you confirm? Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156948] all Sheets have the same scaling settings
https://bugs.documentfoundation.org/show_bug.cgi?id=156948 LeroyG changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156947] Rounding Corners in Draw and Flowchart cannot be entered
https://bugs.documentfoundation.org/show_bug.cgi?id=156947 --- Comment #2 from Regina Henschel --- The corner radius of the "Alternate Process" shape in the Flowchart category cannot be changed. That is by design and will not be changed, because the shape corresponds to a preset shape in OOXML. And if you need other corner radius you can use the "Rounded Rectangle" instead. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156948] all Sheets have the same scaling settings
https://bugs.documentfoundation.org/show_bug.cgi?id=156948 LeroyG changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from LeroyG --- Choose menu Tools - Options - LibreOffice Calc - View and unmark Synchronize sheets (under Zoom). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156947] Rounding Corners in Draw and Flowchart cannot be entered
https://bugs.documentfoundation.org/show_bug.cgi?id=156947 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from Regina Henschel --- LibreOffice provides two rectangles with essential differences. (1) The "legacy" rectangle. In Writer and Calc you need to customize a toolbar to get it. Search for 'Rectangle' in the customize dialog. In Impress and Draw you can use menu View > Toolbars > Legacy Rectangles. This rectangle has a point edit mode and you can drag the handle. And for this kind of rectangle you can enter the corner radius numerically in the upper part in last tab of the Position and Size dialog. (2) The "Rectangle" from the Basic Shapes category of the custom shapes. That has no rounded corners at all. You can use the "Rounded Rectangle" at same place. It has a handle to set the corner radius. And you can set the position of the handle numerically in the lower part in last tab of the Position and Size dialog. The value is the distance from the left edge of the shape. So when pressing "Points" does not work, you have likely used the "Rectangle" type (2). To distinguish one from another select the shape and look at the icon "Toggle Extrusion". If it is enabled, the rectangle is type (2) otherwise type (1). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122545] FILEOPEN: Error on creating script provider for Python script from location=document
https://bugs.documentfoundation.org/show_bug.cgi?id=122545 --- Comment #14 from Michaela --- Still repro with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e46e663cc350d89e4997095466d675b875eb2e04 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156951] Recent file list is cluttered. Suggest to filter this by word or calc etc, depending op module
https://bugs.documentfoundation.org/show_bug.cgi?id=156951 MikeD changed: What|Removed |Added Summary|Recent file list is |Recent file list is |cluttered. Suggest to |cluttered. Suggest to |filter this by word or calc |filter this by word or calc |tec, depending op module|etc, depending op module -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156951] New: Recent file list is cluttered. Suggest to filter this by word or calc tec, depending op module
https://bugs.documentfoundation.org/show_bug.cgi?id=156951 Bug ID: 156951 Summary: Recent file list is cluttered. Suggest to filter this by word or calc tec, depending op module Product: LibreOffice Version: 7.4.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@mata-ni-bula.com Description: The recent file list is virtually unusable as it is NOT filtered by the type of libre office document / spreadsheet / presentation etc. If I'm opening a file from writer, I need to see recent documents - NOT spreadsheets - which I generally use a lot of. PLEASE add a filter to this list , or SORT by file extension, with the top of the list being the module that is requesting the list. Steps to Reproduce: 1.File>Recent Documents 2. 3. Actual Results: Un-sorted list Expected Results: Sorted list or only documents in writer, only spreadsheets in calc etc. Reproducible: Always User Profile Reset: No Additional Info: N/A -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svx/source
svx/source/accessibility/AccessibleControlShape.cxx | 44 +++- 1 file changed, 16 insertions(+), 28 deletions(-) New commits: commit aa3eea21fcf302ef4ddbba5841037378945f9d5e Author: Arnaud VERSINI AuthorDate: Sun Aug 27 18:44:21 2023 +0200 Commit: Noel Grandin CommitDate: Sun Aug 27 20:46:23 2023 +0200 svx : replace local function with OUStringLiteral Change-Id: Ica39cd5b6da3c97dd03aa9844e2dd8d99c279697 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156170 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/svx/source/accessibility/AccessibleControlShape.cxx b/svx/source/accessibility/AccessibleControlShape.cxx index 8fe42db6dada..e625beaec508 100644 --- a/svx/source/accessibility/AccessibleControlShape.cxx +++ b/svx/source/accessibility/AccessibleControlShape.cxx @@ -61,29 +61,18 @@ using namespace ::com::sun::star::container; namespace { -OUString lcl_getNamePropertyName( ) -{ -return "Name"; -} -OUString lcl_getDescPropertyName( ) -{ -return "HelpText"; -} -OUString lcl_getLabelPropertyName( ) -{ -return "Label"; -} -OUString lcl_getLabelControlPropertyName( ) -{ -return "LabelControl"; -} +constexpr OUStringLiteral NAME_PROPERTY_NAME = u"Name"; +constexpr OUStringLiteral DESC_PROPERTY_NAME = u"HelpText"; +constexpr OUStringLiteral LABEL_PROPERTY_NAME = u"Label"; +constexpr OUStringLiteral LABEL_CONTROL_PROPERTY_NAME = u"LabelControl"; + // return the property which should be used as AccessibleName OUString lcl_getPreferredAccNameProperty( const Reference< XPropertySetInfo >& _rxPSI ) { -if ( _rxPSI.is() && _rxPSI->hasPropertyByName( lcl_getLabelPropertyName() ) ) -return lcl_getLabelPropertyName(); +if ( _rxPSI.is() && _rxPSI->hasPropertyByName( LABEL_PROPERTY_NAME ) ) +return LABEL_PROPERTY_NAME; else -return lcl_getNamePropertyName(); +return NAME_PROPERTY_NAME; } // determines whether or not a state which belongs to the inner context needs to be forwarded to the "composed" @@ -325,7 +314,7 @@ OUString case DRAWING_CONTROL: { // check if we can obtain the "Desc" property from the model -OUString sDesc( getControlModelStringProperty( lcl_getDescPropertyName() ) ); +OUString sDesc( getControlModelStringProperty( DESC_PROPERTY_NAME ) ); if ( sDesc.isEmpty() ) { // no -> use the default aDG.Initialize (STR_ObjNameSingulUno); @@ -333,7 +322,7 @@ OUString aDG.AddProperty ( "ControlBorder", DescriptionGenerator::PropertyType::Integer); } // ensure that we are listening to the Name property -m_bListeningForDesc = ensureListeningState( m_bListeningForDesc, true, lcl_getDescPropertyName() ); +m_bListeningForDesc = ensureListeningState( m_bListeningForDesc, true, DESC_PROPERTY_NAME ); } break; @@ -357,14 +346,14 @@ void SAL_CALL AccessibleControlShape::propertyChange( const PropertyChangeEvent& ::osl::MutexGuard aGuard( m_aMutex ); // check if it is the name or the description -if ( _rEvent.PropertyName == lcl_getNamePropertyName() -|| _rEvent.PropertyName == lcl_getLabelPropertyName() ) +if ( _rEvent.PropertyName == NAME_PROPERTY_NAME +|| _rEvent.PropertyName == LABEL_PROPERTY_NAME ) { SetAccessibleName( CreateAccessibleName(), AccessibleContextBase::AutomaticallyCreated); } -else if ( _rEvent.PropertyName == lcl_getDescPropertyName() ) +else if ( _rEvent.PropertyName == DESC_PROPERTY_NAME ) { SetAccessibleDescription( CreateAccessibleDescription(), @@ -612,7 +601,7 @@ void SAL_CALL AccessibleControlShape::disposing() { // ensure we're not listening m_bListeningForName = ensureListeningState( m_bListeningForName, false, lcl_getPreferredAccNameProperty( m_xModelPropsMeta ) ); -m_bListeningForDesc = ensureListeningState( m_bListeningForDesc, false, lcl_getDescPropertyName() ); +m_bListeningForDesc = ensureListeningState( m_bListeningForDesc, false, DESC_PROPERTY_NAME ); if ( m_bMultiplexingStates ) stopStateMultiplexing( ); @@ -843,12 +832,11 @@ AccessibleControlShape* AccessibleControlShape::GetLabeledByControlShape( ) { if(m_xControlModel.is()) { -const OUString& rAccLabelControlProperty = lcl_getLabelControlPropertyName(); Any sCtlLabelBy; // get the "label by" property value of the control -if (::comphelper::hasProperty(rAccLabelControlProperty, m_xControlModel)) +if (::comphelper::hasProperty(LABEL_CONTROL_PROPERTY_NAME, m_xControlModel)) { -sCtlLabelBy =
[Libreoffice-commits] core.git: sc/qa sc/source
sc/qa/unit/tiledrendering/tiledrendering.cxx |4 ++-- sc/source/ui/docshell/docsh3.cxx |5 - 2 files changed, 6 insertions(+), 3 deletions(-) New commits: commit 34d5abf464dfbf4bdc36f6b87e606c84a1f4d99d Author: Szymon Kłos AuthorDate: Tue Jul 25 14:35:49 2023 +0200 Commit: Caolán McNamara CommitDate: Sun Aug 27 20:42:13 2023 +0200 lok: notify only affected tabs on cell resize When row has automatic height and we type something into one cell - it may be resized. That caused sending document size changed callback to all the views, also affecting all the parts/tabs. This patch calls that only for affected views which are looking at modified parts. It will not invalidate all the tabs when only one is modified. Change-Id: I93e574cf967d608696c1a95ad8b5a7614973c3f5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154891 Tested-by: Jenkins CollaboraOffice Reviewed-by: Caolán McNamara Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156156 Tested-by: Jenkins diff --git a/sc/qa/unit/tiledrendering/tiledrendering.cxx b/sc/qa/unit/tiledrendering/tiledrendering.cxx index 35304683e724..76286912a698 100644 --- a/sc/qa/unit/tiledrendering/tiledrendering.cxx +++ b/sc/qa/unit/tiledrendering/tiledrendering.cxx @@ -1054,7 +1054,7 @@ CPPUNIT_TEST_FIXTURE(ScTiledRenderingTest, testInvalidateOnInserRowCol) aView.m_aInvalidations.clear(); dispatchCommand(mxComponent, ".uno:InsertRows", aArgs); CPPUNIT_ASSERT(aView.m_bInvalidateTiles); -CPPUNIT_ASSERT_EQUAL(size_t(2), aView.m_aInvalidations.size()); +CPPUNIT_ASSERT_EQUAL(size_t(1), aView.m_aInvalidations.size()); CPPUNIT_ASSERT_EQUAL(tools::Rectangle(-75, 51240, 32212230, 63990), aView.m_aInvalidations[0]); // move on the right @@ -1070,7 +1070,7 @@ CPPUNIT_TEST_FIXTURE(ScTiledRenderingTest, testInvalidateOnInserRowCol) aView.m_aInvalidations.clear(); dispatchCommand(mxComponent, ".uno:InsertColumns", aArgs); CPPUNIT_ASSERT(aView.m_bInvalidateTiles); -CPPUNIT_ASSERT_EQUAL(size_t(2), aView.m_aInvalidations.size()); +CPPUNIT_ASSERT_EQUAL(size_t(1), aView.m_aInvalidations.size()); CPPUNIT_ASSERT_EQUAL(tools::Rectangle(254925, -15, 32212230, 63990), aView.m_aInvalidations[0]); } diff --git a/sc/source/ui/docshell/docsh3.cxx b/sc/source/ui/docshell/docsh3.cxx index 789737e5f824..50e99f36f109 100644 --- a/sc/source/ui/docshell/docsh3.cxx +++ b/sc/source/ui/docshell/docsh3.cxx @@ -109,6 +109,7 @@ void ScDocShell::PostPaint( SCCOL nStartCol, SCROW nStartRow, SCTAB nStartTab, void ScDocShell::PostPaint( const ScRangeList& rRanges, PaintPartFlags nPart, sal_uInt16 nExtFlags ) { ScRangeList aPaintRanges; +std::set aTabsInvalidated; for (size_t i = 0, n = rRanges.size(); i < n; ++i) { const ScRange& rRange = rRanges[i]; @@ -167,6 +168,7 @@ void ScDocShell::PostPaint( const ScRangeList& rRanges, PaintPartFlags nPart, sa } } aPaintRanges.push_back(ScRange(nCol1, nRow1, nTab1, nCol2, nRow2, nTab2)); +aTabsInvalidated.insert(nTab1); } Broadcast(ScPaintHint(aPaintRanges.Combine(), nPart)); @@ -176,7 +178,8 @@ void ScDocShell::PostPaint( const ScRangeList& rRanges, PaintPartFlags nPart, sa if ((nPart & (PaintPartFlags::Top | PaintPartFlags::Left)) && comphelper::LibreOfficeKit::isActive()) { ScModelObj* pModel = GetModel(); -SfxLokHelper::notifyDocumentSizeChangedAllViews(pModel); +for (auto nTab : aTabsInvalidated) +SfxLokHelper::notifyPartSizeChangedAllViews(pModel, nTab); } }
[Libreoffice-bugs] [Bug 122474] FILEOPEN XLSX, Pivot table gets refreshed automatically when opened in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122474 --- Comment #9 from Michaela --- Still repro with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e46e663cc350d89e4997095466d675b875eb2e04 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156950] New: JAVA JDK not recognised as installed
https://bugs.documentfoundation.org/show_bug.cgi?id=156950 Bug ID: 156950 Summary: JAVA JDK not recognised as installed Product: LibreOffice Version: unspecified Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kermit...@live.co.uk Not very computer savvy, I'm 76 and I don't understand why versions since v7.44 will not recognise that java v20.0.2 is really installed on my M2 macbook pro. looks like I am stuck with v7.44 if using BASE, which is all the time! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156924] Issues with grid controls on Base forms and Gtk
https://bugs.documentfoundation.org/show_bug.cgi?id=156924 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Julien Nabet --- On pc Debian x86-64 with master sources updated today, I confirm gen rendering is ok and smooth but gtk rendering is even worse for me, up/down arrows don't work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/content.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3f2484d071edb415216f5a2d09d146005cdd063e Author: Andrea Gelmini AuthorDate: Sun Aug 27 00:06:19 2023 +0200 Commit: Julien Nabet CommitDate: Sun Aug 27 18:46:57 2023 +0200 Fix typo Change-Id: Iadaed462970f7bc70769664920524ac2c193433a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156152 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/sw/source/uibase/utlui/content.cxx b/sw/source/uibase/utlui/content.cxx index 54593eead31f..e836bbee122b 100644 --- a/sw/source/uibase/utlui/content.cxx +++ b/sw/source/uibase/utlui/content.cxx @@ -2988,7 +2988,7 @@ bool SwContentTree::HasContentChanged() // Set_id needs to be done here because FillMemberList clears the content type member // list and refills with new data making the previously set id invalid. If there is no -// content change detected the Dispay function will not be called and the tree entry +// content change detected the Display function will not be called and the tree entry // user data will not be set to the new content member pointer address. OUString sSubId(weld::toId(pCnt)); m_xTreeView->set_id(*xEntry, sSubId);
[Libreoffice-commits] core.git: xmlsecurity/README.md
xmlsecurity/README.md |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 6d58d3aa8620a23abd0dfdc3cda86aa51bc88268 Author: Andrea Gelmini AuthorDate: Sun Aug 27 00:06:44 2023 +0200 Commit: Julien Nabet CommitDate: Sun Aug 27 18:46:24 2023 +0200 Fix typo Change-Id: I618431147060b4bec7d1957b949dc270eeaafdd2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156153 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/xmlsecurity/README.md b/xmlsecurity/README.md index 80259e6dcbf9..5d45e36119eb 100644 --- a/xmlsecurity/README.md +++ b/xmlsecurity/README.md @@ -24,7 +24,7 @@ the exported PDF files. It is also possible to sign existing PDF files. ## Source Primary Contents - * `component`: Main implementation of `DocumentDigitalSignatuers` where the interaction with security environment and certificates occur. + * `component`: Main implementation of `DocumentDigitalSignatures` where the interaction with security environment and certificates occur. * `dialogs`: Certificate & Signatures management dialogs. * `certificatechooser`: Dialog that allows you to find and choose certificates or signatures for encryption. * `certificateviewer`: More detailed information about each certificate.
[Libreoffice-commits] core.git: xmlsecurity/qa
xmlsecurity/qa/create-certs/create-dump-certs.sh |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit e0142562a1dafb7d1d1b60684934525dbbeb76c0 Author: Andrea Gelmini AuthorDate: Sun Aug 27 00:07:30 2023 +0200 Commit: Julien Nabet CommitDate: Sun Aug 27 18:46:00 2023 +0200 Fix typo Change-Id: I9880e5a7957bf2124f1ce8d9fc0cd3e44e129e65 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156154 Tested-by: Julien Nabet Reviewed-by: Julien Nabet diff --git a/xmlsecurity/qa/create-certs/create-dump-certs.sh b/xmlsecurity/qa/create-certs/create-dump-certs.sh index 4056ddb1a404..95e8de9c6f5a 100644 --- a/xmlsecurity/qa/create-certs/create-dump-certs.sh +++ b/xmlsecurity/qa/create-certs/create-dump-certs.sh @@ -8,7 +8,7 @@ # # This script generates 100 certificates (modifiable) for cases of testing UI latency for instance. # -# Basically, it creates certificates with sender same as reciever following User [number] pattern. +# Basically, it creates certificates with sender same as receiver following User [number] pattern. # for ((i=1; i<=100; i++))
[Libreoffice-bugs] [Bug 111746] Rotation applied on title shape is not removed by resetting the layout
https://bugs.documentfoundation.org/show_bug.cgi?id=111746 --- Comment #11 from Regina Henschel --- Rotation of title shape on master is not applied to the slides title and the other way round, a rotation on a slides title is not removed by applying the master to that slide. Tested with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156949] New: Incorrect capitalization after number when Lightproof grammar checker(English) is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156949 Bug ID: 156949 Summary: Incorrect capitalization after number when Lightproof grammar checker(English) is enabled Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: steveja...@gmail.com Description: When I type a number such as "12pm" it unexpectedly gets changed to "12Pm". When I uncheck the box next to "Lightproof grammar checker(English)" under Options.Language Settings.Writing Aids the problem no longer occurs. Steps to Reproduce: 1. type a number such as "12pm" without the quotes 2. 3. Actual Results: see the incorrect change in capitalization Expected Results: no change in capitalization Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156948] New: all Sheets have the same scaling settings
https://bugs.documentfoundation.org/show_bug.cgi?id=156948 Bug ID: 156948 Summary: all Sheets have the same scaling settings Product: LibreOffice Version: 7.5.3.2 release Hardware: PowerPC OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mixa...@gmail.com Description: all Sheets have the same scaling settings Steps to Reproduce: 1. Sheet1 scaling 100%, Sheet2 scaling 100% 2. Open Sheet1, make scaling not 100% ( doesn't matter, 50 - 200% ) 3. Go to Sheet2, scaling on page 2 also changed Actual Results: interferes with work 8-( Expected Results: different pages should have different scaling, because there may be different data. and this seriously interferes with work (sorry for comparing, but I recently switched to your product after Microsoft, and this is my first inconvenience) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156947] New: Rounding Corners in Draw and Flowchart cannot be entered
https://bugs.documentfoundation.org/show_bug.cgi?id=156947 Bug ID: 156947 Summary: Rounding Corners in Draw and Flowchart cannot be entered Product: LibreOffice Version: 7.5.2.2 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ronaldniels...@gmail.com Description: After drawing a rectangle, pressing "Points" does not result in a small frame in the upper left corner. Many minor procedural variations were tried, but none worked. Either the software or the instructions are not correct. Setup: Win 10 32 bit Pro, HP Desktop, LibreOffice 7.5.5.2 (also 7.4...). Alternative for me: Include an a flowchart oval (not an ellipse) as a standard shape in the table. Steps to Reproduce: 1. In Draw or Flowchart 2. Select and Draw Rectangle 3. Click Points Icon at screen top or on lists in at least 2 other places. Actual Results: No response Expected Results: The instructions say a small frame should appear at the upper left corner of the rectangle. Reproducible: Always User Profile Reset: No Additional Info: Creating Round Corners When you insert a rectangle or a callout box using the drawing functions and activate the Points icon on the Drawing toolbar, you see a small frame at the upper left corner of the object. The frame indicates the amount by which the corners are rounded. When the frame is positioned at the top left corner, no rounding occurs. When the frame is positioned on the handle centered at the top of the object, the corners are rounded as much as possible. You adjust the degree of rounding by moving the frame between these two positions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156946] New: FILEOPEN - csv file import confused between decimal and thousands seperator
https://bugs.documentfoundation.org/show_bug.cgi?id=156946 Bug ID: 156946 Summary: FILEOPEN - csv file import confused between decimal and thousands seperator Product: LibreOffice Version: 7.3.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: veeti.junkk...@gmail.com Created attachment 189171 --> https://bugs.documentfoundation.org/attachment.cgi?id=189171=edit a simple file which replicates the issue when opening a csv file which uses a decimal seperator which happens to also be used as a thousands seperator, calc will assume it to be a thousands seperator first and a decimal seperator second. This causes a weird situation, where some numbers are considered decimals and others are considered to be integers. To replicate open the attached bug.csv with semicolon as the cell delimiter and English (USA) language. doing this will show the decimal sperator on all three cells containing it in the preview, but when you actually open the document cell B2 will be an integer while cells A2 and C2 will be decimal numbers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #6 from third="Beedell", first="Roke" --- Thanks for that. It's great to hear. Hopefully this is just a bug experienced by KDE users. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 149611] Allow the page to adhere to the theme of the system.
https://bugs.documentfoundation.org/show_bug.cgi?id=149611 --- Comment #6 from third="Beedell", first="Roke" --- Thanks for that. It's great to hear. Hopefully this is just a bug experienced by KDE users. -- You are receiving this mail because: You are on the CC list for the bug.