[Libreoffice-bugs] [Bug 153469] LibreOffice Impress user interface will stop responding when opening a presentation slide containing a video clip.
https://bugs.documentfoundation.org/show_bug.cgi?id=153469 --- Comment #2 from Oliver Grimm --- ah, didn't see the "additional info" with regards to wayland. Sorry, please just ignore my comment above ... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153469] LibreOffice Impress user interface will stop responding when opening a presentation slide containing a video clip.
https://bugs.documentfoundation.org/show_bug.cgi?id=153469 --- Comment #1 from Oliver Grimm --- Works fine here with no problems (Debian testing, LO 7.5.1.1, X11, tested on both Gnome and KDE). Can someone else check for wayland, please? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59284] [META] Cell border related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=59284 Heiko Tietze changed: What|Removed |Added Depends on||153782 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153782 [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands
https://bugs.documentfoundation.org/show_bug.cgi?id=153782 Heiko Tietze changed: What|Removed |Added Blocks||59284 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=48 ||622 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=59284 [Bug 59284] [META] Cell border related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands
https://bugs.documentfoundation.org/show_bug.cgi?id=153782 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #4 from Heiko Tietze --- Rafael, up to you. Either remove the tick one (my take) or keep both and rename as suggested. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands
https://bugs.documentfoundation.org/show_bug.cgi?id=153782 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #4 from Heiko Tietze --- Rafael, up to you. Either remove the tick one (my take) or keep both and rename as suggested. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sw/qa writerfilter/source
sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx |binary
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx |7 ++
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 11
++
3 files changed, 14 insertions(+), 4 deletions(-)
New commits:
commit bf9e8ce3a810e2989fb0b486b3398d523f69da97
Author: Justin Luth
AuthorDate: Wed Feb 22 11:19:40 2023 -0500
Commit: Miklos Vajna
CommitDate: Thu Feb 23 07:35:15 2023 +
tdf#153526 writerfilter: catch exception from no NumberingRules
This fixes a LO 7.5 regression (well, exposed some other flaws) from
commit cf02b94bc513ee1b742b4c5d7174632b568e8b72.
I first tried testing if hasPropertyByName,
but that returns true(), even though this is an editeng component.
Well, ignoring the fundamental issues at play here
(and there are many - like having a comment
take over m_xPreviousParagraph)
the issue is easily solved with a try/catch
instead of a redundant if clause.
Change-Id: I4f27fce3e2984235df19dc3ed4be558891b28a90
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147486
Tested-by: Jenkins
Reviewed-by: Justin Luth
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147494
Reviewed-by: Miklos Vajna
diff --git a/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx
b/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx
new file mode 100644
index ..f26240092c10
Binary files /dev/null and
b/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
index be8e5cf663bd..ce1aec0fa07f 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
@@ -80,6 +80,13 @@ DECLARE_OOXMLEXPORT_TEST(testTdf147646,
"tdf147646_mergedCellNumbering.docx")
CPPUNIT_ASSERT_EQUAL(OUString("2."),parseDump("/root/page/body/tab/row[4]/cell/txt/SwParaPortion/SwLineLayout/child::*[@type='PortionType::Number']","expand"));
}
+DECLARE_OOXMLEXPORT_TEST(testTdf153526_commentInNumbering,
"tdf153526_commentInNumbering.docx")
+{
+// an exception was prematurely ending finishParagraph, losing numbering
and CRs
+// so before the patch, this was 6.
+CPPUNIT_ASSERT_EQUAL(13, getParagraphs());
+}
+
CPPUNIT_TEST_FIXTURE(Test, testTdf149551_mongolianVert)
{
// Given a docx document with a shape with vert="mongolianVert".
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index 16ce9c9b5f96..592897313bc7 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++ b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
@@ -2309,11 +2309,14 @@ void DomainMapper_Impl::finishParagraph( const
PropertyMapPtr& pPropertyMap, con
uno::Reference
xCurrentNumberingRules(itNumberingRules->Value, uno::UNO_QUERY);
if (xCurrentNumberingRules.is())
aCurrentNumberingName =
xCurrentNumberingRules->getName();
-if (m_xPreviousParagraph.is())
+try
+{
+uno::Reference
xPreviousNumberingRules(m_xPreviousParagraph->getPropertyValue("NumberingRules"),
uno::UNO_QUERY_THROW);
+aPreviousNumberingName =
xPreviousNumberingRules->getName();
+}
+catch (const uno::Exception&)
{
-uno::Reference
xPreviousNumberingRules(m_xPreviousParagraph->getPropertyValue("NumberingRules"),
uno::UNO_QUERY);
-if (xPreviousNumberingRules.is())
-aPreviousNumberingName =
xPreviousNumberingRules->getName();
+TOOLS_WARN_EXCEPTION("writerfilter",
"DomainMapper_Impl::finishParagraph NumberingRules");
}
}
else if (
m_xPreviousParagraph->getPropertySetInfo()->hasPropertyByName("NumberingStyleName")
&&
[Libreoffice-bugs] [Bug 153786] paste as unformatted text -- doesn't work as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=153786 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- This is completely incorrect interpretation. Pasting as unformatted text is *expected* to not bring formatting present in the available rich clipboard formats to the target documents. It has nothing to do with the further processing of the pasted text content in the target document; e.g., with the metadata (anonymous annotations) added to the document content added in different editing session, used to provide useful version comparison results [1, 2, 3]. The RSID generation can be disabled; and also there is bug 88298 addressing some of your concerns. Everything else in your description is just unrelated and incoherent rant on something that you don't seem to understand. The software is for users, not for IT pros; the complexity of the markup is the result of the WYSIWYG software using fixed algorithms to compose and store vast amount of information *potentially* useful in great variety of use cases, without an intelligence that an IT expert could apply when generating the markup manually. [1] https://git.libreoffice.org/core/+/062eaeffe7cb986255063bb9b0a5f3fb3fc8e34c [2] https://wiki.documentfoundation.org/ReleaseNotes/5.0#Optional_RSIDs [3] https://help.libreoffice.org/7.5/en-US/text/shared/optionen/01040800.html?DbPAR=SHARED#hd_id521597320824763 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands
https://bugs.documentfoundation.org/show_bug.cgi?id=153782 --- Comment #3 from Samuel Mehrbrodt (allotropia) --- (In reply to Heiko Tietze from comment #2) > CellLineStylePopup::Initialize() uses STR_BORDER_DOUBLE_1 twice [1]. Any > reason, Samuel? > > You added this for bug 48622 with > https://gerrit.libreoffice.org/c/core/+/124680 > > [1] > https://opengrok.libreoffice.org/xref/core/sc/source/ui/sidebar/ > CellLineStyleControl.cxx?r=cd116a1b#70 I think this was a mistake. Probably one of them can go. Maybe check which makes more sense (also in terms of interoperability) and remove the other one. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153782] Line width name "Double hairline" is duplicated for two different format commands
https://bugs.documentfoundation.org/show_bug.cgi?id=153782 --- Comment #3 from Samuel Mehrbrodt (allotropia) --- (In reply to Heiko Tietze from comment #2) > CellLineStylePopup::Initialize() uses STR_BORDER_DOUBLE_1 twice [1]. Any > reason, Samuel? > > You added this for bug 48622 with > https://gerrit.libreoffice.org/c/core/+/124680 > > [1] > https://opengrok.libreoffice.org/xref/core/sc/source/ui/sidebar/ > CellLineStyleControl.cxx?r=cd116a1b#70 I think this was a mistake. Probably one of them can go. Maybe check which makes more sense (also in terms of interoperability) and remove the other one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153784] Inputwin of Formula bar changing height
https://bugs.documentfoundation.org/show_bug.cgi?id=153784 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 CC||caol...@redhat.com, ||szymon.k...@collabora.com, ||thorsten.wagne...@gmail.com Resolution|NOTABUG |--- Status|RESOLVED|NEW --- Comment #5 from Heiko Tietze --- No issue with qt5 but on resizing it maximizes this part and I'm never able to make it smaller again (unless to collapse). Gen and gtk3 work more or less acceptable but seem to be cut off. I suspect the input to be maximized like for qt/gen but covered. Besides fixing the bugs we need some splitter to indicate the sizing capability. Szymon and Caolan worked recently on the formula bar, and Thorsten before. Any idea? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153784] Inputwin of Formula bar changing height
https://bugs.documentfoundation.org/show_bug.cgi?id=153784 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 CC||caol...@redhat.com, ||szymon.k...@collabora.com, ||thorsten.wagne...@gmail.com Resolution|NOTABUG |--- Status|RESOLVED|NEW --- Comment #5 from Heiko Tietze --- No issue with qt5 but on resizing it maximizes this part and I'm never able to make it smaller again (unless to collapse). Gen and gtk3 work more or less acceptable but seem to be cut off. I suspect the input to be maximized like for qt/gen but covered. Besides fixing the bugs we need some splitter to indicate the sizing capability. Szymon and Caolan worked recently on the formula bar, and Thorsten before. Any idea? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #8 from Heiko Tietze --- (In reply to sdc.blanco from comment #6) > what list are you looking for? A complete list of items and it abbreviations. The question is whether we change the abbreviation of some items and we should know if that crashes with other. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #8 from Heiko Tietze --- (In reply to sdc.blanco from comment #6) > what list are you looking for? A complete list of items and it abbreviations. The question is whether we change the abbreviation of some items and we should know if that crashes with other. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: sw/inc sw/source
sw/inc/strings.hrc |1 +
sw/inc/swundo.hxx |1 +
sw/source/core/undo/undobj.cxx |3 +++
sw/source/uibase/shells/textfld.cxx |4 ++--
4 files changed, 7 insertions(+), 2 deletions(-)
New commits:
commit 7897143a7313c57aed262826b736619bf9432b48
Author: Miklos Vajna
AuthorDate: Wed Feb 22 19:47:22 2023 +0100
Commit: Miklos Vajna
CommitDate: Thu Feb 23 07:09:57 2023 +
sw: fix undo comment of FN_DELETE_TEXT_FORMFIELDS
It's deletes, not an insert. One has to dispatch
.uno:DeleteTextFormFields to see this in action.
Change-Id: I7c5afa6acc633e0d0a750d97ff6477b9511e816c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147489
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index ec0903f48560..40cbb9acb8c4 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -590,6 +590,7 @@
#define STR_UNDO_INSERT_FORM_FIELD
NC_("STR_UNDO_INSERT_FORM_FIELD", "Insert form field")
#define STR_UNDO_UPDATE_FORM_FIELD
NC_("STR_UNDO_UPDATE_FORM_FIELD", "Update form field")
#define STR_UNDO_UPDATE_FORM_FIELDS
NC_("STR_UNDO_UPDATE_FORM_FIELDS", "Update form fields")
+#define STR_UNDO_DELETE_FORM_FIELDS
NC_("STR_UNDO_DELETE_FORM_FIELDS", "Delete form fields")
#define STR_UNDO_INSERT_PAGE_NUMBER
NC_("STR_UNDO_INSERT_PAGE_NUMBER", "Insert page number")
#define STR_DROP_DOWN_FIELD_ITEM_LIMIT
NC_("STR_DROP_DOWN_FIELD_ITEM_LIMIT", "You can specify maximum of 25 items for
a drop-down form field.")
diff --git a/sw/inc/swundo.hxx b/sw/inc/swundo.hxx
index a387757bfd6b..61261fb9769b 100644
--- a/sw/inc/swundo.hxx
+++ b/sw/inc/swundo.hxx
@@ -169,6 +169,7 @@ enum class SwUndoId
INSERT_PAGE_NUMBER,// 137
UPDATE_FORM_FIELD, // 138
UPDATE_FORM_FIELDS,// 139
+DELETE_FORM_FIELDS,// 140
};
OUString GetUndoComment(SwUndoId eId);
diff --git a/sw/source/core/undo/undobj.cxx b/sw/source/core/undo/undobj.cxx
index 8a23ae1f03ff..3c5f3844591e 100644
--- a/sw/source/core/undo/undobj.cxx
+++ b/sw/source/core/undo/undobj.cxx
@@ -652,6 +652,9 @@ OUString GetUndoComment(SwUndoId eId)
case SwUndoId::UPDATE_FORM_FIELDS:
pId = STR_UNDO_UPDATE_FORM_FIELDS;
break;
+case SwUndoId::DELETE_FORM_FIELDS:
+pId = STR_UNDO_DELETE_FORM_FIELDS;
+break;
}
assert(pId);
diff --git a/sw/source/uibase/shells/textfld.cxx
b/sw/source/uibase/shells/textfld.cxx
index 785b2d95d6c9..e94b230a8f9d 100644
--- a/sw/source/uibase/shells/textfld.cxx
+++ b/sw/source/uibase/shells/textfld.cxx
@@ -982,7 +982,7 @@ FIELD_INSERT:
{
aFieldCommandPrefix = pFieldCommandPrefix->GetValue();
}
-
rSh.GetDoc()->GetIDocumentUndoRedo().StartUndo(SwUndoId::INSERT_FORM_FIELD,
nullptr);
+
rSh.GetDoc()->GetIDocumentUndoRedo().StartUndo(SwUndoId::DELETE_FORM_FIELDS,
nullptr);
rSh.StartAction();
IDocumentMarkAccess* pMarkAccess =
rSh.GetDoc()->getIDocumentMarkAccess();
@@ -1021,7 +1021,7 @@ FIELD_INSERT:
}
rSh.EndAction();
-
rSh.GetDoc()->GetIDocumentUndoRedo().EndUndo(SwUndoId::INSERT_FORM_FIELD,
nullptr);
+
rSh.GetDoc()->GetIDocumentUndoRedo().EndUndo(SwUndoId::DELETE_FORM_FIELDS,
nullptr);
}
break;
case FN_PGNUMBER_WIZARD:
[Libreoffice-bugs] [Bug 65138] [META] Sidebar feature related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=65138 Bug 65138 depends on bug 151745, which changed state. Bug 151745 Summary: Resizing window with Meta+left/right arrow puts Sidebar into glitchy state in Calc https://bugs.documentfoundation.org/show_bug.cgi?id=151745 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source
sc/source/ui/app/inputwin.cxx |1 -
1 file changed, 1 deletion(-)
New commits:
commit 228caa2bafe214a0b502db4ac288dd70169ac2b8
Author: Samuel Mehrbrodt
AuthorDate: Mon Feb 20 23:58:55 2023 +0100
Commit: Samuel Mehrbrodt
CommitDate: Thu Feb 23 07:06:59 2023 +
tdf#151745 Fix input line redraw issue after resizing calc window
Change-Id: Ia8a7e1ab6b68f10f19733d8ce7f36d9ea02d4785
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147352
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
diff --git a/sc/source/ui/app/inputwin.cxx b/sc/source/ui/app/inputwin.cxx
index f833e743b991..6e9b75338751 100644
--- a/sc/source/ui/app/inputwin.cxx
+++ b/sc/source/ui/app/inputwin.cxx
@@ -937,7 +937,6 @@ void ScInputBarGroup::Resize()
{
mxTextWndGroup->SetScrollPolicy();
InterimItemWindow::Resize();
-TriggerToolboxLayout();
}
void ScInputBarGroup::StopEditEngine(bool bAll)
[Libreoffice-commits] core.git: 2 commits - basic/qa chart2/qa chart2/source compilerplugins/clang sccomp/qa sc/qa svl/qa test/source vcl/qa writerperfect/qa
basic/qa/cppunit/test_global_array.cxx |4 +-
basic/qa/cppunit/test_global_as_new.cxx |4 +-
chart2/qa/extras/chart2export2.cxx |4 +-
chart2/qa/extras/chart2import2.cxx |8 ++---
chart2/source/controller/sidebar/ChartAreaPanel.cxx |3 +-
compilerplugins/clang/cppunitassertequals.cxx | 15 ++
compilerplugins/clang/test/cppunitassertequals.cxx | 11 +++
sc/qa/unit/subsequent_export_test.cxx |4 +-
sc/qa/unit/subsequent_filters_test.cxx |4 +-
sc/qa/unit/ucalc.cxx| 28 ++--
sc/qa/unit/ucalc_copypaste.cxx | 14 +-
sc/qa/unit/ucalc_sort.cxx | 20 +++---
sccomp/qa/unit/solver.cxx |2 -
svl/qa/unit/svl.cxx | 20 +++---
test/source/table/xtablerows.cxx|4 +-
vcl/qa/cppunit/outdev.cxx | 20 +++---
writerperfect/qa/unit/WPXSvStreamTest.cxx |2 -
17 files changed, 95 insertions(+), 72 deletions(-)
New commits:
commit a2732de4bd080e3ed8894ba3618f48bc4c6d9abe
Author: Samuel Mehrbrodt
AuthorDate: Mon Feb 20 22:20:59 2023 +0100
Commit: Samuel Mehrbrodt
CommitDate: Thu Feb 23 07:04:15 2023 +
tdf#153640 Fix changing chart background color back to None
Change-Id: I653028d6016ca0caa72cb2a877cd23592c322a18
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147351
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
diff --git a/chart2/source/controller/sidebar/ChartAreaPanel.cxx
b/chart2/source/controller/sidebar/ChartAreaPanel.cxx
index 71e978e14543..b8bd8198b9bc 100644
--- a/chart2/source/controller/sidebar/ChartAreaPanel.cxx
+++ b/chart2/source/controller/sidebar/ChartAreaPanel.cxx
@@ -408,9 +408,10 @@ void ChartAreaPanel::setFillStyleAndBitmap(const
XFillStyleItem* pStyleItem,
xPropSet->setPropertyValue("FillBitmapName", aBitmap);
}
-void ChartAreaPanel::setFillUseBackground(const XFillStyleItem* /*pStyleItem*/,
+void ChartAreaPanel::setFillUseBackground(const XFillStyleItem* pStyleItem,
const XFillUseSlideBackgroundItem&
/*rItem*/)
{
+setFillStyle(*pStyleItem);
}
void ChartAreaPanel::updateData()
commit dc96de7c62e1e6f37ec485f3f0f564a00f3d01f4
Author: Stephan Bergmann
AuthorDate: Wed Feb 22 21:28:52 2023 +0100
Commit: Stephan Bergmann
CommitDate: Thu Feb 23 07:04:09 2023 +
Extend loplugin:cppunitassertequals to more argument types
Change-Id: Ic2990ebc2e4a9a36dcd3f90c5f634ca7dd225d52
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147491
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/basic/qa/cppunit/test_global_array.cxx
b/basic/qa/cppunit/test_global_array.cxx
index 5317e8701858..d2dafcfbda00 100644
--- a/basic/qa/cppunit/test_global_array.cxx
+++ b/basic/qa/cppunit/test_global_array.cxx
@@ -51,8 +51,8 @@ End Function
)BAS");
CPPUNIT_ASSERT(mod->Compile());
-CPPUNIT_ASSERT_EQUAL(StarBASIC::GetErrBasic(), ERRCODE_NONE);
-CPPUNIT_ASSERT_EQUAL(SbxBase::GetError(), ERRCODE_NONE);
+CPPUNIT_ASSERT_EQUAL(ERRCODE_NONE, StarBASIC::GetErrBasic());
+CPPUNIT_ASSERT_EQUAL(ERRCODE_NONE, SbxBase::GetError());
CPPUNIT_ASSERT(mod->IsCompiled());
return mod;
}
diff --git a/basic/qa/cppunit/test_global_as_new.cxx
b/basic/qa/cppunit/test_global_as_new.cxx
index ea5b6fcc527c..868f62d3ec15 100644
--- a/basic/qa/cppunit/test_global_as_new.cxx
+++ b/basic/qa/cppunit/test_global_as_new.cxx
@@ -45,8 +45,8 @@ End Function
)BAS");
CPPUNIT_ASSERT(mod->Compile());
-CPPUNIT_ASSERT_EQUAL(StarBASIC::GetErrBasic(), ERRCODE_NONE);
-CPPUNIT_ASSERT_EQUAL(SbxBase::GetError(), ERRCODE_NONE);
+CPPUNIT_ASSERT_EQUAL(ERRCODE_NONE, StarBASIC::GetErrBasic());
+CPPUNIT_ASSERT_EQUAL(ERRCODE_NONE, SbxBase::GetError());
CPPUNIT_ASSERT(mod->IsCompiled());
return mod;
}
diff --git a/chart2/qa/extras/chart2export2.cxx
b/chart2/qa/extras/chart2export2.cxx
index 4a95f40ab515..f56a0782feca 100644
--- a/chart2/qa/extras/chart2export2.cxx
+++ b/chart2/qa/extras/chart2export2.cxx
@@ -569,8 +569,8 @@ void Chart2ExportTest2::testCustomPositionofDataLabel()
chart2::RelativePosition aCustomLabelPosition;
CPPUNIT_ASSERT(xPropertySet->getPropertyValue("CustomLabelPosition")
>>= aCustomLabelPosition);
-CPPUNIT_ASSERT_DOUBLES_EQUAL(aCustomLabelPosition.Primary,
-0.0961935120945059, 1e-5);
-CPPUNIT_ASSERT_DOUBLES_EQUAL(aCustomLabelPosition.Secondary,
0.209578842093566, 1e-5);
+CPPUNIT_ASSERT_DOUBLES_EQUAL(-0.0961935120945059,
aCustomLabelPosition.Primary, 1e-5);
+
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153458 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153458 [Bug 153458] Connecting to database: wrong cursor position for dropping data to Calc sheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153458] Connecting to database: wrong cursor position for dropping data to Calc sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153458 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||102495 Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org Keywords||bibisectRequest --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced with: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same with kf5 (cairo+wayland). But not with gtk3 VCL. Not reproduced in: Version: 7.4.5.1 / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153786] New: paste as unformatted text -- doesn't work as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=153786 Bug ID: 153786 Summary: paste as unformatted text -- doesn't work as expected Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@cspv.hu Description: first off, it works... the problem is "ONLY" that it doesn't actually does what it suggests it's doing... As we might all know, a Writer document is actually a zip file, which among other components, has a "content.xml" -- well this is our document... this is its "source code"... this "code" (text with info and tags) is very messy... which is a bad thing... this means that the Microsoft's approach is still inherent in Libreoffice, that is, what matters is what you eventually see on your screen and in your prints... But how we achieve this look, this surface, should remain our dirty little secret... (the developers'), while the user is being happy with her/his document... that s/he "created) (only did the typing, it is us who created it! :)) I believe in transparency which HTML5 represents. More importantly, I believe that we all believe in it ... ODT docs and the machinery behind should be transparent in that sense... the text's source code should be clean... (I know, I know: a document's text can come from very surreal places, and from a series of various places, different machines, languages settings, vintages, templates, etc, etc) But cleanness should be a priority... Why? Because, for example, messiness simply causes Scribus (a program, application which deserves respect in terms of compatibility and common workflow, too) to import text jammed up... "jamming" only means only that here and there a space is missing... but when you've been editing a book for weeks, and the text is finished, it is a surreal situation that you "may have" some minor faults in your originally almost perfect text document... after importing it... SO, I think, there should be applicable methods for cleaning the messy source code.. and one such method could be "paste as unformatted text"... Imagine that you paste 10 pages like that, and then you have to format everything from scratch.. It'd be cool! But... headings and emphases could be kept.. and that would be even more superb... Unfortunately, "paste as unformatted text" only means "unformatted for the appearance"... cause the messy source code is just being pasted over... later perhaps, similar to "clear all direct formatting", there could be a tool "clear all formatting" BTW: despite using styles, the source code really looks (in some cases) like directly formatted... sometimes a space or a letter of a word separately gets a new tag... which is mess... and style names proliferate wildly... like, ranging from "text style name: T2" ... to... "T18". within one paragraph... which could be called mess... the main problem is that once a letter is separated from a word, it will remain like that... and the source code will get more and more fragmented by course of time this is why a method of cleaning, or even more methods could be a wonderful thing... acting against the messy and messier tendency ... Steps to Reproduce: 1. copy some paragraph from a text... 2. paste it in a new document... 3. open the source code file (context.xml) Actual Results: what you see is that broken up words remained as they were in the original (messed up) source file... Expected Results: you should see that pasted unformatted text's source code is CLEAN... only 2 tags, one at the beginning, one at the end... broken up words, lonely spaces embraced by tags should all be united in just one line of text... Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 2; OS: Linux 5.4; 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-bugs] [Bug 152033] Memory leakage when using Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152033 --- Comment #4 from Robert Großkopf --- Tested the attached document with OpenSUSE 15.3 64bit rpm Linux. Couldn't reproduce growing of used memory. Is contant 2,8 GB (of 16 GB max.) Tested with LO 7.3.6.2 and also LO 7.5.1.1 Might be it is a special Windows bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/app/salvtables.cxx |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
New commits:
commit 6d404f9ccad3ac6a7ffb83876ae7a656bc2d4547
Author: Noel Grandin
AuthorDate: Sun Feb 5 11:29:27 2023 +0100
Commit: Noel Grandin
CommitDate: Thu Feb 23 06:12:39 2023 +
make create_virtual_device not use a separate alpha layer
so that the gtk and the normal path do the same thing
Change-Id: I69bb7be98e5834b0f20db66a67b3c37cc9d09676
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146566
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/vcl/source/app/salvtables.cxx b/vcl/source/app/salvtables.cxx
index 43a4b6305395..7c2f726a9b9b 100644
--- a/vcl/source/app/salvtables.cxx
+++ b/vcl/source/app/salvtables.cxx
@@ -661,9 +661,10 @@ OUString SalInstanceWidget::strip_mnemonic(const OUString&
rLabel) const
VclPtr SalInstanceWidget::create_virtual_device() const
{
-// create with (annoying) separate alpha layer that LibreOffice itself uses
-return VclPtr::Create(*Application::GetDefaultDevice(),
- DeviceFormat::WITH_ALPHA);
+// create with no separate alpha layer like everything sane does
+auto xRet = VclPtr::Create();
+xRet->SetBackground(COL_TRANSPARENT);
+return xRet;
}
void SalInstanceWidget::call_attention_to()
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #85 from Commit Notification --- niket1322git committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e4fb37353e2f9f998c028319c5fa083bf3eaa4cc tdf#143148 Use pragma once instead of include guards 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-commits] core.git: slideshow/source
slideshow/source/inc/attributableshape.hxx |5 + slideshow/source/inc/expressionnode.hxx|5 + slideshow/source/inc/hyperlinkarea.hxx |5 + 3 files changed, 3 insertions(+), 12 deletions(-) New commits: commit e4fb37353e2f9f998c028319c5fa083bf3eaa4cc Author: niket1322git AuthorDate: Wed Feb 22 21:55:03 2023 +0530 Commit: Ilmari Lauhakangas CommitDate: Thu Feb 23 05:52:01 2023 + tdf#143148 Use pragma once instead of include guards Change-Id: I3d3c34f5f131578c7208c12462f03efac357fa05 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147484 Reviewed-by: Julien Nabet Tested-by: Ilmari Lauhakangas Reviewed-by: Ilmari Lauhakangas diff --git a/slideshow/source/inc/attributableshape.hxx b/slideshow/source/inc/attributableshape.hxx index d903c3b2abbb..f250b60d0e6d 100644 --- a/slideshow/source/inc/attributableshape.hxx +++ b/slideshow/source/inc/attributableshape.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SLIDESHOW_SOURCE_INC_ATTRIBUTABLESHAPE_HXX -#define INCLUDED_SLIDESHOW_SOURCE_INC_ATTRIBUTABLESHAPE_HXX +#pragma once #include @@ -215,6 +214,4 @@ namespace slideshow::internal } -#endif // INCLUDED_SLIDESHOW_SOURCE_INC_ATTRIBUTABLESHAPE_HXX - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/slideshow/source/inc/expressionnode.hxx b/slideshow/source/inc/expressionnode.hxx index 6f9139012e12..7e3e674a8814 100644 --- a/slideshow/source/inc/expressionnode.hxx +++ b/slideshow/source/inc/expressionnode.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SLIDESHOW_SOURCE_INC_EXPRESSIONNODE_HXX -#define INCLUDED_SLIDESHOW_SOURCE_INC_EXPRESSIONNODE_HXX +#pragma once /* Definition of ExpressionNode interface */ @@ -73,6 +72,4 @@ namespace slideshow::internal } -#endif // INCLUDED_SLIDESHOW_SOURCE_INC_EXPRESSIONNODE_HXX - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/slideshow/source/inc/hyperlinkarea.hxx b/slideshow/source/inc/hyperlinkarea.hxx index d7d760c081f7..7ee124d43649 100644 --- a/slideshow/source/inc/hyperlinkarea.hxx +++ b/slideshow/source/inc/hyperlinkarea.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SLIDESHOW_SOURCE_INC_HYPERLINKAREA_HXX -#define INCLUDED_SLIDESHOW_SOURCE_INC_HYPERLINKAREA_HXX +#pragma once #include @@ -93,6 +92,4 @@ namespace slideshow::internal } -#endif // INCLUDED_SLIDESHOW_SOURCE_INC_HYPERLINKAREA_HXX - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */
[Libreoffice-bugs] [Bug 147446] CALC Navigator Insert as Link Non-Functional
https://bugs.documentfoundation.org/show_bug.cgi?id=147446 --- Comment #5 from Colin --- (In reply to Olivier Hallot from comment #4) > This topic is better suited to be detailed in the Calc Guide. > Please bring this issue to the documentation forum at > > https://community.documentfoundation.org/c/documentation/loguides/14 Hi Olivier, Is this comment aimed at me - the initiator - or Roman who brought it to your attention? -- 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|target:7.6.0 |target:7.6.0| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151770] Improve LibreOffice grids -- defaults (Writer/Calc) help page with an answer from ask.libreoffice.org
https://bugs.documentfoundation.org/show_bug.cgi?id=151770 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 153350] Allow user to change bibliography citation number structure
https://bugs.documentfoundation.org/show_bug.cgi?id=153350 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 153350] Allow user to change bibliography citation number structure
https://bugs.documentfoundation.org/show_bug.cgi?id=153350 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 152873] Help Writer → Variables → Numbering by Chapter: Wrong description
https://bugs.documentfoundation.org/show_bug.cgi?id=152873 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 152660] link to text formula help from the formula type form field (calculate with document statistics like word count)
https://bugs.documentfoundation.org/show_bug.cgi?id=152660 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 153471] Ccontinuous write error
https://bugs.documentfoundation.org/show_bug.cgi?id=153471 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 153478] GTK Backend Rendering Areas Completely Black
https://bugs.documentfoundation.org/show_bug.cgi?id=153478 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 153466] Slide imported from PPTX with custom sized background image. When opened in Impress it loses the settings and changes from tile to stretched.
https://bugs.documentfoundation.org/show_bug.cgi?id=153466 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 153469] LibreOffice Impress user interface will stop responding when opening a presentation slide containing a video clip.
https://bugs.documentfoundation.org/show_bug.cgi?id=153469 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 153463] [7.5] Every (empty) document warns about macros (policies.xcd)
https://bugs.documentfoundation.org/show_bug.cgi?id=153463 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 150121] My whole document turns into an unwanted hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=150121 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153456] In skia rendering mode, the bold text will be displayed in green under certain page zoom ratios
https://bugs.documentfoundation.org/show_bug.cgi?id=153456 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 153422] Writer Table Formula Evaluation Errors
https://bugs.documentfoundation.org/show_bug.cgi?id=153422 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 153458] Connecting to database: wrong cursor position for dropping data to Calc sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153458 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 150121] My whole document turns into an unwanted hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=150121 --- Comment #5 from QA Administrators --- Dear Robert Beale, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149960] Crash in: RtlUserThreadStart EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=149960 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149960] Crash in: RtlUserThreadStart EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=149960 --- Comment #3 from QA Administrators --- Dear Paul White, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148042] Base reports crash on Mageia 8 when opened, but not when edited
https://bugs.documentfoundation.org/show_bug.cgi?id=148042 --- Comment #18 from QA Administrators --- Dear I027614, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148042] Base reports crash on Mageia 8 when opened, but not when edited
https://bugs.documentfoundation.org/show_bug.cgi?id=148042 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144282] Crash when changing protection options on document
https://bugs.documentfoundation.org/show_bug.cgi?id=144282 --- Comment #8 from QA Administrators --- Dear Steve Garry, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150617] different page numbering for preliminaries
https://bugs.documentfoundation.org/show_bug.cgi?id=150617 --- Comment #3 from QA Administrators --- Dear Ross Woods, 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 145492] Since latest release (7.1.6.2) replacement of content in cells and comments is unstable.
https://bugs.documentfoundation.org/show_bug.cgi?id=145492 --- Comment #2 from QA Administrators --- Dear John Hart, 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 144497] insert section -- a few suggestions in one
https://bugs.documentfoundation.org/show_bug.cgi?id=144497 --- Comment #5 from QA Administrators --- Dear peter josvai, 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 144475] msiexec addlocal parameter and unit in CA instead of CM
https://bugs.documentfoundation.org/show_bug.cgi?id=144475 --- Comment #5 from QA Administrators --- Dear fl, 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 143157] Alphabetical index field: on mouse-over include keys in tooltips
https://bugs.documentfoundation.org/show_bug.cgi?id=143157 --- Comment #4 from QA Administrators --- Dear R. Green, 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 140732] Establish accessible event to expose cursor position (draw, pointer, text?) on document canvas for use by Assistive Technology tools
https://bugs.documentfoundation.org/show_bug.cgi?id=140732 --- Comment #6 from QA Administrators --- Dear Peter Franke, 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 140253] Links in Index (at least manually set ones)
https://bugs.documentfoundation.org/show_bug.cgi?id=140253 --- Comment #6 from QA Administrators --- Dear bruno.beispiel, 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 75916] Unresetted hidden decimals in positions and sizes
https://bugs.documentfoundation.org/show_bug.cgi?id=75916 --- Comment #8 from QA Administrators --- Dear sergio.callegari, 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 75046] PRINTING Prints off page beyond bottom margin when a row break is in hidden rows
https://bugs.documentfoundation.org/show_bug.cgi?id=75046 --- Comment #6 from QA Administrators --- Dear Chris Severance, 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 71324] EDITING: can't un-bold selection if it crosses hidden lines of an auto-filter
https://bugs.documentfoundation.org/show_bug.cgi?id=71324 --- Comment #15 from QA Administrators --- Dear Toby, 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 140558] Ruler is wrong in document with gutter
https://bugs.documentfoundation.org/show_bug.cgi?id=140558 --- Comment #2 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 140249] FRAME DIALOG: Duplicate items of previous/next links in options tab
https://bugs.documentfoundation.org/show_bug.cgi?id=140249 --- Comment #3 from QA Administrators --- Dear Petr Valach, 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 140467] LO math does not refresh correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=140467 --- Comment #4 from QA Administrators --- Dear dante19031999, 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 134777] EDITING: After adding content to new cells while leaving an empty row after the old content, rerunning autofilter has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=134777 --- Comment #5 from QA Administrators --- Dear Johnny Rosenberg, 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 135148] Delete index redo/index has an effect on the image position
https://bugs.documentfoundation.org/show_bug.cgi?id=135148 --- Comment #2 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 132986] Redefined #REF! values recovers the last value and fórmula, however it's never updated anymore EDITING the referenced cell
https://bugs.documentfoundation.org/show_bug.cgi?id=132986 --- Comment #9 from QA Administrators --- Dear Daniel, 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 122092] FILEOPEN XLS, LO uses formula instead of the mode repeating values.
https://bugs.documentfoundation.org/show_bug.cgi?id=122092 --- Comment #9 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 121322] Paste with 'Dynamic Data Exchange' does not use DDE function but inserts file link
https://bugs.documentfoundation.org/show_bug.cgi?id=121322 --- 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 115894] Default formatting on selected text reset the size of the textbox unexpectedly.
https://bugs.documentfoundation.org/show_bug.cgi?id=115894 --- Comment #5 from QA Administrators --- Dear Mark Hung, 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 151535] FILESAVE After change of Sheet Name results in Crash
https://bugs.documentfoundation.org/show_bug.cgi?id=151535 --- Comment #4 from peter.luke...@gmail.com --- No longer have the file in question - it was Oct 22 after all. Tried to recreate on different file - no success. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141692] When Tabbed interface is applied to all apps, you still have to enter each app to turn on or off the MenuBar individually instead of applying to all.
https://bugs.documentfoundation.org/show_bug.cgi?id=141692 --- Comment #6 from acridtriumph --- I appreciate you sharing the content. I'm quite interested in the details you provided. https://robloxdoors.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Bug 108897 depends on bug 153767, which changed state. Bug 153767 Summary: FILEOPEN XLSX Boolean formula results not loaded, needs recalculation https://bugs.documentfoundation.org/show_bug.cgi?id=153767 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/formula sc/inc sc/source
include/formula/tokenarray.hxx |5 +
sc/inc/document.hxx|2 +-
sc/inc/formulacell.hxx |3 ++-
sc/source/core/data/formulacell.cxx|8 +++-
sc/source/filter/oox/formulabuffer.cxx | 31 ---
sc/source/ui/view/output2.cxx | 13 +++--
6 files changed, 46 insertions(+), 16 deletions(-)
New commits:
commit 05ac57f85eb622b798719db03bbdd07b79e1703a
Author: Eike Rathke
AuthorDate: Thu Feb 23 01:22:16 2023 +0100
Commit: Eike Rathke
CommitDate: Thu Feb 23 01:33:48 2023 +
Resolves: tdf#153767 Try harder to import OOXML bool shared formula result
... by setting the result value or if necessary recalculating even if
AutoCalc is turned off for the document. Similar for other implicitly
recalculating formula types.
Also set a boolean number format if none.
Change-Id: I2f75735707180eccf4b2c525738ac0b763901230
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147425
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/include/formula/tokenarray.hxx b/include/formula/tokenarray.hxx
index cbff6a3e469d..330543d427dc 100644
--- a/include/formula/tokenarray.hxx
+++ b/include/formula/tokenarray.hxx
@@ -430,6 +430,11 @@ public:
example OOXML. */
boolIsRecalcModeMustAfterImport() const
{ return (nMode & ScRecalcMode::EMask) <=
ScRecalcMode::ONLOAD_ONCE; }
+voidClearRecalcModeMustAfterImport()
+{
+if (IsRecalcModeMustAfterImport() &&
!IsRecalcModeAlways())
+SetExclusiveRecalcModeNormal();
+}
/** Get OpCode of the most outer function */
inline OpCode GetOuterFuncOpCode() const;
diff --git a/sc/inc/document.hxx b/sc/inc/document.hxx
index 20e42a999ac8..c6b2f2289ddb 100644
--- a/sc/inc/document.hxx
+++ b/sc/inc/document.hxx
@@ -1224,7 +1224,7 @@ public:
SC_DLLPUBLIC sal_uInt32 GetNumberFormat( SCCOL nCol,
SCROW nRow, SCTAB nTab ) const;
sal_uInt32GetNumberFormat( const ScRange&
rRange ) const;
SC_DLLPUBLIC sal_uInt32 GetNumberFormat( const
ScInterpreterContext& rContext, const ScAddress& ) const;
-void SetNumberFormat( const
ScAddress& rPos, sal_uInt32 nNumberFormat );
+SC_DLLPUBLIC void SetNumberFormat( const
ScAddress& rPos, sal_uInt32 nNumberFormat );
void GetNumberFormatInfo( const
ScInterpreterContext& rContext, SvNumFormatType& nType, sal_uInt32& nIndex,
const ScAddress& rPos ) const;
SC_DLLPUBLIC const ScFormulaCell* GetFormulaCell( const ScAddress&
rPos ) const;
diff --git a/sc/inc/formulacell.hxx b/sc/inc/formulacell.hxx
index e4bc41772e0e..42b7f6120149 100644
--- a/sc/inc/formulacell.hxx
+++ b/sc/inc/formulacell.hxx
@@ -445,7 +445,8 @@ public:
if (!IsDirtyOrInTableOpDirty())
return false;
-return (rDocument.GetAutoCalc() || (cMatrixFlag !=
ScMatrixMode::NONE));
+return rDocument.GetAutoCalc() || (cMatrixFlag != ScMatrixMode::NONE)
+|| (pCode->IsRecalcModeMustAfterImport() &&
!pCode->IsRecalcModeAlways());
}
void MaybeInterpret()
diff --git a/sc/source/core/data/formulacell.cxx
b/sc/source/core/data/formulacell.cxx
index 143b27579a83..0e2840284ec5 100644
--- a/sc/source/core/data/formulacell.cxx
+++ b/sc/source/core/data/formulacell.cxx
@@ -2331,6 +2331,8 @@ void ScFormulaCell::InterpretTail( ScInterpreterContext&
rContext, ScInterpretTa
OSL_ENSURE( pCode->GetCodeError() != FormulaError::NONE, "no RPN code
and no errors ?!?!" );
ResetDirty();
}
+
+pCode->ClearRecalcModeMustAfterImport();
}
void ScFormulaCell::HandleStuffAfterParallelCalculation(ScInterpreter*
pInterpreter)
@@ -2546,7 +2548,7 @@ void ScFormulaCell::SetDirty( bool bDirtyFlag )
// the FormulaTree, once in there it would be assumed that its
// dependents already had been tracked and it would be skipped on a
// subsequent notify. Postpone tracking until all listeners are set.
-if (!rDocument.IsImportingXML())
+if (!rDocument.IsImportingXML() &&
!rDocument.IsInsertingFromOtherDoc())
rDocument.TrackFormulas();
}
@@ -2647,10 +2649,6 @@ void ScFormulaCell::AddRecalcMode( ScRecalcMode nBits )
{
if ( (nBits & ScRecalcMode::EMask) != ScRecalcMode::NORMAL )
SetDirtyVar();
-if ( nBits & ScRecalcMode::ONLOAD_ONCE )
-{ // OnLoadOnce is used only to set Dirty after filter import.
-nBits = (nBits & ~ScRecalcMode::EMask) | ScRecalcMode::NORMAL;
-}
pCode->AddRecalcMode( nBits );
}
diff --git
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 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-ux-advise] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: sw/inc sw/uiconfig
sw/inc/strings.hrc |2 +-
sw/uiconfig/swriter/ui/tocentriespage.ui |5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
New commits:
commit e5a744851cb58da1ceeef623799274d73b60b030
Author: Seth Chaiklin
AuthorDate: Wed Feb 22 00:05:43 2023 +
Commit: Seth Chaiklin
CommitDate: Thu Feb 23 01:13:30 2023 +
tdf#153561 rename "chapter" to "heading"; update/add tool/extended tip
Change-Id: I84cde8117d7eafa4b8656b5b17347a4bd255409e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147369
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index 454df50b1284..ec0903f48560 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -1337,7 +1337,7 @@
#define STR_TOKEN_LINK_STARTNC_("STR_TOKEN_LINK_START",
"LS")
#define STR_TOKEN_LINK_END NC_("STR_TOKEN_LINK_END", "LE")
#define STR_TOKEN_AUTHORITY NC_("STR_TOKEN_AUTHORITY", "A")
-#define STR_TOKEN_HELP_ENTRY_NO NC_("STR_TOKEN_HELP_ENTRY_NO",
"Chapter number")
+#define STR_TOKEN_HELP_ENTRY_NO NC_("STR_TOKEN_HELP_ENTRY_NO",
"Heading number")
#define STR_TOKEN_HELP_ENTRYNC_("STR_TOKEN_HELP_ENTRY",
"Entry")
#define STR_TOKEN_HELP_TAB_STOP NC_("STR_TOKEN_HELP_TAB_STOP",
"Tab stop")
#define STR_TOKEN_HELP_TEXT NC_("STR_TOKEN_HELP_TEXT",
"Text")
diff --git a/sw/uiconfig/swriter/ui/tocentriespage.ui
b/sw/uiconfig/swriter/ui/tocentriespage.ui
index 016357850b71..d97f4ffaa83c 100644
--- a/sw/uiconfig/swriter/ui/tocentriespage.ui
+++ b/sw/uiconfig/swriter/ui/tocentriespage.ui
@@ -582,14 +582,15 @@
-Chapter No.
+Heading No.
True
True
True
True
+Insert in
the entry structure to include heading numbers for the selected level in the
generated index.
-Inserts the chapter number. To
assign chapter numbering to a heading style, choose Tools - Chapter
Numbering.
+Insert in the entry structure
to include heading numbers for the selected level in the generated index. To
enable numbers for headings, choose Tools - Heading Numbering.
[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 153485, which changed state. Bug 153485 Summary: Tooltip for H icon and command name in Heading context menu in Navigator should be "Show Up to Outline Level" https://bugs.documentfoundation.org/show_bug.cgi?id=153485 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153485] Tooltip for H icon and command name in Heading context menu in Navigator should be "Show Up to Outline Level"
https://bugs.documentfoundation.org/show_bug.cgi?id=153485 sdc.bla...@youmail.dk changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Summary|Tooltip for H icon in |Tooltip for H icon and |Navigator should be |command name in Heading |"Outline Level" |context menu in Navigator ||should be "Show Up to ||Outline Level" --- Comment #18 from sdc.bla...@youmail.dk --- Amusing side note, discovered post-facto. Until the patch in comment 17, the help for "Outline Level" has not changed since its initial 2004 check-in. Here is a relevant excerpt. Click this icon ... You can also access this command by right-clicking a heading in the Navigator window. Meanwhile, the first version of navigatorpanel.ui (late 2016) had "Heading Levels Shown" as the tooltip for the icon (and I assume it was present even longer back), while "Outline Level" has been in the context menu forever. So -- nice that this ticket could bring the UI into line with the help. (-: Have updated summary to better reflect the change. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||8518, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=64 ||222 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 Justin L changed: What|Removed |Added Version|7.2.3.2 release |7.2.0.0.alpha0+ Hardware|x86-64 (AMD64) |All --- Comment #8 from Justin L --- We have been battling these kinds of things for years in DOC and DOCX formats, so having partial remnants of ms format compatibility flags in your documents going to cause you problems. P.S. It should be sufficient to round-trip once as DOCX to pick up the latest compat flags and then you could save back again into ODT format if you prefer using the native file format. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152033] Memory leakage when using Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152033 --- Comment #3 from James Sheehan --- Created attachment 185539 --> https://bugs.documentfoundation.org/attachment.cgi?id=185539=edit Multiple Copies of the US Constitution as a sample file to duplicate the bug I was able to duplicate the bug with this file as described in my previous post. Open the file and continuously scroll through the file using the scroll wheel. In this case, the memory usage reached 96% before crashing. When the CPU usage spiked, I saw that Windows Problem Reporting program go to the top of the usage list. However, when I tried this a second time it did not crash. In order to get it to crash, I opened a second file and switched back and forth scrolling in each file. This is consistent with what I do in actual editing, cutting and pasting between files. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||0613 --- Comment #7 from Justin L --- This is basically a duplicate of bug 150613. This file must have spent part of its life as a Microsoft format. This has the setting ApplyParagraphMarkFormatToNumbering = true, which was a (poor) way to handle Microsoft's ability to apply carriage-return formatting to the numbering. Well, LO doesn't have the ability to format a carriage return - and thus the compatibility flag. I expect this will just need to be worked around. Some suggestions: 1.) save as DOCX (or DOC) since those formats now have improved abilities to deal with this, and basically now avoid this section of code. 2.) Select the whole document (Ctrl-A) and copy/paste into a new document. 3.) unzip the ODT, and change (or delete) settings.xml's ApplyParagraphMarkFormatToNumbering. (This could probably be scripted, although there is some trickery about "properly" zipping up an ODT file.) I don't think we can adapt the code to do something like #1's fix for isODT - because those all have to do with compatibility settings, and I'm not aware of ODT loading any flags that wouldn't apply to importing an MS Format. (In fact, this is the only place in the SW code that we have an "IsDOCX" variable.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153606] macOS app icon is not properly integrated
https://bugs.documentfoundation.org/show_bug.cgi?id=153606 --- Comment #22 from alexandre burton --- interesting! maybe make it a tiny bit higher than the official squircle to compensate the reduced surface? make the white doc almost the squircle height? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit e54838a5f8629226dce0498a5ec178ca5e03b886 Author: Seth Chaiklin AuthorDate: Thu Feb 23 00:22:55 2023 + Commit: Gerrit Code Review CommitDate: Thu Feb 23 00:22:55 2023 + Update git submodules * Update helpcontent2 from branch 'master' to ac82657672e6d9867e4d8560536e241ca4814da6 - tdf#153485 Update "Outline level" -> "Show up to outline level" also improve command description Change-Id: I5ce25e704688c0af4c659066d4ffb339a01bce7e Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147443 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/helpcontent2 b/helpcontent2 index c9e84e0aa79e..ac82657672e6 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit c9e84e0aa79ec1ddeae1e53d1bf70920bb85d896 +Subproject commit ac82657672e6d9867e4d8560536e241ca4814da6
[Libreoffice-bugs] [Bug 153485] Tooltip for H icon in Navigator should be "Outline Level"
https://bugs.documentfoundation.org/show_bug.cgi?id=153485 --- Comment #17 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/ac82657672e6d9867e4d8560536e241ca4814da6 tdf#153485 Update "Outline level" -> "Show up to outline level" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/0211.xhp | 19 +-- 1 file changed, 9 insertions(+), 10 deletions(-) New commits: commit ac82657672e6d9867e4d8560536e241ca4814da6 Author: Seth Chaiklin AuthorDate: Wed Feb 22 23:14:51 2023 + Commit: Seth Chaiklin CommitDate: Thu Feb 23 00:22:54 2023 + tdf#153485 Update "Outline level" -> "Show up to outline level" also improve command description Change-Id: I5ce25e704688c0af4c659066d4ffb339a01bce7e Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147443 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/source/text/swriter/01/0211.xhp b/source/text/swriter/01/0211.xhp index c6660201d0..ebd3c66bbb 100644 --- a/source/text/swriter/01/0211.xhp +++ b/source/text/swriter/01/0211.xhp @@ -130,7 +130,7 @@ Heading item -Collapse/Expand All, Go to, Select, Delete, Move Chapter Up, Move Chapter Down, Promote Outline Level, Demote Outline Level, Outline Content Visibility, Outline Tracking, Outline Level +Collapse/Expand All, Go to, Select, Delete, Move Chapter Up, Move Chapter Down, Promote Outline Level, Demote Outline Level, Outline Content Visibility, Outline Tracking, Show Up to Outline Level @@ -397,24 +397,23 @@ -Outline Level +Show Up to Outline Level +Click the icon at the top of Navigator or right-click a heading in the Navigator window, then choose how many levels of headings to show in the Headings section of the Navigator window. + + +For example, choose 1 to only show headings with outline level 1. Choose 3 to show headings up to outline level 3; choose 10 to show all headings. + - Icon Outline level + Icon Show Up to Outline Level - Outline level + Show Up to Outline Level -Click this icon, and then choose the number of heading outline levels that you want to view in the Navigator window. You can also access this command by right-clicking a heading in the Navigator window. - - -1-10 -Click 1 to only view the top level headings (chapter heading) in the Navigator window, and 10 to view all of the headings. - List Box
[Libreoffice-bugs] [Bug 153606] macOS app icon is not properly integrated
https://bugs.documentfoundation.org/show_bug.cgi?id=153606 --- Comment #21 from خالد حسني --- Created attachment 185538 --> https://bugs.documentfoundation.org/attachment.cgi?id=185538=edit Icon without background My suggestion would be to drop the outer white background and enlarge the document drawing so it fills the current icon height. The different amount of white space that the current icon has vertically vs horizontally, makes it IMO feel unbalanced, removing the background makes this less pronounced. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151694] Sifr: The Mime Types for MS Office Files Are Missing or Too Generic
https://bugs.documentfoundation.org/show_bug.cgi?id=151694 --- Comment #5 from Rizal Muttaqin --- (In reply to Buovjaga from comment #4) > Should the status be fixed? This bug need coding and not related to any icon theme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152033] Memory leakage when using Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152033 James Sheehan changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 Alias||Snoopy48 --- Comment #2 from James Sheehan --- Hardware: (PC) Processor: 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz Memory:12.0GB Software: Operating System: Windows 11 Home 22H2 22621.1265 LibreOffice Version: 7.3.7.2 (x64) / LibreOffice Community 1. In Windows 11, open task manager showing memory usage graph 2. Open LibreOffice Writer and a large file (doesn't have to be a large file, but it is easier/faster to duplicate with it - I think I have seen this with multiple smaller files open when cutting and pasting between files). My sample file is about 350 pages long with lots of text and is in Word .docx format. Opening the file does not cause memory usage to bump up very much. I decided to not include the sample file since it contained personal information. However, I have seen this with several different files. Also, my files are on a Sandisk SSD (2TB) connected via USB 3.0. Less than half the space on the SSD is used. 3. With File Manager visible (1/2 screen) and LibreOffice 1/2 screen (in order to monitor the memory usage), start scrolling through the file continuously. I have a trackball and use the scroll wheel. 4. Continue scrolling through the file. Note that the memory usage continues to increment as you scroll through the file. When the memory usage hits 94%, CPU usage jumps and LibreOffice freezes, then crashes and closes. For me, this causes a crash of LibreOffice every time. I have had similar crashes on my Linux Mint machine, but didn't know how to duplicate the problem. If desired, I can fire it up later and try to duplicate there, now knowing how to duplicate it. I suspect that this memory leak (or perhaps there is a better term) is the root cause of several other bug reports. I am also fairly certain I experienced this same issue on previous versions of LibreOffice. The "work around" is to save changes frequently. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140986] LO hangs when you select a cell with validity's drop-down
https://bugs.documentfoundation.org/show_bug.cgi?id=140986 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #18 from raal --- Still freeze in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 14844d835cc5d6dfde499a0b1074aea5dcff4fc7 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 raal changed: What|Removed |Added CC||jl...@mail.com, ||r...@post.cz Keywords|possibleRegression |bibisected, bisected, ||regression Regression By||Justin Luth --- Comment #6 from raal --- This seems to have begun at the below commit. Adding Cc: to Justin Luth ; Could you possibly take a look at this one? Thanks 0ecb686a9b7b69dfb5f0b8e0d0cad482efda8f63 is the first bad commit commit 0ecb686a9b7b69dfb5f0b8e0d0cad482efda8f63 Author: Jenkins Build User Date: Thu Mar 18 19:45:16 2021 +0100 source sha:0a32371cc2f93fad7954e0fe9c48976aae6c5b9f https://git.libreoffice.org/core/+/0a32371cc2f93fad7954e0fe9c48976aae6c5b9f -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #6 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #5) > also contains everything around bibliographies (though I haven't found this > list in the sources). what list are you looking for? Perhaps the "confusion" mentioned in comment 3 is no longer relevant, with localization, such that it is meaningful to change E#? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #6 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #5) > also contains everything around bibliographies (though I haven't found this > list in the sources). what list are you looking for? Perhaps the "confusion" mentioned in comment 3 is no longer relevant, with localization, such that it is meaningful to change E#? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa writerfilter/source
sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx |binary
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx |7 ++
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 11
++
3 files changed, 14 insertions(+), 4 deletions(-)
New commits:
commit dbbfcb7e098c1c16f932785ef62ef7d3d819ad1a
Author: Justin Luth
AuthorDate: Wed Feb 22 11:19:40 2023 -0500
Commit: Justin Luth
CommitDate: Wed Feb 22 22:35:06 2023 +
tdf#153526 writerfilter: catch exception from no NumberingRules
This fixes a LO 7.5 regression (well, exposed some other flaws) from
commit cf02b94bc513ee1b742b4c5d7174632b568e8b72.
I first tried testing if hasPropertyByName,
but that returns true(), even though this is an editeng component.
Well, ignoring the fundamental issues at play here
(and there are many - like having a comment
take over m_xPreviousParagraph)
the issue is easily solved with a try/catch
instead of a redundant if clause.
Change-Id: I4f27fce3e2984235df19dc3ed4be558891b28a90
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147486
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx
b/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx
new file mode 100644
index ..f26240092c10
Binary files /dev/null and
b/sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
index 8b6795b726c5..2e71b5bcc7fe 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
@@ -80,6 +80,13 @@ DECLARE_OOXMLEXPORT_TEST(testTdf147646,
"tdf147646_mergedCellNumbering.docx")
CPPUNIT_ASSERT_EQUAL(OUString("2."),parseDump("/root/page/body/tab/row[4]/cell/txt/SwParaPortion/SwLineLayout/child::*[@type='PortionType::Number']","expand"));
}
+DECLARE_OOXMLEXPORT_TEST(testTdf153526_commentInNumbering,
"tdf153526_commentInNumbering.docx")
+{
+// an exception was prematurely ending finishParagraph, losing numbering
and CRs
+// so before the patch, this was 6.
+CPPUNIT_ASSERT_EQUAL(13, getParagraphs());
+}
+
DECLARE_OOXMLEXPORT_TEST(testTdf153042_largeTab, "tdf153042_largeTab.docx")
{
// This is not the greatest test because it is slightly weird, and has a
different layout
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index efc83477f818..558d71f90fe7 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++ b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
@@ -2332,11 +2332,14 @@ void DomainMapper_Impl::finishParagraph( const
PropertyMapPtr& pPropertyMap, con
uno::Reference
xCurrentNumberingRules(itNumberingRules->Value, uno::UNO_QUERY);
if (xCurrentNumberingRules.is())
aCurrentNumberingName =
xCurrentNumberingRules->getName();
-if (m_xPreviousParagraph.is())
+try
+{
+uno::Reference
xPreviousNumberingRules(m_xPreviousParagraph->getPropertyValue("NumberingRules"),
uno::UNO_QUERY_THROW);
+aPreviousNumberingName =
xPreviousNumberingRules->getName();
+}
+catch (const uno::Exception&)
{
-uno::Reference
xPreviousNumberingRules(m_xPreviousParagraph->getPropertyValue("NumberingRules"),
uno::UNO_QUERY);
-if (xPreviousNumberingRules.is())
-aPreviousNumberingName =
xPreviousNumberingRules->getName();
+TOOLS_WARN_EXCEPTION("writerfilter",
"DomainMapper_Impl::finishParagraph NumberingRules");
}
}
else if (
m_xPreviousParagraph->getPropertySetInfo()->hasPropertyByName("NumberingStyleName")
&&
[Libreoffice-bugs] [Bug 153770] Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index
https://bugs.documentfoundation.org/show_bug.cgi?id=153770 --- Comment #9 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #8) > Table of Objects shows a different part of the UI with the string "Create > From the Following Objects"; Implicit in the proposal in comment 2 was that "the Following Objects" should be deleted from the section title for "Table of Objects" (Given that a list of objects are shown, there is little or no information value in "the Following Objects"). -- 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 sdc.bla...@youmail.dk changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 Bug 120200 depends on bug 152977, which changed state. Bug 152977 Summary: improve help for the search attribute "Individual Words" https://bugs.documentfoundation.org/show_bug.cgi?id=152977 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 Commit Notification changed: What|Removed |Added Whiteboard| QA:needsComment| QA:needsComment ||target:7.6.0 -- 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 --- Comment #1 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/c9e84e0aa79ec1ddeae1e53d1bf70920bb85d896 tdf#152977 correction to description for "Individual Words" attribute -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 681f8e6e97ec45de3305e2056ccd8415582ba705 Author: Seth Chaiklin AuthorDate: Wed Feb 22 22:23:19 2023 + Commit: Gerrit Code Review CommitDate: Wed Feb 22 22:23:19 2023 + Update git submodules * Update helpcontent2 from branch 'master' to c9e84e0aa79ec1ddeae1e53d1bf70920bb85d896 - tdf#152977 correction to description for "Individual Words" attribute Change-Id: I277b6dbce5eb2d8812a5fb51693cf2574704a47c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147442 Reviewed-by: Seth Chaiklin Tested-by: Jenkins diff --git a/helpcontent2 b/helpcontent2 index 48e0b7962fdc..c9e84e0aa79e 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 48e0b7962fdcfd46f8754ffa6c15dc149719f523 +Subproject commit c9e84e0aa79ec1ddeae1e53d1bf70920bb85d896
[Libreoffice-commits] help.git: source/text
source/text/shared/01/02100200.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit c9e84e0aa79ec1ddeae1e53d1bf70920bb85d896 Author: Seth Chaiklin AuthorDate: Wed Feb 22 22:12:02 2023 + Commit: Seth Chaiklin CommitDate: Wed Feb 22 22:23:18 2023 + tdf#152977 correction to description for "Individual Words" attribute Change-Id: I277b6dbce5eb2d8812a5fb51693cf2574704a47c Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147442 Reviewed-by: Seth Chaiklin Tested-by: Jenkins diff --git a/source/text/shared/01/02100200.xhp b/source/text/shared/01/02100200.xhp index da757b8d46..2d67988836 100644 --- a/source/text/shared/01/02100200.xhp +++ b/source/text/shared/01/02100200.xhp @@ -151,7 +151,7 @@ Individual Words - Finds characters formatted with Underlining or Strikethrough as Individual words. + Finds characters with the Individual Words attribute, which can be set when using Underlining, Strikethrough and Overlining. Character background
[Libreoffice-commits] core.git: cui/uiconfig
cui/uiconfig/ui/editmodulesdialog.ui |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 7df725eda3330d62da204a95a177df1ae5b11f73 Author: Seth Chaiklin AuthorDate: Tue Feb 7 11:33:58 2023 + Commit: Seth Chaiklin CommitDate: Wed Feb 22 22:20:49 2023 + (related tdf#153417) rename "Back" to "Reset" Change-Id: I70c79f7a40889bcca3aed3d2309779091967a2e2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146532 Tested-by: Jenkins Reviewed-by: Heiko Tietze diff --git a/cui/uiconfig/ui/editmodulesdialog.ui b/cui/uiconfig/ui/editmodulesdialog.ui index 10353d4f0668..eea4ac07289e 100644 --- a/cui/uiconfig/ui/editmodulesdialog.ui +++ b/cui/uiconfig/ui/editmodulesdialog.ui @@ -231,7 +231,7 @@ -_Back +_Reset True True True
[Libreoffice-bugs] [Bug 153417] no help page for Edit Modules in Options - Language Settings - Writing Aids
https://bugs.documentfoundation.org/show_bug.cgi?id=153417 --- Comment #8 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/7df725eda3330d62da204a95a177df1ae5b11f73 (related tdf#153417) rename "Back" to "Reset" 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.
