[Libreoffice-bugs] [Bug 153199] writer and impress freeze after closing other program adobe illustrator
https://bugs.documentfoundation.org/show_bug.cgi?id=153199 --- Comment #2 from fadil.fikril...@gmail.com --- - i tried photoshop, it doesn't produce the bug - it does happen with LibreOffice Calc - Version: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 12; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: id-ID (id_ID); UI: id-ID Calc: CLVersion: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 12; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: id-ID (id_ID); UI: id-ID Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: basic/qa
basic/qa/vba_tests/chr.vb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 263c15ee238e04c7b25d36cdbb9ab21c0bdf518d Author: Andreas Heinisch AuthorDate: Wed Jan 25 11:16:00 2023 + Commit: Andreas Heinisch CommitDate: Thu Jan 26 07:45:25 2023 + Delete extra whitespaces inserted by the editor Change-Id: I89ef4d04e27e52f5ee6168f368e23f96e112a8be Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146085 Tested-by: Jenkins Reviewed-by: Andreas Heinisch diff --git a/basic/qa/vba_tests/chr.vb b/basic/qa/vba_tests/chr.vb index 5dc85a0c9157..f9bc7ea12aa5 100644 --- a/basic/qa/vba_tests/chr.vb +++ b/basic/qa/vba_tests/chr.vb @@ -21,7 +21,7 @@ Sub verify_testCHR() TestUtil.AssertEqual(Chr(87), "W", "Chr(87)") TestUtil.AssertEqual(Chr(105), "i", "Chr(105)") TestUtil.AssertEqual(Chr(35), "#", "Chr(35)") - + ' tdf#145693 - argument name should be 'charcode' instead of 'string' TestUtil.AssertEqual(Chr(charcode:=35), "#", "Chr(charcode:=35)")
[Libreoffice-bugs] [Bug 152907] blank space after cropping image
https://bugs.documentfoundation.org/show_bug.cgi?id=152907 Dieter changed: What|Removed |Added Summary|blank space after cutting |blank space after cropping |picture |image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152907] blank space after cutting picture
https://bugs.documentfoundation.org/show_bug.cgi?id=152907 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Blocks||108280 Whiteboard| QA:needsComment| --- Comment #4 from Dieter --- I confirm it with Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Open attachment 184511 2. Select first image -> Context menu -> Crop 3. Crop around 1cm from top 4. Crop around 1 cm from bottom Actual result: Blank space between formatting mark and image Additional information Doesn't happen with properties -> crop Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108280 [Bug 108280] [META] Image crop bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108280] [META] Image crop bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108280 Dieter changed: What|Removed |Added Depends on||152907 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152907 [Bug 152907] blank space after cutting picture -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/sdi
sw/sdi/_textsh.sdi |1 - 1 file changed, 1 deletion(-) New commits: commit cba2fda9ce2a82d874b86e585b576cb7d551d64d Author: Miklos Vajna AuthorDate: Wed Jan 25 20:08:18 2023 +0100 Commit: Miklos Vajna CommitDate: Thu Jan 26 07:38:41 2023 + sw, FN_DELETE_TEXT_FORMFIELDS: remove unused StateMethod FN_DELETE_TEXT_FORMFIELDS is only handled in SwTextShell::ExecField() and SwTextShell::StateField() doesn't seem to have a default handler for slots not mentioned explicitly, so this is not needed. Change-Id: I00bc3c543c44d541d352748c721be43b76965e32 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146144 Tested-by: Jenkins Reviewed-by: Miklos Vajna diff --git a/sw/sdi/_textsh.sdi b/sw/sdi/_textsh.sdi index d8ec5afef933..cca84716962f 100644 --- a/sw/sdi/_textsh.sdi +++ b/sw/sdi/_textsh.sdi @@ -1827,7 +1827,6 @@ interface BaseText FN_DELETE_TEXT_FORMFIELDS [ ExecMethod = ExecField ; -StateMethod = StateField ; ] FN_PROTECT_FIELDS
[Libreoffice-bugs] [Bug 138587] Using the navigator upsets optimal zoom setting
https://bugs.documentfoundation.org/show_bug.cgi?id=138587 Dieter changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #6 from Dieter --- VERIFIED with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1c638b7ac46d8077994c8483e6becc4a33efd12b CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded Jim, thank you for fixing it! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153205] Selection not cleared after copying text by "control-dragging"
https://bugs.documentfoundation.org/show_bug.cgi?id=153205 --- Comment #3 from Ulrich Windl --- Created attachment 184916 --> https://bugs.documentfoundation.org/attachment.cgi?id=184916=edit Windows Recording showing the effect I can reproduce the issue in Windows 100%, but in Linux only occasionally. For the recording: Towards the end I first position the cursor at the end by clicking then I press a character (that makes the text inserted before disappear again). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152534] Dark Mode on Windows 11 Active selections from the tabbed menu bar have light blue background which makes the white icon almost invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=152534 --- Comment #3 from Sebastiaan Veld --- Same issue in 7.5.0.2. Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sd/qa xmloff/source
sd/qa/uitest/data/tdf153161_FlushToSave.odp |binary
sd/qa/uitest/impress_tests2/tdf153161.py| 37
xmloff/source/draw/shapeexport.cxx | 12 +
3 files changed, 49 insertions(+)
New commits:
commit 8d05f9c8c12f09c2fc963b6afb71447015f432b2
Author: Mike Kaganski
AuthorDate: Wed Jan 25 01:37:00 2023 +0300
Commit: Mike Kaganski
CommitDate: Thu Jan 26 07:16:26 2023 +
tdf#153161: (Ab)use a call to XTextRange::getString to flush edits
Restore the call (without checking its returned value), removed in commit
d194474aabd699806cb3631bc8641dd0548b8026 ("tdf#151100: xText->getString()
may be empty for content needing export", 2022-09-22), side effects of
which obviously allow some object's changes to get flushed and saved.
Change-Id: I62f27cd056c32ad76f79a4862e2f4a0964eaadef
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146106
Tested-by: Mike Kaganski
Reviewed-by: Mike Kaganski
(cherry picked from commit d183daea1abbd7b564d083298874dd7c40d5a5b3)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146081
diff --git a/sd/qa/uitest/data/tdf153161_FlushToSave.odp
b/sd/qa/uitest/data/tdf153161_FlushToSave.odp
new file mode 100644
index ..1fd5c20c2a52
Binary files /dev/null and b/sd/qa/uitest/data/tdf153161_FlushToSave.odp differ
diff --git a/sd/qa/uitest/impress_tests2/tdf153161.py
b/sd/qa/uitest/impress_tests2/tdf153161.py
new file mode 100644
index ..db14d7986f5b
--- /dev/null
+++ b/sd/qa/uitest/impress_tests2/tdf153161.py
@@ -0,0 +1,37 @@
+# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-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/.
+#
+
+from libreoffice.uno.propertyvalue import mkPropertyValues
+from uitest.framework import UITestCase
+from uitest.uihelper.common import get_url_for_data_file
+
+class TestTdf153161(UITestCase):
+
+def testTdf153161(self):
+url = get_url_for_data_file('tdf153161_FlushToSave.odp')
+
+with self.ui_test.load_file(url) as document:
+oldText = document.DrawPages[0].getByIndex(1).String
+self.assertTrue(oldText.startswith('在没有版本控制系统的时期'))
+
+xImpressDoc = self.xUITest.getTopFocusWindow()
+xEditWin = xImpressDoc.getChild('impress_win')
+xEditWin.executeAction('SELECT',
mkPropertyValues({'OBJECT':'Unnamed Drawinglayer object 1'}))
+
+# Type something, getting into text editing mode (appending)
automatically
+xEditWin.executeAction('TYPE', mkPropertyValues({'TEXT': 'Foo
Bar'}))
+xToolkit =
self.xContext.ServiceManager.createInstance('com.sun.star.awt.Toolkit')
+xToolkit.processEventsToIdle()
+self.xUITest.executeCommand('.uno:Save')
+
+# Reload and check that the edit was saved
+with self.ui_test.load_file(url) as document:
+self.assertEqual(oldText + 'Foo Bar',
document.DrawPages[0].getByIndex(1).String)
+
+# vim: set shiftwidth=4 softtabstop=4 expandtab:
diff --git a/xmloff/source/draw/shapeexport.cxx
b/xmloff/source/draw/shapeexport.cxx
index 51ee4c894250..6e687e746ba4 100644
--- a/xmloff/source/draw/shapeexport.cxx
+++ b/xmloff/source/draw/shapeexport.cxx
@@ -310,6 +310,18 @@ void XMLShapeExport::collectShapeAutoStyles(const
uno::Reference< drawing::XShap
uno::Reference< text::XText > xText(xShape, uno::UNO_QUERY);
if (xText.is())
{
+try
+{
+// tdf#153161: it seems that the call to XTextRange::getString
flushes the changes
+// for some objects, that otherwise fail to get exported
correctly. Maybe at some
+// point it would make sense to find a better place for more
targeted flush.
+xText->getString();
+}
+catch (uno::RuntimeException const&)
+{
+// E.g., SwXTextFrame that contains only a table will throw;
this is not an error
+}
+
uno::Reference< beans::XPropertySetInfo > xPropSetInfo(
xPropSet->getPropertySetInfo() );
if( xPropSetInfo.is() &&
xPropSetInfo->hasPropertyByName("IsEmptyPresentationObject") )
[Libreoffice-bugs] [Bug 153205] Selection not cleared after copying text by "control-dragging"
https://bugs.documentfoundation.org/show_bug.cgi?id=153205 Ulrich Windl changed: What|Removed |Added CC||ulrich.wi...@rz.uni-regensb ||urg.de --- Comment #2 from Ulrich Windl --- Created attachment 184915 --> https://bugs.documentfoundation.org/attachment.cgi?id=184915=edit Screenshot Windows: About (In reply to raal from comment #1) > Please copy and paste here the contents of your Help - About from your > LibreOffice. This allows us to know more about your system. >From Linux: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - sd/source sd/util solenv/bin solenv/clang-format
sd/source/ui/framework/configuration/ConfigurationController.cxx |9
sd/source/ui/framework/configuration/ConfigurationUpdater.cxx|3
sd/source/ui/framework/configuration/ConfigurationUpdater.hxx| 14 -
sd/source/ui/framework/configuration/ResourceFactoryManager.cxx |3
sd/source/ui/framework/configuration/ResourceFactoryManager.hxx |7
sd/source/ui/framework/factories/BasicPaneFactory.cxx| 92
+++---
sd/source/ui/framework/factories/BasicToolBarFactory.cxx | 71 ++-
sd/source/ui/framework/factories/BasicViewFactory.cxx| 73 ++-
sd/source/ui/framework/module/ModuleController.cxx | 37 +---
sd/source/ui/framework/module/SlideSorterModule.cxx | 10 -
sd/source/ui/framework/module/SlideSorterModule.hxx |6
sd/source/ui/inc/framework/ConfigurationController.hxx |4
sd/source/ui/inc/framework/ModuleController.hxx |7
sd/source/ui/inc/framework/factories/BasicPaneFactory.hxx| 12 -
sd/source/ui/inc/framework/factories/BasicToolBarFactory.hxx | 12 -
sd/source/ui/inc/framework/factories/BasicViewFactory.hxx| 12 -
sd/source/ui/unoidl/DrawController.cxx |8
sd/util/sd.component | 12 -
solenv/bin/native-code.py|3
solenv/clang-format/excludelist |6
20 files changed, 155 insertions(+), 246 deletions(-)
New commits:
commit bfb8706466b52298def33d47d31b6efffc3ed531
Author: Noel Grandin
AuthorDate: Wed Jan 25 10:09:55 2023 +0200
Commit: Noel Grandin
CommitDate: Thu Jan 26 06:36:45 2023 +
no need for sd::ModuleController to load these factories via UNO
Change-Id: I2ac1d29ff9cbd5c8676dc1957a62ea02454d052e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146122
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sd/source/ui/framework/factories/BasicPaneFactory.cxx
b/sd/source/ui/framework/factories/BasicPaneFactory.cxx
index 64cec425ad54..e112ac4c315a 100644
--- a/sd/source/ui/framework/factories/BasicPaneFactory.cxx
+++ b/sd/source/ui/framework/factories/BasicPaneFactory.cxx
@@ -20,7 +20,7 @@
#include
#include
-#include "BasicPaneFactory.hxx"
+#include
#include "ChildWindowPane.hxx"
#include "FrameWindowPane.hxx"
@@ -84,67 +84,23 @@ public:
//= PaneFactory ===
BasicPaneFactory::BasicPaneFactory (
-const Reference& rxContext)
+const Reference& rxContext,
+const rtl::Reference<::sd::DrawController>& rxController)
: mxComponentContext(rxContext),
mpViewShellBase(nullptr),
mpPaneContainer(new PaneContainer)
{
-}
-
-BasicPaneFactory::~BasicPaneFactory()
-{
-}
-
-void BasicPaneFactory::disposing(std::unique_lock&)
-{
-Reference xCC (mxConfigurationControllerWeak);
-if (xCC.is())
-{
-xCC->removeResourceFactoryForReference(this);
-xCC->removeConfigurationChangeListener(this);
-mxConfigurationControllerWeak.clear();
-}
-
-for (const auto& rDescriptor : *mpPaneContainer)
-{
-if (rDescriptor.mbIsReleased)
-{
-Reference xComponent (rDescriptor.mxPane, UNO_QUERY);
-if (xComponent.is())
-{
-xComponent->removeEventListener(this);
-xComponent->dispose();
-}
-}
-}
-}
-
-void SAL_CALL BasicPaneFactory::initialize (const Sequence& aArguments)
-{
-if (!aArguments.hasElements())
-return;
-
try
{
-// Get the XController from the first argument.
-Reference xController (aArguments[0],
UNO_QUERY_THROW);
-
// Tunnel through the controller to obtain access to the ViewShellBase.
-try
-{
-if (auto pController =
dynamic_cast(xController.get()))
-mpViewShellBase = pController->GetViewShellBase();
-}
-catch(RuntimeException&)
-{}
+mpViewShellBase = rxController->GetViewShellBase();
-Reference xCM (xController, UNO_QUERY_THROW);
-Reference xCC
(xCM->getConfigurationController());
+Reference xCC
(rxController->getConfigurationController());
mxConfigurationControllerWeak = xCC;
// Add pane factories for the two left panes (one for Impress and one
for
// Draw) and the center pane.
-if (xController.is() && xCC.is())
+if (rxController.is() && xCC.is())
{
PaneDescriptor aDescriptor;
aDescriptor.msPaneURL = FrameworkHelper::msCenterPaneURL;
@@ -190,6 +146,34 @@ void SAL_CALL BasicPaneFactory::initialize (const
Sequence& aArguments)
}
}
+BasicPaneFactory::~BasicPaneFactory()
+{
+}
+
+void BasicPaneFactory::disposing(std::unique_lock&)
+{
+Reference xCC
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 152844, which changed state. Bug 152844 Summary: Footnote separator alignment + Footnote paragraph direction flip in LO->MSO->LO round-trip https://bugs.documentfoundation.org/show_bug.cgi?id=152844 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INSUFFICIENTDATA|--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109195 Bug 109195 depends on bug 152844, which changed state. Bug 152844 Summary: Footnote separator alignment + Footnote paragraph direction flip in LO->MSO->LO round-trip https://bugs.documentfoundation.org/show_bug.cgi?id=152844 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INSUFFICIENTDATA|--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152844] Footnote separator alignment + Footnote paragraph direction flip in LO->MSO->LO round-trip
https://bugs.documentfoundation.org/show_bug.cgi?id=152844 Fahad Al-Saidi changed: What|Removed |Added Resolution|INSUFFICIENTDATA|--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152844] Footnote separator alignment + Footnote paragraph direction flip in LO->MSO->LO round-trip
https://bugs.documentfoundation.org/show_bug.cgi?id=152844 --- Comment #5 from Fahad Al-Saidi --- Created attachment 184914 --> https://bugs.documentfoundation.org/attachment.cgi?id=184914=edit rtl footnote odt saving RTL footnote to docx is broken from long time. I test it in these cases: 1- saving odt as docx then open it in ms office. 2- saving odt as docx then open it in libre office. use the attachment to test it -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152286] wrong text formatting with copy paste
https://bugs.documentfoundation.org/show_bug.cgi?id=152286 Dieter changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38481] Envelope layout wrong for centered lengthwise (OKI printers)
https://bugs.documentfoundation.org/show_bug.cgi?id=38481 --- Comment #32 from Todd --- still a problem as of 7.4.4 Makes me wonder what exactly the developers think the users user LO for. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152977] improve help for the search attribute "Individual Words"
https://bugs.documentfoundation.org/show_bug.cgi?id=152977 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 153121] Comment inside Slide
https://bugs.documentfoundation.org/show_bug.cgi?id=153121 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152976] Left/right pages not properly displayed in preview
https://bugs.documentfoundation.org/show_bug.cgi?id=152976 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 152974] Forms: Borders of text controls switch to 3D if form has been edited in LO 7.5.0.1 and reopened in older versions
https://bugs.documentfoundation.org/show_bug.cgi?id=152974 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 152973] Forms: Default color for buttons and borders changed to dark grey
https://bugs.documentfoundation.org/show_bug.cgi?id=152973 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153171] suggestion: add option to add x number of rows/columns in the menu
https://bugs.documentfoundation.org/show_bug.cgi?id=153171 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153200] Some CJK characters are not oriented correctly in vertical mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153200 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153171] suggestion: add option to add x number of rows/columns in the menu
https://bugs.documentfoundation.org/show_bug.cgi?id=153171 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153200] Some CJK characters are not oriented correctly in vertical mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153200 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153171] suggestion: add option to add x number of rows/columns in the menu
https://bugs.documentfoundation.org/show_bug.cgi?id=153171 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153171] suggestion: add option to add x number of rows/columns in the menu
https://bugs.documentfoundation.org/show_bug.cgi?id=153171 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152286] wrong text formatting with copy paste
https://bugs.documentfoundation.org/show_bug.cgi?id=152286 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152286] wrong text formatting with copy paste
https://bugs.documentfoundation.org/show_bug.cgi?id=152286 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151903] Crash when using removeChildByIndex of node in TreeControl
https://bugs.documentfoundation.org/show_bug.cgi?id=151903 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151903] Crash when using removeChildByIndex of node in TreeControl
https://bugs.documentfoundation.org/show_bug.cgi?id=151903 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82380] Wrong "Reached the end of the document" text with 'Find Next' and 'Find Previous'
https://bugs.documentfoundation.org/show_bug.cgi?id=82380 --- Comment #12 from QA Administrators --- Dear Prathapmuruganandam, 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 150186] Version 7.3.5 - Crashing on New Document
https://bugs.documentfoundation.org/show_bug.cgi?id=150186 --- Comment #7 from QA Administrators --- Dear Gene, 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 95953] Size of text not preserved and Liberation changed to Arial through save and open as pptx
https://bugs.documentfoundation.org/show_bug.cgi?id=95953 --- Comment #15 from QA Administrators --- Dear sam tygier, 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 147598] Continuous crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=147598 --- Comment #12 from QA Administrators --- Dear DErik, 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 95433] EDITING autocorrect option "Apply styles" causes Default Style paragraphs to change to "Text Body" paragraph style while typing
https://bugs.documentfoundation.org/show_bug.cgi?id=95433 --- Comment #13 from QA Administrators --- Dear Jeppe Bundsgaard, 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 93681] FILEOPEN: PPTX Import reverse order of columns in a right-to-left table
https://bugs.documentfoundation.org/show_bug.cgi?id=93681 --- Comment #9 from QA Administrators --- Dear Ofir, 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 77746] Missing list indentation in a pptx
https://bugs.documentfoundation.org/show_bug.cgi?id=77746 --- Comment #12 from QA Administrators --- Dear Ofir, 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 72567] FILEOPEN: Impress does not import text gradient from .PPTX
https://bugs.documentfoundation.org/show_bug.cgi?id=72567 --- Comment #18 from QA Administrators --- Dear Marcos Souza, 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 67348] FILEOPEN PPTX Fly In Animations Not Correctly Rendered for Chart Objects
https://bugs.documentfoundation.org/show_bug.cgi?id=67348 --- Comment #11 from QA Administrators --- Dear Luke, 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 59036] EDITING AutoCorrect: "Remove blank paragraphs" will work for all styles, other "[M]" options only for Default
https://bugs.documentfoundation.org/show_bug.cgi?id=59036 --- Comment #10 from QA Administrators --- Dear Mirosław Zalewski, 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 49920] FILEOPEN PPTX Colors of gradient are wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=49920 --- Comment #13 from QA Administrators --- Dear erwin.vandevelde, 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 49246] FILEOPEN: particular .pptx with missing (2D) WordArt Text Effects (Glow)
https://bugs.documentfoundation.org/show_bug.cgi?id=49246 --- Comment #13 from QA Administrators --- Dear sasha.libreoffice, 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 41253] FILEOPEN PPTX Shadows for characters missing
https://bugs.documentfoundation.org/show_bug.cgi?id=41253 --- Comment #11 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41180] VIEWING: Wordart 3D and color effect missing when FILEOPEN particular pptx
https://bugs.documentfoundation.org/show_bug.cgi?id=41180 --- Comment #11 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38481] Envelope layout wrong for centered lengthwise (OKI printers)
https://bugs.documentfoundation.org/show_bug.cgi?id=38481 --- Comment #31 from QA Administrators --- Dear Dan Essin, 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 36229] FORMATTING: PPTX import doesn't preserve text effects
https://bugs.documentfoundation.org/show_bug.cgi?id=36229 --- Comment #15 from QA Administrators --- Dear Georgy Angelov, 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 139620] Applying color fill to textbox from toolbar not working
https://bugs.documentfoundation.org/show_bug.cgi?id=139620 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139231] Lots of interacting between images position when moving images around (because of anchor)
https://bugs.documentfoundation.org/show_bug.cgi?id=139231 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137260] FILESAVE: Graphics wildly enlarged or gone after PPT/PPTX roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=137260 --- Comment #4 from QA Administrators --- Dear Lars Jødal, 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 136824] AutoCorrect > Apply does not work in bulleted or numbered lists.
https://bugs.documentfoundation.org/show_bug.cgi?id=136824 --- Comment #3 from QA Administrators --- Dear lomacar, 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 135320] FILEOPEN PPTX: effect similar to soft edges ("inward soft edges") not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=135320 --- Comment #10 from QA Administrators --- Dear Gerald Pfeifer, 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 132895] FILEOPEN PPTX: Font size too small for autoresize textbox with empty paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=132895 --- Comment #7 from QA Administrators --- Dear Alvaro Segura, 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 129059] FILEOPEN PPTX: equation is incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=129059 --- Comment #5 from QA Administrators --- Dear Ofir, 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 127554] FILESAVE: "Rotate all text 90°" of shape is wrong on PPTX export
https://bugs.documentfoundation.org/show_bug.cgi?id=127554 --- Comment #4 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127739] FILESAVE PPTX: Slides with 'black' theme lack text in PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=127739 --- Comment #6 from QA Administrators --- Dear Christian, 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 127437] FILEOPEN PPTX Rotated text in shape is imported wrongly
https://bugs.documentfoundation.org/show_bug.cgi?id=127437 --- Comment #5 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125897] MS PowerPoint bitmap filled shape display problem when shape is rotated
https://bugs.documentfoundation.org/show_bug.cgi?id=125897 --- Comment #4 from QA Administrators --- Dear nd101, 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 124230] FILESAVE PPTX: Custom Animations Sound Lost on Roundtrip
https://bugs.documentfoundation.org/show_bug.cgi?id=124230 --- Comment #5 from QA Administrators --- Dear Luke, 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 123511] SLIDESHOW PPTX Animation does not start automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=123511 --- Comment #14 from QA Administrators --- Dear seven, 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 122697] Clear Direct Formatting removes Conditional Formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=122697 --- Comment #9 from QA Administrators --- Dear russell, 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 122470] FILEOPEN XLSX, Column and line labels in pivot table changes when opened in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=122470 --- Comment #7 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 121086] The first page in print preview shifts to the left when exporting to PDF (visual glitch) (gen)
https://bugs.documentfoundation.org/show_bug.cgi?id=121086 --- Comment #10 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121060] LibreOffice gets unresponsive (does not respond) under certain circumstances
https://bugs.documentfoundation.org/show_bug.cgi?id=121060 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120690] FILEOPEN PPTX: Custom Audio playback timing settings not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=120690 --- Comment #4 from QA Administrators --- Dear Luke, 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 120427] Fileopen DOCX: Microsoft Equation 3.0 wrong from LO 5.0
https://bugs.documentfoundation.org/show_bug.cgi?id=120427 --- Comment #6 from QA Administrators --- Dear Timur, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117945] Videoclip flickering during full screen presentation (GTK3)
https://bugs.documentfoundation.org/show_bug.cgi?id=117945 --- Comment #28 from QA Administrators --- Dear Luca Della Santina, 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 116749] Font size and font of Formula object are not kept when displaying the OLE object in Microsoft Word or Powerpoint, OOXML and ODF formated documents
https://bugs.documentfoundation.org/show_bug.cgi?id=116749 --- Comment #10 from QA Administrators --- Dear Shimi Chen, 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 114430] Importing master slides broken
https://bugs.documentfoundation.org/show_bug.cgi?id=114430 --- Comment #5 from QA Administrators --- Dear Martin Sourada, 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 115164] Calc freezes when trying to update Links without connectivity
https://bugs.documentfoundation.org/show_bug.cgi?id=115164 --- Comment #4 from QA Administrators --- Dear Dan Dascalescu, 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 113819] FILEOPEN PPTX Shape does not return to its original rotation after Wave animation
https://bugs.documentfoundation.org/show_bug.cgi?id=113819 --- Comment #6 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113006] FILEOPEN PPTX Table opens with Liberation font instead of Arial (OK if PPTX resaved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=113006 --- Comment #8 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107376] Displaying false preview when using pptx files.
https://bugs.documentfoundation.org/show_bug.cgi?id=107376 --- Comment #10 from QA Administrators --- Dear Philipp Petschner, 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 102200] [FILEOPEN, FORMATTING, PPTX] text boxes on some slides doubled so content seems blurred
https://bugs.documentfoundation.org/show_bug.cgi?id=102200 --- Comment #12 from QA Administrators --- Dear Chuck, 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 103476] FORMATTING: bad paragraph and line spacing in PPTX "Do not Autofit" textbox (related to autofit text)
https://bugs.documentfoundation.org/show_bug.cgi?id=103476 --- Comment #5 from QA Administrators --- Dear internationils, 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 108743] [META] Find toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108743 Bug 108743 depends on bug 146178, which changed state. Bug 146178 Summary: Allow navigate by field to advance from last field of document to the first field in the stack, and reverse https://bugs.documentfoundation.org/show_bug.cgi?id=146178 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 146178, which changed state. Bug 146178 Summary: Allow navigate by field to advance from last field of document to the first field in the stack, and reverse https://bugs.documentfoundation.org/show_bug.cgi?id=146178 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146178] Allow navigate by field to advance from last field of document to the first field in the stack, and reverse
https://bugs.documentfoundation.org/show_bug.cgi?id=146178 Jim Raykowski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146178] Allow navigate by field to advance from last field of document to the first field in the stack, and reverse
https://bugs.documentfoundation.org/show_bug.cgi?id=146178 --- Comment #5 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/60035ea9b46f10351ef0bd56d4999bc43558dd33 tdf#146178 Allow navigate by field to advance from last field It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146178] Allow navigate by field to advance from last field of document to the first field in the stack, and reverse
https://bugs.documentfoundation.org/show_bug.cgi?id=146178 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/uiwriter/uiwriter6.cxx | 32
sw/source/uibase/uiview/viewmdi.cxx | 28 +++-
2 files changed, 59 insertions(+), 1 deletion(-)
New commits:
commit 60035ea9b46f10351ef0bd56d4999bc43558dd33
Author: Jim Raykowski
AuthorDate: Wed Jan 18 08:54:02 2023 -0900
Commit: Jim Raykowski
CommitDate: Thu Jan 26 03:12:48 2023 +
tdf#146178 Allow navigate by field to advance from last field
of document to the first field in the stack, and reverse
Change-Id: Ie0ef1eee0c556644f0b87a65b4bde1a7d9cdf337
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145775
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/qa/extras/uiwriter/uiwriter6.cxx
b/sw/qa/extras/uiwriter/uiwriter6.cxx
index a3cda9eca08f..5585723cb482 100644
--- a/sw/qa/extras/uiwriter/uiwriter6.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter6.cxx
@@ -59,6 +59,8 @@
#include
#include
+#include
+
using namespace osl;
using namespace com::sun::star;
using namespace com::sun::star::beans;
@@ -2400,6 +2402,36 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf151828)
CPPUNIT_ASSERT_EQUAL(OUString("MyTableName"), pFormat->GetName());
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf146178)
+{
+createSwDoc();
+
+SwDoc* pDoc = getSwDoc();
+SwWrtShell* pWrtShell = pDoc->GetDocShell()->GetWrtShell();
+SwPaM* pCursor = pDoc->GetEditShell()->GetCursor();
+
+// insert two fields
+dispatchCommand(mxComponent, ".uno:InsertTimeField", {});
+dispatchCommand(mxComponent, ".uno:InsertDateField", {});
+
+// navigate by field
+SwView::SetMoveType(NID_FIELD);
+
+// set cursor to the start of the document
+pWrtShell->SttEndDoc(false);
+// navigate to the previous field
+dispatchCommand(mxComponent, ".uno:ScrollToPrevious", {});
+// Before the fix the position would be 0, navigation did not wrap to end
of document
+CPPUNIT_ASSERT_EQUAL(sal_Int32(1), pCursor->GetPoint()->GetContentIndex());
+
+// set cursor to the end of the document
+pWrtShell->SttEndDoc(false);
+// navigate to the next field
+dispatchCommand(mxComponent, ".uno:ScrollToNext", {});
+// Before the fix the position would be 1, navigation did not wrap to
start of document
+CPPUNIT_ASSERT_EQUAL(sal_Int32(0), pCursor->GetPoint()->GetContentIndex());
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/uibase/uiview/viewmdi.cxx
b/sw/source/uibase/uiview/viewmdi.cxx
index f2c9ad63034a..cb070b655efc 100644
--- a/sw/source/uibase/uiview/viewmdi.cxx
+++ b/sw/source/uibase/uiview/viewmdi.cxx
@@ -428,8 +428,34 @@ IMPL_LINK( SwView, MoveNavigationHdl, void*, p, void )
FN_PREV_BOOKMARK);
break;
case NID_FIELD:
+{
rSh.EnterStdMode();
-rSh.MoveFieldType(nullptr, bNext, SwFieldIds::Unknown);
+rSh.StartAction();
+SearchLabel eSearchLabel = SearchLabel::Empty;
+if (!rSh.MoveFieldType(nullptr, bNext, SwFieldIds::Unknown))
+{
+// no field found in the move direction
+// wrap and try again
+SwShellCursor* pCursor = rSh.GetCursor_();
+SwCursorSaveState aSaveState(*pCursor);
+rSh.SttEndDoc(bNext);
+// document might have a field at the start of the document
+SwField* pField = rSh.GetCurField();
+if ((bNext && pField && pField->GetTypeId() !=
SwFieldTypesEnum::Postit) ||
+rSh.MoveFieldType(nullptr, bNext, SwFieldIds::Unknown))
+{
+eSearchLabel = bNext ? SearchLabel::EndWrapped :
SearchLabel::StartWrapped;
+}
+else
+{
+// no visible fields found
+pCursor->RestoreSavePos();
+eSearchLabel = SearchLabel::NavElementNotFound;
+}
+}
+SvxSearchDialogWrapper::SetSearchLabel(eSearchLabel);
+rSh.EndAction();
+}
break;
case NID_FIELD_BYTYPE:
{
[Libreoffice-bugs] [Bug 95405] Sidebar deck for find/search and replace
https://bugs.documentfoundation.org/show_bug.cgi?id=95405 --- Comment #29 from Jim Raykowski --- (In reply to Heiko Tietze from comment #27) > b) What happens if a words occurs multiple time in a range? We could show > every single item (MSO does this) or summarize into one result (as shown in > the mockup). Having individual listings for all finds would be better for context menu actions like the hyperlinks to results enhancement Stuart has suggested. > c and d) The current quickfind function highlights all places until one > iterates over it via next/previous; MSO uses a different shading for the > currently active result, the mockup has a frame in highlight color / blue > around the find result. Perhaps like what has been done for enhancement bug 152029, find results could have an inverted overlay if in the visible display area when the mouse is placed over entries in the content list. Navigating to an entry could be made to not clear all find selections as opposed to how the find bar clears the selections when stepping through results. > a) The quickfind has the option to run a case sensitive search (and users > asked repeatedly for more options). If we decide to add this option/s to the > sidebar deck, it should remain simple. Could imagine a toggle button next to > the search field. Check buttons could be placed under the search term input box like the find and replace dialog has for 'match case' and 'whole words only options'. (In reply to V Stuart Foote from comment #28) > So, place it into an existing SB Deck, or should this be a new "Search" Deck > that would hold find related Content panels? Starting with a Content panel > showing result of "Quick find" Find Bar as in attachment 184862 [details] One deck that contains a quick find panel and find and replace panel seems like a good idea to me. Someday it might be possible for users to create custom decks with any panels they want to place in them ;-) > Regards layout on the content panel, would the "results" being shown be > "clipped" from the document (with full styling/formatting) --or should > result be more simple unformatted text runs for a cleaner UI? Personally, > I'd prefer no formatting. A checkbox for how to display results might work for this. > And could the hyperlinking to the results be available to manipulate (e.g. > turn a selected search result into a reference or a bookmark). If I'm following, this would be done through a context menu. Sounds like a nice enhancement. > But also what would a content panel holding elements for the full "Find and > Replace" dialog provide? Could the full dialog be eliminated? Or the Content > panel would just show results? The full find and replace dialog can be placed in the sidebar. Some ui changes could be done to make it more panel appropriate. The dialog version could be eliminated but it wouldn't be required to for the panel version to exist. > Likewise, would this new SB work--Deck and Content Panel(s)-- to also enter > and display find/search result for the HUD for the "Command search" (bug > 91874 and bug 151228) Nice! I didn't know about the command search HUD. Seems like it would be appropriate as a panel in a find deck. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 95405] Sidebar deck for find/search and replace
https://bugs.documentfoundation.org/show_bug.cgi?id=95405 --- Comment #29 from Jim Raykowski --- (In reply to Heiko Tietze from comment #27) > b) What happens if a words occurs multiple time in a range? We could show > every single item (MSO does this) or summarize into one result (as shown in > the mockup). Having individual listings for all finds would be better for context menu actions like the hyperlinks to results enhancement Stuart has suggested. > c and d) The current quickfind function highlights all places until one > iterates over it via next/previous; MSO uses a different shading for the > currently active result, the mockup has a frame in highlight color / blue > around the find result. Perhaps like what has been done for enhancement bug 152029, find results could have an inverted overlay if in the visible display area when the mouse is placed over entries in the content list. Navigating to an entry could be made to not clear all find selections as opposed to how the find bar clears the selections when stepping through results. > a) The quickfind has the option to run a case sensitive search (and users > asked repeatedly for more options). If we decide to add this option/s to the > sidebar deck, it should remain simple. Could imagine a toggle button next to > the search field. Check buttons could be placed under the search term input box like the find and replace dialog has for 'match case' and 'whole words only options'. (In reply to V Stuart Foote from comment #28) > So, place it into an existing SB Deck, or should this be a new "Search" Deck > that would hold find related Content panels? Starting with a Content panel > showing result of "Quick find" Find Bar as in attachment 184862 [details] One deck that contains a quick find panel and find and replace panel seems like a good idea to me. Someday it might be possible for users to create custom decks with any panels they want to place in them ;-) > Regards layout on the content panel, would the "results" being shown be > "clipped" from the document (with full styling/formatting) --or should > result be more simple unformatted text runs for a cleaner UI? Personally, > I'd prefer no formatting. A checkbox for how to display results might work for this. > And could the hyperlinking to the results be available to manipulate (e.g. > turn a selected search result into a reference or a bookmark). If I'm following, this would be done through a context menu. Sounds like a nice enhancement. > But also what would a content panel holding elements for the full "Find and > Replace" dialog provide? Could the full dialog be eliminated? Or the Content > panel would just show results? The full find and replace dialog can be placed in the sidebar. Some ui changes could be done to make it more panel appropriate. The dialog version could be eliminated but it wouldn't be required to for the panel version to exist. > Likewise, would this new SB work--Deck and Content Panel(s)-- to also enter > and display find/search result for the HUD for the "Command search" (bug > 91874 and bug 151228) Nice! I didn't know about the command search HUD. Seems like it would be appropriate as a panel in a find deck. -- You are receiving this mail because: You are on the CC list for the bug.
Re: Upgrading mdds and orcus coming soon
On 24.01.2023 23:30, Kohei Yoshida wrote: On 17.01.2023 16:55, Kohei Yoshida wrote: Hi there, I'll be working on upgrading the mdds and orcus libraries to versions 2.1.0 and 0.18.0 respectively. Not sure how long the process will take, but hopefully it will be finished with a week. Turns out one week was a bit too optimistic. It will take a little while longer. It's landed: https://cgit.freedesktop.org/libreoffice/core/commit/?id=516bc904e94971b61e4b13af632bf321b0a4a640 Kohei
[Libreoffice-commits] core.git: configure.ac cui/source download.lst external/liborcus external/mdds RepositoryExternal.mk sc/inc sc/qa sc/source svl/source
RepositoryExternal.mk |4
configure.ac|4
cui/source/dialogs/AdditionsDialog.cxx |2
download.lst|8
external/liborcus/ExternalPackage_liborcus.mk |8
external/liborcus/ExternalProject_liborcus.mk |4
external/liborcus/Library_orcus.mk | 21
external/liborcus/UnpackedTarball_liborcus.mk | 21
external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1 | 236 +++
external/liborcus/forcepoint-83.patch.1 | 38
external/liborcus/forcepoint-84.patch.1 | 38
external/liborcus/forcepoint-87.patch.1 | 27
external/liborcus/forcepoint-88.patch.1 | 42
external/liborcus/forcepoint-95.patch.1 | 11
external/liborcus/gcc9.patch.0 | 17
external/liborcus/inc/pch/precompiled_orcus-parser.hxx |8
external/liborcus/inc/pch/precompiled_orcus.hxx |9
external/liborcus/include.patch.0 | 20
external/liborcus/liborcus-no-benchmark.patch.1 |8
external/liborcus/overrun.patch.0 | 63
external/liborcus/std-get-busted.patch.1| 88 -
external/mdds/UnpackedTarball_mdds.mk |2
external/mdds/speedup-erase-2.patch | 18
external/mdds/speedup-erase-begin.patch | 140 -
sc/inc/mtvelements.hxx | 43
sc/qa/unit/helper/csv_handler.hxx | 27
sc/qa/unit/helper/qahelper.cxx |8
sc/source/core/tool/scmatrix.cxx| 13
sc/source/filter/html/htmlpars.cxx | 74
sc/source/filter/inc/orcusinterface.hxx | 431 +++--
sc/source/filter/orcus/filterdetect.cxx |3
sc/source/filter/orcus/interface.cxx| 893 +++-
sc/source/filter/orcus/xmlcontext.cxx | 37
sc/source/ui/dataprovider/csvdataprovider.cxx |8
sc/source/ui/docshell/datastream.cxx| 10
svl/source/misc/gridprinter.cxx |7
36 files changed, 1242 insertions(+), 1149 deletions(-)
New commits:
commit 516bc904e94971b61e4b13af632bf321b0a4a640
Author: Kohei Yoshida
AuthorDate: Tue Jan 17 17:10:07 2023 -0500
Commit: Kohei Yoshida
CommitDate: Thu Jan 26 02:27:57 2023 +
Upgrade mdds and orcus to 2.1.0 and 0.18.0, respectively
Change-Id: I288b5b54bd07d951bcc68afda7514bde730193dc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146107
Tested-by: Jenkins
Reviewed-by: Kohei Yoshida
diff --git a/RepositoryExternal.mk b/RepositoryExternal.mk
index 92ea4ba17670..0f7c77f443d6 100644
--- a/RepositoryExternal.mk
+++ b/RepositoryExternal.mk
@@ -3306,7 +3306,7 @@ $(call gb_LinkTarget_set_include,$(1),\
)
$(call gb_LinkTarget_add_libs,$(1),\
- -L$(call gb_UnpackedTarball_get_dir,liborcus)/src/liborcus/.libs
-lorcus-0.17 \
+ -L$(call gb_UnpackedTarball_get_dir,liborcus)/src/liborcus/.libs
-lorcus-0.18 \
)
$(if $(SYSTEM_BOOST), \
@@ -3325,7 +3325,7 @@ $(call gb_LinkTarget_set_include,$(1),\
)
$(call gb_LinkTarget_add_libs,$(1),\
- -L$(call gb_UnpackedTarball_get_dir,liborcus)/src/parser/.libs
-lorcus-parser-0.17 \
+ -L$(call gb_UnpackedTarball_get_dir,liborcus)/src/parser/.libs
-lorcus-parser-0.18 \
)
endef
diff --git a/configure.ac b/configure.ac
index 41518fdc533c..321cc06acbdb 100644
--- a/configure.ac
+++ b/configure.ac
@@ -10532,7 +10532,7 @@ dnl
===
dnl Check for system mdds
dnl ===
MDDS_CFLAGS_internal="-I${WORKDIR}/UnpackedTarball/mdds/include"
-libo_CHECK_SYSTEM_MODULE([mdds],[MDDS],[mdds-2.0 >= 2.0.0])
+libo_CHECK_SYSTEM_MODULE([mdds],[MDDS],[mdds-2.1 >= 2.1.0])
dnl ===
dnl Check for system dragonbox
@@ -10839,7 +10839,7 @@ AC_SUBST(DEFAULT_CRASHDUMP_VALUE)
dnl ===
dnl Orcus
dnl ===
-libo_CHECK_SYSTEM_MODULE([orcus],[ORCUS],[liborcus-0.17 >= 0.17.2])
+libo_CHECK_SYSTEM_MODULE([orcus],[ORCUS],[liborcus-0.18 >= 0.18.0])
if test "$with_system_orcus" != "yes"; then
if test "$SYSTEM_BOOST" = "TRUE"; then
dnl Link with Boost.System
diff --git a/cui/source/dialogs/AdditionsDialog.cxx
b/cui/source/dialogs/AdditionsDialog.cxx
index ffbe02a344e2..7c76f9c9872a
[Libreoffice-bugs] [Bug 150591] Calc Segmentation Fault Segfault Crash Coredump Upon Close After Changes
https://bugs.documentfoundation.org/show_bug.cgi?id=150591 nroycea+documentfoundat...@gmail.com changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #7 from nroycea+documentfoundat...@gmail.com --- Confirmed, works for me. Closing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133794] Memory used related to external data (CSV) not released after close of document
https://bugs.documentfoundation.org/show_bug.cgi?id=133794 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- Seems it works with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc441f3886330c4ae2abeb67c0758b935ba23f47 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152285] CLONE FORMATTING DOCX: Clone formatting of font is no longer applied after saving and reloading
https://bugs.documentfoundation.org/show_bug.cgi?id=152285 --- Comment #9 from supineb...@protonmail.com --- I guess you are right that bug 2 is not a bug, so we can just focus on bug 1 here. I didn't even realise the formatting layers/rules were complex, - because I never once changed the character or paragraph formatting, either in the drop down menu or the styles menu. I guess it must have happened when copying text from the web and pasting. Been using MS Word all my life before this year and never once experienced this problem. Need to work out what libreoffice is doing different so can avoid it in future. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152286] wrong text formatting with copy paste
https://bugs.documentfoundation.org/show_bug.cgi?id=152286 --- Comment #5 from supineb...@protonmail.com --- Yes, you seem to have found the problem with the different formatting. I totally missed this - because I never once changed the character or paragraph formatting, either in the drop down menu or the styles menu. I guess it must have happened when copying text from the web and pasting. Been using MS Word all my life before this year and never once experienced this problem. Need to work out what libreoffice is doing different so can avoid it in future. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Priority|medium |low Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Keywords||needsUXEval Severity|normal |minor --- Comment #8 from Stéphane Guillou (stragu) --- I can see how this unwanted scrolling is an annoyance. I don't know how possible it is to block that while dragging onto the canvas but allow it again once the user goes back towards the edges. Copying UX in for their opinion. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151090] [UI] The spreadsheet shifts when we drag'n'drop content from outside the window
https://bugs.documentfoundation.org/show_bug.cgi?id=151090 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Priority|medium |low Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Keywords||needsUXEval Severity|normal |minor --- Comment #8 from Stéphane Guillou (stragu) --- I can see how this unwanted scrolling is an annoyance. I don't know how possible it is to block that while dragging onto the canvas but allow it again once the user goes back towards the edges. Copying UX in for their opinion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153207 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153207 [Bug 153207] Calc horizontal ruler / scrollbar reversed in Right-to-Left mode (macOS) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153207 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153207 [Bug 153207] Calc horizontal ruler / scrollbar reversed in Right-to-Left mode (macOS) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153207] Calc horizontal ruler / scrollbar reversed in Right-to-Left mode (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=153207 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|x86 (IA32) |All Ever confirmed|0 |1 Summary|Ruller at Spreadsheet in|Calc horizontal ruler / |Right to Left mode |scrollbar reversed in ||Right-to-Left mode (macOS) Blocks||129661, 42082 Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Thank you Ihsan! Not reproduced on Ubuntu 20.04: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e125e6623fa1c0f39d927bb37547ca6d1e299cb1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But reproduced in: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 2; OS: Mac OS X 12.6.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Dragging the scrollbar thumb makes it go in the opposite way. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=42082 [Bug 42082] [META] Make LibreOffice shine and glow on macOS https://bugs.documentfoundation.org/show_bug.cgi?id=129661 [Bug 129661] [META] Right-To-Left (RTL) user interface issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153206] Calc sort order wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=153206 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Blocks||108386 --- Comment #5 from Stéphane Guillou (stragu) --- I agree this could be better documented. We've got: - https://help.libreoffice.org/latest/en-US/text/scalc/01/12030100.html - https://help.libreoffice.org/latest/en-US/text/scalc/01/12030200.html There's mention that "Number fields are sorted by size and text fields by the order of the characters", but it doesn't clarify what comes first, and also that the alphabetical part starts with numbers. Hendrik, the example you provide gives me a result that makes sense: 215468 499432 6545146 306518/8 v123245 - First, numbers from lowest to highest (three first rows) - Then, text strings, alphabetically, with numbers first (two last rows) What might be more surprising to users is the inclusion of dates and times in the column. The logic should also be explained in the documentation. Should we change this into a documentation improvement? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108386 [Bug 108386] [META] Calc sorting related bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108386] [META] Calc sorting related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108386 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153206 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153206 [Bug 153206] Calc sort order wrong -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153188] suggestion: AutoSave on lose focus; see additional more sophisticated suggestion in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=153188 m.a.riosv changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #4 from m.a.riosv --- Maybe because LibreOffice it's not closed properly with files opened, and perhaps some change force recovery. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153204] Draw: cannot create layer named "background"
https://bugs.documentfoundation.org/show_bug.cgi?id=153204 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- The following five names have an internal usage and cannot be set by the user: layout, background, backgroundobjects, controls, measurelines The naming on the tabs is different and depends on language. The internal name is visible in the Modify dialog. 'layout', 'controls', 'measurelines' layers are visible in normal view. 'backgroundobjects' layer is visible in master view. 'background' layer is never visible and is not intended to be directly used by the user. 'measureline' layer is special as a dimension-line shape is automatically placed on layer 'measureline'. 'controls' layer is special as a form control shape is automatically placed on 'controls' layer and objects on 'controls' layer are always rendered in front of objects on other layers. -- You are receiving this mail because: You are the assignee for the bug.
