[Libreoffice-bugs] [Bug 152091] Addition of several groups of contiguous cells gives "#Value!"

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152091

--- Comment #4 from Julien Nabet  ---
Created attachment 183657
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183657=edit
testfile

Sorry I had forgotten the attachment.

BTW, sum in status bar at bottom right (don't know if it's the right naming)
provides correct sum, 210, so Calc considers it as a plain sum in this case.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 91902] Increase and decrease indent buttons not accessible in textbox edit mode

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91902

Dieter  changed:

   What|Removed |Added

  Component|LibreOffice |Calc

--- Comment #8 from Dieter  ---
Still present in

Version: 7.4.3.1 (x64) / LibreOffice Community
Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151846

--- Comment #5 from Noel Grandin  ---
I can't see any use of 
  - XTransformation 
  - XDataInterpreter
  - InterpretedData
in your code, so it looks like you only actually need XChartTypeTemplate ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152091] Addition of several groups of contiguous cells gives "#Value!"

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152091

--- Comment #3 from estesprit...@yahoo.com ---
=A1:A2 doesn't tell Calc what to do with this matrix, do Calc cannot know the
user wants to sum the matrix. LeroyG is right, OP should tell Calc about it by
using the SUM function.

Not a bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: Branch 'private/tvajngerl/staging' - 4 commits - basegfx/test editeng/source include/basegfx include/editeng include/svx sd/source svx/source

2022-11-17 Thread Tomaž Vajngerl (via logerrit)
Rebased ref, commits from common ancestor:
commit 5038cb51cb48d1661103690b44f7fac01dd5a324
Author: Tomaž Vajngerl 
AuthorDate: Fri Nov 18 16:37:33 2022 +0900
Commit: Tomaž Vajngerl 
CommitDate: Fri Nov 18 16:37:33 2022 +0900

basegfx: add setSize, setPosition to range classes, add tests

Change-Id: Idf01d1254e7327f1816e7b58d882bcc5ec9efae2

diff --git a/basegfx/test/B1DRangeTest.cxx b/basegfx/test/B1DRangeTest.cxx
index 22cf662defe5..9c3c12e37684 100644
--- a/basegfx/test/B1DRangeTest.cxx
+++ b/basegfx/test/B1DRangeTest.cxx
@@ -25,72 +25,115 @@
 
 namespace basegfx
 {
-class b1Xrange : public CppUnit::TestFixture
+class B1DRangeTest : public CppUnit::TestFixture
 {
 public:
-template  void implCheck()
+void checkIntervalAxioms()
 {
 // test interval axioms
 // (http://en.wikipedia.org/wiki/Interval_%28mathematics%29)
-Type aRange;
+B1DRange aRange;
 CPPUNIT_ASSERT_MESSAGE("default ctor - empty range", aRange.isEmpty());
-CPPUNIT_ASSERT_MESSAGE("center - get cop-out value since range is 
empty",
-   aRange.getCenter() == 0);
+CPPUNIT_ASSERT_EQUAL_MESSAGE("center - get cop-out value since range 
is empty", 0.0,
+ aRange.getCenter());
 
 // degenerate interval
 aRange.expand(1);
+CPPUNIT_ASSERT_EQUAL(B1DRange(1.0, 1.0), aRange);
 CPPUNIT_ASSERT_MESSAGE("degenerate range - still, not empty!", 
!aRange.isEmpty());
-CPPUNIT_ASSERT_MESSAGE("degenerate range - size of 0", 
aRange.getRange() == 0);
+CPPUNIT_ASSERT_EQUAL_MESSAGE("degenerate range - size of 0", 0.0, 
aRange.getRange());
 CPPUNIT_ASSERT_MESSAGE("same value as degenerate range - is inside 
range",
-   aRange.isInside(1));
-CPPUNIT_ASSERT_MESSAGE("center - must be the single range value", 
aRange.getCenter() == 1);
+   aRange.isInside(1.0));
+CPPUNIT_ASSERT_EQUAL_MESSAGE("center - must be the single range 
value", 1.0,
+ aRange.getCenter());
 
 // proper interval
-aRange.expand(2);
-CPPUNIT_ASSERT_MESSAGE("proper range - size of 1", aRange.getRange() 
== 1);
+aRange.expand(2.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(1.0, 2.0), aRange);
+CPPUNIT_ASSERT_EQUAL_MESSAGE("proper range - size of 1", 1.0, 
aRange.getRange());
 CPPUNIT_ASSERT_MESSAGE("smaller value of range - is inside *closed* 
range",
aRange.isInside(1));
 CPPUNIT_ASSERT_MESSAGE("larger value of range - is inside *closed* 
range",
aRange.isInside(2));
 
 // center for proper interval that works for ints, too
-aRange.expand(3);
-CPPUNIT_ASSERT_MESSAGE("center - must be half of the range", 
aRange.getCenter() == 2);
+aRange.expand(3.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(1.0, 3.0), aRange);
+CPPUNIT_ASSERT_EQUAL_MESSAGE("center - must be half of the range", 
2.0, aRange.getCenter());
+}
+
+void checkOverlap()
+{
+B1DRange aRange(1.0, 3.0);
+B1DRange aRange2(0.0, 1.0);
 
-// check overlap
-Type aRange2(0, 1);
 CPPUNIT_ASSERT_MESSAGE("range overlapping *includes* upper bound",
aRange.overlaps(aRange2));
 CPPUNIT_ASSERT_MESSAGE("range overlapping *includes* upper bound, but 
only barely",
!aRange.overlapsMore(aRange2));
 
-Type aRange3(0, 2);
+B1DRange aRange3(0.0, 2.0);
 CPPUNIT_ASSERT_MESSAGE("range overlapping is fully overlapping now",
aRange.overlapsMore(aRange3));
+}
 
-// check intersect
-Type aRange4(3, 4);
-aRange.intersect(aRange4);
+void checkIntersect()
+{
+B1DRange aRange(1.0, 3.0);
+B1DRange aRange2(3.0, 4.0);
+aRange.intersect(aRange2);
 CPPUNIT_ASSERT_MESSAGE("range intersection is yielding empty range!", 
!aRange.isEmpty());
 
-Type aRange5(5, 6);
-aRange.intersect(aRange5);
+B1DRange aRange3(5.0, 6.0);
+aRange.intersect(aRange3);
 CPPUNIT_ASSERT_MESSAGE("range intersection is yielding nonempty 
range!", aRange.isEmpty());
 }
 
-void check() { implCheck(); }
+void checkShift()
+{
+B1DRange aRange(1.0, 3.0);
+aRange.shift(2.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(3.0, 5.0), aRange);
+
+B1DRange aRange2(-1.0, -3.0);
+aRange2.shift(2.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(1.0, -1.0), aRange2);
+}
+
+void checkSetSize()
+{
+B1DRange aRange(1.0, 3.0);
+aRange.setSize(5.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(1.0, 6.0), aRange);
+
+B1DRange aRange2(-1.0, -3.0);
+aRange2.setSize(3.0);
+CPPUNIT_ASSERT_EQUAL(B1DRange(-3.0, 

[Libreoffice-bugs] [Bug 129434] [META] Writer (EDITING) Suggested bug fixes, enhancements and features for authors.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129434
Bug 129434 depends on bug 92821, which changed state.

Bug 92821 Summary: Make Shift-F5 jump to the last four places where you edited 
something
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

   What|Removed |Added

 Status|RESOLVED|NEW
 Resolution|DUPLICATE   |---

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108018] [META] Writer UX bugs and enhancements

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108018
Bug 108018 depends on bug 92821, which changed state.

Bug 92821 Summary: Make Shift-F5 jump to the last four places where you edited 
something
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

   What|Removed |Added

 Status|RESOLVED|NEW
 Resolution|DUPLICATE   |---

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 92821] Make Shift-F5 jump to the last four places where you edited something

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

Mike Kaganski  changed:

   What|Removed |Added

 Status|RESOLVED|NEW
 Resolution|DUPLICATE   |---

--- Comment #13 from Mike Kaganski  ---
I disagree that an idea to have a set of "visit history" points is a dupe of
bug 141586. I don't know how to define each such point (e.g., when the view
shifts when you type - is it another point? When you page up/gown, is each
keypress a new point?)

No idea how realistic it is; if someone has a reasonable implementation idea,
why not.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152102] New: PIVOTTABLE: Compatibility is lost between versions of Calc

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152102

Bug ID: 152102
   Summary: PIVOTTABLE: Compatibility is lost between versions of
Calc
   Product: LibreOffice
   Version: 6.0.7.3 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: iobal...@gmail.com

PIVOTTABLE: When I modify in Calc 7.3 a spreadsheet made in Calc 6.0.7.3, it is
lost for the for the older version.
The pivottable still works in Calc 7.3 but if I open it after in Calc 6.0.7.3,
the values remain in the cells but no longer correspond to a pivot table, so
they cannot be recalculated/updated.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 129434] [META] Writer (EDITING) Suggested bug fixes, enhancements and features for authors.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129434
Bug 129434 depends on bug 92821, which changed state.

Bug 92821 Summary: Make Shift-F5 jump to the last four places where you edited 
something
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108018] [META] Writer UX bugs and enhancements

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108018
Bug 108018 depends on bug 92821, which changed state.

Bug 92821 Summary: Make Shift-F5 jump to the last four places where you edited 
something
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141586

Hagar Delest  changed:

   What|Removed |Added

 CC||j...@vansomeren.co.uk

--- Comment #9 from Hagar Delest  ---
*** Bug 92821 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 92821] Make Shift-F5 jump to the last four places where you edited something

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92821

Hagar Delest  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #12 from Hagar Delest  ---


*** This bug has been marked as a duplicate of bug 141586 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141586

--- Comment #8 from Hagar Delest  ---
The status is still UNCONFIRMED. Shouldn't it be changed to NEW?

For those interested, here is a set of macros that mimic MS Word behavior (and
one of the proposed solutions):
https://forum.openoffice.org//en/forum/viewtopic.php?t=108684

Assign the 2 macros (1 to set the bookmark, 1 to retrieve the position) to
buttons or events for example. Can take a few seconds or need to run the macro
several times to retrieve the position, depending on the length and complexity
of the document (the repagination has to be finished first).

Note: several versions available in the forum discussion.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 132631] Broken attachment download in Safari

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132631

--- Comment #2 from Olivia James  ---
Agree

Visit here:
https://blogsteak.com/mastering-great-customer-service-skills-with-these-4-major-tactics/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141586

Hagar Delest  changed:

   What|Removed |Added

 CC||ceki...@gmx.net

--- Comment #7 from Hagar Delest  ---
*** Bug 140147 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 140147] position of cursor not saved

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140147

Hagar Delest  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #42 from Hagar Delest  ---


*** This bug has been marked as a duplicate of bug 141586 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #8 from fml2  ---
Also I noticed that after selecting a thin line as the border for the chart,
the line only appers on the right and at the bottom, but not on the left and
the top side of the chart. But this is another issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #7 from fml2  ---
Created attachment 183656
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183656=edit
Dropdown with "Use skia" disabled

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #6 from fml2  ---
Without skia, it's still blurred, see the attachment.

I also tried to disable the options "Use antialiasing" and "Use hardware
acceleration", it did not change anything.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #5 from fml2  ---
In the cell border format, lines are not blurred in the dropdown.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113882] Report editor's Sorting and Grouping is not always updated after a Data Content change

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113882

--- Comment #5 from Robert Großkopf  ---
Bug still exists in LO 7.4.3.1 on OpenSUSE 15.3 64bit rpm Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152101] Mumbai Escorts Service

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152101

Mumbai escorts  changed:

   What|Removed |Added

URL||https://www.sanakaur.com/
   Keywords||bibisected

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152101] New: Mumbai Escorts Service

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152101

Bug ID: 152101
   Summary: Mumbai Escorts Service
   Product: Impress Remote
   Version: 1.0.0
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: General
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sanakaur...@gmail.com

Description:
The Mumbai Escorts at our agency know how to fulfill the demands of men. The
call girls at Mumbai Escort Service have magical touch that will make you go
crazy. So, to experience lovely physical pleasure at an affordable rate,
contact our escort service in Mumbai. 
https://www.sanakaur.com/


Actual Results:

https://www.sanakaur.com/


Expected Results:
https://www.sanakaur.com/


Reproducible: Always


User Profile Reset: No

Additional Info:

https://www.sanakaur.com/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103182

Heiko Tietze  changed:

   What|Removed |Added

 Depends on|152088  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152088
[Bug 152088] Navigator (F5) can not be docked using Wayland
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152088] Navigator (F5) can not be docked using Wayland

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

Heiko Tietze  changed:

   What|Removed |Added

Summary|[UI] Navigator (F5, View >  |Navigator (F5) can not be
   |Navigator) can not be   |docked using Wayland
   |docked at the left side any |
   |more..  |
 Blocks|103182  |

--- Comment #9 from Heiko Tietze  ---
(In reply to V Stuart Foote from comment #2)
> Continues to dock w/frame drag, 
Never worked for me
> +2x mouse click, or with 
Both work well

// loginctl show-session 1 -p Type: Type=x11

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (en_US.UTF-8); UI: en-US
7.4.2-2
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103182
[Bug 103182] [META] GTK3-specific bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

--- Comment #3 from Mike Kaganski  ---
On the other hand, it opens fast (under 4 s on my system) using Version:
7.4.3.1 (x64) / LibreOffice Community
Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL

=> WORKSFORME?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: include/vcl vcl/CppunitTest_vcl_font.mk vcl/qa

2022-11-17 Thread Chris Sherlock (via logerrit)
 include/vcl/outdev.hxx |2 -
 vcl/CppunitTest_vcl_font.mk|5 ++
 vcl/qa/cppunit/logicalfontinstance.cxx |   59 +
 3 files changed, 65 insertions(+), 1 deletion(-)

New commits:
commit 0cef06f0a2c0963e8c1579b78975710e6af4471c
Author: Chris Sherlock 
AuthorDate: Wed Oct 19 11:20:19 2022 +0200
Commit: Tomaž Vajngerl 
CommitDate: Fri Nov 18 07:40:46 2022 +0100

vcl: test getting glyph boundary rect from LogicalFontInstance

MacOS produces a slightly different glyph height.

Quoting from Khaled in dev IRC:

"Currently GetGlyphBoundRect() calls different platform-specific
implementations on each platform, so even with the same font it is
possible to get some difference. So my suggestion is to use a large font
size and allow for some fuzziness".

Consequently I'm using a 110pt font.

Change-Id: I939e633eb1e45a16171ad0675216246b31966454
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141234
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/include/vcl/outdev.hxx b/include/vcl/outdev.hxx
index 14c1675e7eed..b4fdd82e1ab9 100644
--- a/include/vcl/outdev.hxx
+++ b/include/vcl/outdev.hxx
@@ -1176,7 +1176,7 @@ public:
 //If bNewFontLists is true then drop and refetch lists of system fonts
 SAL_DLLPRIVATE static void  ImplUpdateAllFontData( bool bNewFontLists );
 
-SAL_DLLPRIVATE const LogicalFontInstance* GetFontInstance() const;
+const LogicalFontInstance* GetFontInstance() const;
 
 protected:
 SAL_DLLPRIVATE tools::Long GetEmphasisAscent() const { return 
mnEmphasisAscent; }
diff --git a/vcl/CppunitTest_vcl_font.mk b/vcl/CppunitTest_vcl_font.mk
index 891352508a1c..813ab1c9c009 100644
--- a/vcl/CppunitTest_vcl_font.mk
+++ b/vcl/CppunitTest_vcl_font.mk
@@ -20,6 +20,7 @@ $(eval $(call gb_CppunitTest_add_exception_objects,vcl_font, \
vcl/qa/cppunit/physicalfontfacecollection \
vcl/qa/cppunit/physicalfontfamily \
vcl/qa/cppunit/physicalfontcollection \
+   vcl/qa/cppunit/logicalfontinstance \
 ))
 
 $(eval $(call gb_CppunitTest_use_externals,vcl_font,\
@@ -56,4 +57,8 @@ $(eval $(call gb_CppunitTest_use_components,vcl_font,\
 
 $(eval $(call gb_CppunitTest_use_configuration,vcl_font))
 
+$(eval $(call gb_CppunitTest_use_more_fonts,vcl_font))
+
+$(eval $(call gb_CppunitTest_set_non_application_font_use,vcl_font,abort))
+
 # vim: set noet sw=4 ts=4:
diff --git a/vcl/qa/cppunit/logicalfontinstance.cxx 
b/vcl/qa/cppunit/logicalfontinstance.cxx
new file mode 100644
index ..56b9897f0589
--- /dev/null
+++ b/vcl/qa/cppunit/logicalfontinstance.cxx
@@ -0,0 +1,59 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include 
+
+#include 
+#include 
+
+#include 
+#include 
+
+#include 
+
+#include 
+
+class VclLogicalFontInstanceTest : public test::BootstrapFixture
+{
+public:
+VclLogicalFontInstanceTest()
+: BootstrapFixture(true, false)
+{
+}
+
+void testglyphboundrect();
+
+CPPUNIT_TEST_SUITE(VclLogicalFontInstanceTest);
+CPPUNIT_TEST(testglyphboundrect);
+
+CPPUNIT_TEST_SUITE_END();
+};
+
+void VclLogicalFontInstanceTest::testglyphboundrect()
+{
+ScopedVclPtr device = 
VclPtr::Create(DeviceFormat::DEFAULT);
+device->SetOutputSizePixel(Size(1000, 1000));
+device->SetFont(vcl::Font("Liberation Sans", Size(0, 110)));
+
+const LogicalFontInstance* pFontInstance = device->GetFontInstance();
+
+tools::Rectangle aBoundRect;
+const auto LATIN_SMALL_LETTER_B = 0x0062;
+
pFontInstance->GetGlyphBoundRect(pFontInstance->GetGlyphIndex(LATIN_SMALL_LETTER_B),
 aBoundRect,
+ false);
+#ifdef MACOSX
+CPPUNIT_ASSERT_EQUAL(tools::Rectangle(Point(7, -80), Size(51, 83)), 
aBoundRect);
+#else
+CPPUNIT_ASSERT_EQUAL(tools::Rectangle(Point(7, -80), Size(51, 82)), 
aBoundRect);
+#endif
+}
+
+CPPUNIT_TEST_SUITE_REGISTRATION(VclLogicalFontInstanceTest);
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s 
cinkeys+=0=break: */


[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

Mike Kaganski  changed:

   What|Removed |Added

   Keywords||perf

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143209] Edge Scrolling no longer works properly on my touchpad beginning with version 6.2 and newer.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143209

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||ilmari.lauhakangas@libreoff
   ||ice.org,
   ||jeyov45...@sinagalore.com
 Status|UNCONFIRMED |NEW

--- Comment #10 from Buovjaga  ---
(In reply to jeyov45316 from comment #9)
> Created attachment 183655 [details]
> Patch that fixes the bug. Developed against libreoffice-core commit
> 0eec6d44c65f895c6fe2172792717418627db05d.
> 
> I'd like code review for this patch and mentorship to shepherd it into a
> release if possible.

Thanks for the patch! If possible could you submit it to our code review
system:

https://wiki.documentfoundation.org/Development/gerrit/setup
https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch

If you need help, you can contact me via email.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152094] The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

--- Comment #5 from Mike Kaganski  ---
@Caolan: likely, this is related to bug 103322 comment 49?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 144195] UI: PNG export dialog has radio button doesn't allow 'dimensions' or 'DPI' to be set both

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144195

--- Comment #21 from Frasier Crane  ---
That's not true - I always get the wrong file size unless I set the dimensions
to "Pixels"!

E.g. in "Draw", I create a page 30 x 20 cm landscape and place some high-res
photos on it.

When I export this page as JPG, I can select "Modify dimensions" (default 30 x
20 cm) or "Modify resolution" (default 96 dpi).

When I select the first choice, I get an image file with the dimensions 1134 x
756 pixels. Seems to be correct for 96 dpi.

When I select the second option and set it to 300 dpi, I also get an image file
with 1134 x 756 pixels, which is totally wrong of course!

The "width and height" of the image should always stay 30 x 20 cm, even if I
change the dpi, so that I can get a high-resolution output file!

When exporting JPG (and other files that are aware of dimension AND dpi), it
must be possible to specify BOTH, dimension AND dpi and not one OR the other!

A work-around is to set the dimension to 3543 x 2362 pixels - which corresponds
to an image of 30 x 20 cm with 300 dpi. This produces a correct high-res file.
However, Draw should handle that correctly (and professionally), of course, so
that I can define my output file to be 30 x 20 cm with 300 dpi...

Anyone who has ever worked with image file formats that are size and dpi aware
knows that it's not one or the other, but both that define a correct image.
It's an absolute basic feature of these file formats and I can hardly believe
that a program called "Draw" does not handle this correctly... especially when
this bug has been reported more than a year ago already...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||1586

--- Comment #2 from Mike Kaganski  ---
"the cursor is at the first character in the file and not at the last cursor
position" is the direct consequence of the slowdown, and is bug 141586.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141586

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||2098

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141586

Mike Kaganski  changed:

   What|Removed |Added

 CC||john.h...@yahoo.co.uk

--- Comment #6 from Mike Kaganski  ---
*** Bug 152097 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152097] Writer document does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152097

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Mike Kaganski  ---


*** This bug has been marked as a duplicate of bug 141586 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152100] "Windows Share" item needs a notice that it is only shown on non-Windows systems

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152100

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||9812

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152100] New: "Windows Share" item needs a notice that it is only shown on non-Windows systems

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152100

Bug ID: 152100
   Summary: "Windows Share" item needs a notice that it is only
shown on non-Windows systems
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com
CC: olivier.hal...@libreoffice.org

In bug 119812, Windows Share item was removed from File Services dialog on
Windows. This needs to be reflected in help:

https://help.libreoffice.org/latest/en-US/text/shared/guide/cmis-remote-files-setup.html

This creates confusion in users:

https://ask.libreoffice.org/t/windows-share-is-missing-in-remote-files-in-type-under-file-services/84213

Additionally, this should mention that on Windows, these shares are accessed
using normal OS file dialogs, without Remote Files feature.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152099] New: EDITING: Libre Office Base could use a autocomplete feature in SQL view.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152099

Bug ID: 152099
   Summary: EDITING: Libre Office Base could use a autocomplete
feature in SQL view.
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stasmalinow...@proton.me

Description:
Hi,
I'd like to suggest a feature to be added to Base that would autocomplete hSQL
commands after pressing the TAB key. I would be great even if it didn't
understand context. Maybe just autocompleting commands by default, and table or
column names if what we started writing starts with ". It would make working
with Base so much easier.

Actual Results:
.

Expected Results:
.


Reproducible: Always


User Profile Reset: No

Additional Info:
.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 119745] Scrolling with a laptop touchpad in Libreoffice way too fast

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119745

--- Comment #49 from jeyov45...@sinagalore.com ---
(In reply to Ian Hodgson from comment #36)
> Same issue with LO Writer and Calc. In Calc, scrolling up/down and
> left/right is super fast/sensitive. In Writer, scrolling up/down is good.
> But Ctrl + up/down + 2 finger scroll (zoom in/out) is too sensitive to be
> able to use in both Calc and Writer.
> 
> XPS13 9370 
> 
> Not sure what the trackpad hardware details are. I don't know which output
> entry from lspci/lsusb refers to the trackpad.
> 
> Ubuntu 20.04
> 
> LO 6.4.7.2
> 
> Ian

It seems likely that there are multiple underlying issues being tracked in this
bug report; for the one you mention (calc scroll up/left is fast, down/right is
slow), I've developed a patch; see
.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151473] Draw PDF import: ASCII brackets (e.g. (), [] etc) are reversed when the paragraph is RTL

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151473

--- Comment #5 from Kevin Suo  ---
There seems to already be a fix on the Apache OpenOffice, see the m_aMirrorMap
in PDFIProcessor::prepareMirrorMap():
http://opengrok.openoffice.org/xref/trunk/main/sdext/source/pdfimport/tree/pdfiprocessor.cxx?r=c142477c

Not sure whether it is OK to "borrow" some of its code. Is there any license
issue? At what extent shall we use it?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143209] Edge Scrolling no longer works properly on my touchpad beginning with version 6.2 and newer.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143209

--- Comment #9 from jeyov45...@sinagalore.com ---
Created attachment 183655
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183655=edit
Patch that fixes the bug. Developed against libreoffice-core commit
0eec6d44c65f895c6fe2172792717418627db05d.

I'd like code review for this patch and mentorship to shepherd it into a
release if possible.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143209] Edge Scrolling no longer works properly on my touchpad beginning with version 6.2 and newer.

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143209

--- Comment #8 from jeyov45...@sinagalore.com ---
I dug in here and figured out the problem: `lcl_HandleScrollHelper` is using
`o3tl::saturating_cast` to handle scroll deltas, which results in
positive/negative asymmetry. The asymmetry can be fixed by simply adding 0.5:

`nNewPos = o3tl::saturating_cast(fVal + 0.5);`

in `lcl_HandleScrollHelper` in `vcl/source/window/window2.cxx`.

But looking at this code, it really should be properly handling sub-cell
scrolls. I've written a patch that stores partial scroll offsets in
`WindowImpl` and uses them in `Window::HandleScrollCommand`; this cleanly fixes
this bug and improves smoothness of scrolling in general for touchpads.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 130781] Trying to create too big QR code closes program after showing error message

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=130781

--- Comment #7 from cocominikki  ---
Thanks for providing app files for free Everything You Want to Know about
http://www.shareitmod.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 145291] CALC evaluation of ad hoc labels fails when a CELL within the label array is included in the formula

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145291

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 151879] Opening a Base document a second time with macro executed after view has been created gives error message - no macro executed any more

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151879

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 152092] Libreoffice impress freezes when I try to move slides and I'm forced to quit. 'EDITING'

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152092

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152092] Libreoffice impress freezes when I try to move slides and I'm forced to quit. 'EDITING'

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152092

--- Comment #3 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 148984] Image not pasting into text document when copying from desktop

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148984

--- Comment #2 from QA Administrators  ---
Dear Linux,

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 99103] SIDEBAR: Presentation styles in Styles and Formatting dont update in Outline view

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99103

--- Comment #5 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 99085] Promoting and demoting outline bullets doesnt preserve paragraph spacing

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=99085

--- Comment #5 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 91902] Increase and decrease indent buttons not accessible in textbox edit mode

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91902

--- Comment #7 from QA Administrators  ---
Dear Yousuf Philips (jay) (retired),

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 86174] logic error with mod() and int() function

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86174

--- Comment #5 from QA Administrators  ---
Dear Brian Prasse,

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 76143] Many missing / wrong paper sizes in the Print Preview

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76143

--- Comment #13 from QA Administrators  ---
Dear A (Andy),

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 58511] EDITING: Cut fontwork object does not work

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58511

--- Comment #12 from QA Administrators  ---
Dear Rainer Bielefeld Retired,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 65746] FILESAVE: Excel 2003 XML formulas are not preserved

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65746

--- Comment #11 from QA Administrators  ---
Dear Sawradym,

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 138265] incorrect message for undefined ODBC DSN

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138265

--- Comment #2 from QA Administrators  ---
Dear Terrence Enger,

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 138263] Checkbox for Draw's View - Shift menu item does not uncheck

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138263

--- Comment #2 from QA Administrators  ---
Dear Buovjaga,

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 138189] UI: Undocked resized table toolbar doesn't retain dimensions. Resets itself to a bar after close

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138189

--- Comment #4 from QA Administrators  ---
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 136252] Can't assign Alt+- to function

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136252

--- Comment #2 from QA Administrators  ---
Dear Dan Dascalescu,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 113882] Report editor's Sorting and Grouping is not always updated after a Data Content change

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113882

--- Comment #4 from QA Administrators  ---
Dear Howard Johnson,

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 113867] The scroll bar isn't moving & pages keeps scrolling after releasing the page down button

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113867

--- Comment #8 from QA Administrators  ---
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the left side any more..

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

Aron Budea  changed:

   What|Removed |Added

 CC||momonas...@gmail.com
   Keywords||bibisected, bisected

--- Comment #8 from Aron Budea  ---
(In reply to Cor Nouws from comment #4)
> On the same computer, versions prior to 
> Version: 6.2.0.0.alpha1+
> Build ID: b8e260a9372de9ee1186e1f78ade29717e9b8026
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; 
> TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
> 2018-10-29_17:17:42
> Locale: en-US (en_US.UTF-8); Calc: threaded
> do not have the issue.
> 
> So it is not solely a Wayland issue, IMO.
Well, I checked with commit preceding that in the 6.2 bibisect repo, and the
bug still occurs, so there are versions prior that that still have the bug.

This is the commit that introduced the bug in 6.1, bibisected using repo
bibisect-linux-64-6.1:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=e223e70f5d92e2ed027fc5d449bd790a123acdc2
author  Maxim Monastirsky 2018-06-11
02:08:54 +0300
committer   Maxim Monastirsky 2018-06-26
12:00:11 +0200

"tdf#117175 wayland: Make popup windows not show off-screen"

...which is the backport of three commits from 6.2:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=0da89ede1fee3a9079b7b41ee8b34504ddeb5ee5
https://cgit.freedesktop.org/libreoffice/core/commit/?id=2bfc4cefc21ab18e9ff7cc5fdc743bcc856d103c
https://cgit.freedesktop.org/libreoffice/core/commit/?id=eb84dcb9c0a202f4917169acdce50775778b72ec

Interestingly, in the 6.2 Linux bibisect repo the result is the following
commit, which is obviously wrong, as it's dealing with IWYU stuff:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=f4dafe050abe42a36ed56576c23539eb808db5ba

Maxim, in your opinion, is this a regression, or originates from a general
problem with Wayland?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151708] Unsaved documents are no longer recovered

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151708

--- Comment #11 from Matt  ---
(In reply to Robert Großkopf from comment #10)
> You saved one file before killing the process. Did you changed content after
> you have saved something in the file? Is this new content also available in
> the recovered document?
--
RESPONSE:
Changed information in "saved file" is also lost.  
--
> 
> Have tested this and no new content was available here.
> 
> What did you choose in Tools → Options → Load/Save → General → Save
> AutoRecovery Information every: … minutes?
> Have set this to 2 minutes, waited 3 minutes after changing content or
> created a new unsaved document with new content.
> All unsaved content is there, also the content of the unsaved document.
> 
--
RESPONSE:
Did not change AutoRecovery minutes from default.  Is set at 10 minutes,
however  default is not activated.  Activated, retested, no change.  Still
receiving original problem results.  

Using default settings, problem did not previously exist.
--

> Tested with 
> Version: 7.4.3.1 / LibreOffice Community
> Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
> CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
> Locale: de-DE (de_DE.UTF-8); UI: en-US
> Calc: threaded
> 
> So I can't confirm a buggy behavior here.

--
RESPONSE:
The screenshots that I provided prove buggy behavior.  These results were with
a clean install of: 
Version 7.4.2.3 (Current Release)
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
Windows 10 current version
--

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152098] Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

JohnHa  changed:

   What|Removed |Added

 CC||john.h...@yahoo.co.uk

--- Comment #1 from JohnHa  ---
Created attachment 183654
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183654=edit
Large file with 2,500 A4 pages of text

Large file with 2,500 pages of A4 default text.

My User data was
Forename: John
Surname: Ha
Initials: JH

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152098] New: Large Writer document 15x slower to open in 7.3.7.2 and does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152098

Bug ID: 152098
   Summary: Large Writer document 15x slower to open in 7.3.7.2
and does not open at last cursor position
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: john.h...@yahoo.co.uk

Description:
A large document (six copies of Vanity Fair, 2,500 A4 pages, 1.8 million words,
just plain default text - no images, tables, footnotes etc) takes about 120
seconds to open in 7.3.7.2.  It opened in about 8 seconds in 7.0.6.2. 

When it does finally open the cursor is at the first character in the file and
not at the last cursor position.

Steps to Reproduce:
1.  Download attached Vanity Fair - six copies.odt.
2.  Open with 7.3.7.2 and make an edit towards the end.  This places your
information as editor and should allow to document to open at the cursor
position.
3.  Note the cursor position.
4.  Save file.
5.  Open file.


Actual Results:
1.  It takes about 120 seconds before the blue circle stops spinning and I can
type, scroll etc.

2.  The file opens with the cursor at the beginning.

Expected Results:
1.  The file should open in about 8 seconds and allow me to type, scroll etc as
it did in 7.0.6.2.

2.  The file should open with the cursor at the position at which YOU last
saved it as it did in 7.0.6.2.



Reproducible: Always


User Profile Reset: Yes

Additional Info:
1.  See also Bug 152097 - Writer document does not open at last cursor position
where much smaller document opens with cursor at random positions.

2.  This appears to be a regression - all worked OK with 7.0.6.2.

3.  I had User Data in Tools > Options ..., which is necessary for LO to open
the file at the last cursor position.

4.  Resetting the profile (delete...\user, then add back User Data) had no
effect.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the left side any more..

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

Aron Budea  changed:

   What|Removed |Added

 Status|NEW |UNCONFIRMED
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152097] Writer document does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152097

JohnHa  changed:

   What|Removed |Added

 CC||john.h...@yahoo.co.uk

--- Comment #2 from JohnHa  ---
Created attachment 183653
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183653=edit
A test file to test the location where Writer opens the document

I attach fred.odt which I am using for testing.

The behaviour is quite random and the document opens with the cursor at
different positions on each opening.  Some of the locations of the cursor are
repeated on different openings but none are where the cursor was located when
the document was saved.

I reset the profile and added back the User Data.  The random behaviour
continued.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103182

Aron Budea  changed:

   What|Removed |Added

 Depends on||152088


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152088
[Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the
left side any more..
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103030

Aron Budea  changed:

   What|Removed |Added

 Depends on||152088


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152088
[Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the
left side any more..
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100156

Aron Budea  changed:

   What|Removed |Added

 Depends on||152088


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152088
[Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the
left side any more..
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the left side any more..

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

Aron Budea  changed:

   What|Removed |Added

 Blocks||103182, 103030, 100156
 CC||aron.bu...@gmail.com
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Hardware|x86-64 (AMD64)  |All


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=100156
[Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103030
[Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103182
[Bug 103182] [META] GTK3-specific bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152097] Writer document does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152097

--- Comment #1 from JohnHa  ---
Not reproduceable.  Possibly caused by a lock file being present when tested.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/inc sw/source

2022-11-17 Thread Tomaž Vajngerl (via logerrit)
 sw/inc/OnlineAccessibilityCheck.hxx |2 ++
 sw/source/core/access/AccessibilityCheck.cxx|   12 +++-
 sw/source/core/inc/AccessibilityCheck.hxx   |1 +
 sw/source/core/txtnode/OnlineAccessibilityCheck.cxx |   11 +++
 4 files changed, 25 insertions(+), 1 deletion(-)

New commits:
commit 45d1fca81991f0d6837c98d6be6fe0d21d566fa5
Author: Tomaž Vajngerl 
AuthorDate: Mon Oct 31 11:09:46 2022 +0100
Commit: Tomaž Vajngerl 
CommitDate: Fri Nov 18 02:06:13 2022 +0100

sw: run document properties a11y checks on a loaded document

Change-Id: Iba98a91a61955af52651348409f88244d1eed2c1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142216
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/sw/inc/OnlineAccessibilityCheck.hxx 
b/sw/inc/OnlineAccessibilityCheck.hxx
index fe4652949d64..3d68a71f11db 100644
--- a/sw/inc/OnlineAccessibilityCheck.hxx
+++ b/sw/inc/OnlineAccessibilityCheck.hxx
@@ -53,6 +53,7 @@ private:
 sal_Int32 m_nAccessibilityIssues;
 bool m_bInitialCheck;
 bool m_bOnlineCheckStatus;
+std::unique_ptr 
m_pDocumentAccessibilityIssues;
 
 void runAccessibilityCheck(SwNode* pNode);
 void updateStatusbar();
@@ -60,6 +61,7 @@ private:
 void initialCheck();
 void lookForPreviousNodeAndUpdate(SwPosition const& rNewPos);
 void clearAccessibilityIssuesFromAllNodes();
+void runDocumentLevelAccessibilityCheck();
 
 public:
 OnlineAccessibilityCheck(SwDoc& rDocument);
diff --git a/sw/source/core/access/AccessibilityCheck.cxx 
b/sw/source/core/access/AccessibilityCheck.cxx
index 802dda2b95cd..ac558a44c69e 100644
--- a/sw/source/core/access/AccessibilityCheck.cxx
+++ b/sw/source/core/access/AccessibilityCheck.cxx
@@ -1411,7 +1411,7 @@ void AccessibilityCheck::checkNode(SwNode* pNode)
 }
 }
 
-void AccessibilityCheck::check()
+void AccessibilityCheck::checkDocumentProperties()
 {
 if (m_pDoc == nullptr)
 return;
@@ -1424,6 +1424,16 @@ void AccessibilityCheck::check()
 if (pDocumentCheck)
 pDocumentCheck->check(m_pDoc);
 }
+}
+
+void AccessibilityCheck::check()
+{
+if (m_pDoc == nullptr)
+return;
+
+init();
+
+checkDocumentProperties();
 
 auto const& pNodes = m_pDoc->GetNodes();
 SwNode* pNode = nullptr;
diff --git a/sw/source/core/inc/AccessibilityCheck.hxx 
b/sw/source/core/inc/AccessibilityCheck.hxx
index 1ff4cf5b16f7..c7613e8829a4 100644
--- a/sw/source/core/inc/AccessibilityCheck.hxx
+++ b/sw/source/core/inc/AccessibilityCheck.hxx
@@ -51,6 +51,7 @@ public:
 void check() override;
 void checkObject(SdrObject* pObject);
 void checkNode(SwNode* pNode);
+void checkDocumentProperties();
 };
 
 } // end sw namespace
diff --git a/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx 
b/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
index db1212600644..1188bc7d06c5 100644
--- a/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
+++ b/sw/source/core/txtnode/OnlineAccessibilityCheck.cxx
@@ -135,11 +135,22 @@ void 
OnlineAccessibilityCheck::runAccessibilityCheck(SwNode* pNode)
 = std::make_unique(aCollection);
 }
 
+void OnlineAccessibilityCheck::runDocumentLevelAccessibilityCheck()
+{
+m_aAccessibilityCheck.getIssueCollection().clear();
+m_aAccessibilityCheck.checkDocumentProperties();
+auto aCollection = m_aAccessibilityCheck.getIssueCollection();
+m_pDocumentAccessibilityIssues
+= std::make_unique(aCollection);
+}
+
 void OnlineAccessibilityCheck::initialCheck()
 {
 if (m_bInitialCheck)
 return;
 
+runDocumentLevelAccessibilityCheck();
+
 auto const& pNodes = m_rDocument.GetNodes();
 for (SwNodeOffset n(0); n < pNodes.Count(); ++n)
 {


[Libreoffice-commits] core.git: include/sfx2 officecfg/registry svx/sdi sw/inc sw/sdi sw/source sw/uiconfig

2022-11-17 Thread Tomaž Vajngerl (via logerrit)
 include/sfx2/sfxsids.hrc |   14 +--
 officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu |   14 +++
 svx/sdi/svx.sdi  |   18 

 sw/inc/OnlineAccessibilityCheck.hxx  |5 -
 sw/inc/node.hxx  |1 
 sw/sdi/_viewsh.sdi   |   11 ++
 sw/source/core/txtnode/OnlineAccessibilityCheck.cxx  |   42 
+-
 sw/source/uibase/uiview/view0.cxx|   24 
+
 sw/uiconfig/sglobal/menubar/menubar.xml  |1 
 sw/uiconfig/swriter/menubar/menubar.xml  |1 
 10 files changed, 119 insertions(+), 12 deletions(-)

New commits:
commit 00128f14c400b661444676410b2088aca357291c
Author: Tomaž Vajngerl 
AuthorDate: Fri Oct 28 22:11:59 2022 +0200
Commit: Tomaž Vajngerl 
CommitDate: Fri Nov 18 02:05:55 2022 +0100

sw: add a menu option to enable/disable online a11y check

Change-Id: I656037ef4e40e7c79daef5dd73f8f10c9818ac25
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142215
Tested-by: Tomaž Vajngerl 
Reviewed-by: Tomaž Vajngerl 

diff --git a/include/sfx2/sfxsids.hrc b/include/sfx2/sfxsids.hrc
index 8333ce792d9d..eb729e873fd2 100644
--- a/include/sfx2/sfxsids.hrc
+++ b/include/sfx2/sfxsids.hrc
@@ -459,15 +459,15 @@ class SvxZoomItem;
 #define SID_PASTE_ONLY_FORMULA  (SID_SFX_START + 803)
 #define SID_PASTE_ONLY_VALUE(SID_SFX_START + 804)
 #define SID_PASTE_TEXTIMPORT_DIALOG (SID_SFX_START + 805)
-#define SID_PASTE_TRANSPOSED(SID_SFX_START + 812)
-#define SID_PASTE_AS_LINK   (SID_SFX_START + 813)
+#define SID_PASTE_TRANSPOSED(SID_SFX_START + 808)
+#define SID_PASTE_AS_LINK   (SID_SFX_START + 809)
 
 // Used for redaction
-#define SID_SHAPE_NAME  (SID_SFX_START + 808)
-// FREE: SID_SFX_START + 809
-#define SID_GRAPHIC_SIZE_CHECK  (SID_SFX_START + 809)
-#define SID_ACCESSIBILITY_CHECK (SID_SFX_START + 810)
-#define SID_ASYNCHRON   (SID_SFX_START + 811)
+#define SID_SHAPE_NAME  (SID_SFX_START + 810)
+#define SID_GRAPHIC_SIZE_CHECK  (SID_SFX_START + 811)
+#define SID_ACCESSIBILITY_CHECK (SID_SFX_START + 812)
+#define SID_ASYNCHRON   (SID_SFX_START + 813)
+#define SID_ACCESSIBILITY_CHECK_ONLINE  (SID_SFX_START + 814)
 
 // default-ids for configuration
 #define SID_CONFIG  (SID_SFX_START + 904)
diff --git 
a/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu 
b/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu
index 20817a9b4239..c355eb776ad3 100644
--- a/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu
+++ b/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu
@@ -5020,6 +5020,20 @@ bit 3 (0x8): #define 
UICOMMANDDESCRIPTION_PROPERTIES_TOGGLEBUTTON 8
   9
 
   
+  
+
+  Automatic Accessibility Checking
+
+
+  Automatic A~ccessibility Checking
+
+
+  Toggle Automatic Accessibility 
Checking
+
+
+  1
+
+  
   
 
   Do Not Mark Errors
diff --git a/svx/sdi/svx.sdi b/svx/sdi/svx.sdi
index 0be42759ae94..d4e4f62450b6 100644
--- a/svx/sdi/svx.sdi
+++ b/svx/sdi/svx.sdi
@@ -12546,6 +12546,24 @@ SfxVoidItem AccessibilityCheck SID_ACCESSIBILITY_CHECK
 GroupId = SfxGroupId::Modify;
 ]
 
+SfxBoolItem AccessibilityCheckOnline SID_ACCESSIBILITY_CHECK_ONLINE
+(SfxBoolItem Enable FN_PARAM_1)
+[
+AutoUpdate = TRUE,
+FastCall = FALSE,
+ReadOnlyDoc = TRUE,
+Toggle = TRUE,
+Container = FALSE,
+RecordAbsolute = FALSE,
+RecordPerSet;
+
+
+AccelConfig = TRUE,
+MenuConfig = TRUE,
+ToolBoxConfig = TRUE,
+GroupId = SfxGroupId::Options;
+]
+
 XColorItem GlowColor SID_ATTR_GLOW_COLOR
 
 [
diff --git a/sw/inc/OnlineAccessibilityCheck.hxx 
b/sw/inc/OnlineAccessibilityCheck.hxx
index 7a37f05cc432..fe4652949d64 100644
--- a/sw/inc/OnlineAccessibilityCheck.hxx
+++ b/sw/inc/OnlineAccessibilityCheck.hxx
@@ -52,15 +52,18 @@ private:
 SwNodeOffset m_nPreviousNodeIndex;
 sal_Int32 m_nAccessibilityIssues;
 bool m_bInitialCheck;
+bool m_bOnlineCheckStatus;
 
 void runAccessibilityCheck(SwNode* pNode);
 void updateStatusbar();
 void updateNodeStatus(SwNode* pContentNode);
 void initialCheck();
+void lookForPreviousNodeAndUpdate(SwPosition const& rNewPos);
+void clearAccessibilityIssuesFromAllNodes();
 
 public:
 OnlineAccessibilityCheck(SwDoc& rDocument);
-void update(const SwPosition& rNewPos);
+void 

[Libreoffice-bugs] [Bug 152097] New: Writer document does not open at last cursor position

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152097

Bug ID: 152097
   Summary: Writer document does not open at last cursor position
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: john.h...@yahoo.co.uk

Description:
If a user has inserted User Data in Tools > Options then any document they open
should open at the position at which the cursor was located when the document
was closed.  

The document opens at the very top with the cursor at the first character.

This is a regression - it worked as expected in 7.0.6.2.

Steps to Reproduce:
1.  Insert Surname, Forename and Initials text in Tools > Options > LibreOffice
> User Data.
2.  Open fred.odt which has a few pages of text.  
3.  Make a small edit on the last page.  Do not move cursor - leave it at the
edit.
4.  Save fred.odt
5.  Open fred.odt

Actual Results:
Document opens with cursor at top of document

Expected Results:
Document should open at the last cursor position on the last page.


Reproducible: Always


User Profile Reset: No

Additional Info:
This is a regression - it worked as expected in 7.0.6.2.

I then installed 7.3.7.2 which used the profile from 7.0.6.2 so it is not a
profile problem

Other users are experiencing it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152096] Impress export to png reverses colors

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152096

Regina Henschel  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||rb.hensc...@t-online.de

--- Comment #1 from Regina Henschel  ---
I cannot confirm it. Tested with Version: 7.5.0.0.alpha0+ (X86_64) /
LibreOffice Community
Build ID: 17dfc9a9da009cc23de3fb4e2cef9c97d581
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL threaded

Do you have the problem with every presentation or only with a specific
presentation. If latter, please attach the presentation.

Do you use odp file format or do you use pptx?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||miguelangelrv@libreoffice.o
   ||rg
 Ever confirmed|0   |1

--- Comment #4 from m.a.riosv  ---
Please can you test disabling 'Skia', Menu/Tools/LibreOffice/View

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152091] Addition of several groups of contiguous cells gives "#Value!"

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152091

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #2 from m.a.riosv  ---
Or introducing it as an array, you get two cells result. The first summing
A1+A5+A9 and second one A2+A6+A10.

For me not a bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143909] Cannot use unicode keyboard shortcut in comments

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143909

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #9 from Regina Henschel  ---
It does not only fail in comments but in text boxes and shapes in Writer too.
And fails in Calc too. It works in frames in Writer.

It fails in comments in Draw/Impress, but works in text boxes and shapes in
Draw/Impress.

tested with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 17dfc9a9da009cc23de3fb4e2cef9c97d581
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152096] New: Impress export to png reverses colors

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152096

Bug ID: 152096
   Summary: Impress export to png reverses colors
   Product: LibreOffice
   Version: 7.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: elka...@q.com

Description:
In LibreOffice Impress, going to File->Export and then choosing the file
extension to be png results in an image with color reversal, i.e., that is the
negative of the actual colors on the Impress file.  White becomes black, etc. 
This does not happen when exporting to a jpg.

Actual Results:
Create a LibreOffice Impress file.  Go to File -> Export and when the file
explorer pop-up window appears, choose the file extension to be png using the
drop-down.  

Expected Results:
The saved png file will be the negative, color-wise, of the original Impress
file.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.2.2.2 (x64) / LibreOffice Community
Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 85428] Imported PDF displays extra-long lines for shaded area

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85428

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com
 Status|NEW |NEEDINFO

--- Comment #8 from Rajasekaran Karunanithi  ---
(In reply to Robinson Tryon (qubit) from comment #0)
> Importing PDF version of UW campus map into Draw results in shaded areas to
> render lines too long.
> 
> Original: https://www.washington.edu/static/media/campus-and-vicinity.pdf
> 
> Affected parts of the map are the "Construction Area" regions, both on the
> map and in the map's legend.
> 
> Tested with LO 4.3.2.2 and 4.4.0.0.alpha1 on Ubuntu 14.04.
> 
> Map displays correctly in Firefox 33.0 and Evince 3.10.3.

Couldn't find the pdf version of UW Campus file right now.Can you send any
other samples to test for this bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152095] Enhancement request : adding 'Data - Refresh all ranges' command

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152095

--- Comment #1 from Stephane Santon  ---
I forgot before step #3 to reproduce :
- Define named range on every sheet

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152095] New: Enhancement request : adding 'Data - Refresh all ranges' command

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152095

Bug ID: 152095
   Summary: Enhancement request : adding 'Data - Refresh all
ranges' command
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m.libreoff...@santonum.eu

Description:
The 'Data - Refresh range' can refresh only the data range that includes the
active cell. 
One new command is needed to refresh all the workbook data ranges.

Steps to Reproduce:
1. You fill a table in Sheet1 A1:J30
2. You mirror data by the "{=$Sheet1.A1:J30}" array formula in multiple sheets
Sheet2, Sheet3, Sheet4
3. You define an automatic filter on every mirroring sheet Sheet2, Sheet3,
Sheet4
4. You modify a cell data in Sheet1
5. You want to refresh all the filtered sheets


Actual Results:
You have to activate one sheet after another and execute the "Data - Refresh
range" as many times as the sheets count.

Expected Results:
Use only the "Data - Refresh all ranges" or "Data - Refresh all workbook
ranges" manu command.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.1.2 (x64) / LibreOffice Community
Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0
CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152091] Addition of several groups of contiguous cells gives "#Value!"

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152091

--- Comment #1 from LeroyG  ---
I think that it is not a bug.

You must opt for =SUM(A1:A2;A5:A6;A9:A10) (or not usually with
=SUM(A1:A2~A4:A5~A7:A8))

=A1:A2;A5:A6;A9:A10 will give Err:509 Operator missing.

Just try in B1 with =A1:A2 and you will get only the A1 value. And with the
same formula in B2 you will get only the A2 value.

Tested with:
Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (en_US.UTF-8); UI: en-US
Calc: threaded

(In reply to Julien Nabet from comment #0)
> 1. Retrieve attachment

Attachment is missing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the left side any more..

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

--- Comment #7 from LeroyG  ---
Created attachment 183652
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183652=edit
Blank left after dragging the Navigator toolbar

With F5 the Navigator appear at the left side.

Ctrl+Shft+F10 does nothing. I can't make it to float by dragging.

If docked to the top/right/bottom by dragging, in the left side there remains a
blank space (see screenshot). Pressing F5 twice, the Navigator reappear at the
left side.

Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (en_US.UTF-8); UI: en-US
Calc: threaded
Supplied by SUSE.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152089] Page Style Paragraph Area color renders inconsistently while scrolling. Sometime it's shown sometimes not

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152089

Telesto  changed:

   What|Removed |Added

Summary|Page Style Paragraph Area   |Page Style Paragraph Area
   |is being rendered   |color renders
   |inconsistently while|inconsistently while
   |scrolling. Sometime it's|scrolling. Sometime it's
   |shown sometimes not |shown sometimes not

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152094] The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

--- Comment #4 from LeroyG  ---
Similar issue with:
Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (en_US.UTF-8); UI: en-US
Calc: threaded

The screen is 1152x864.

I tested with the fifth and with the fourth Lorem.
The effect is reset if the text is scrolled out (to left or right) and in
again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151846] LibreOffice 7.4 missing several imports in com.sun.star.chart2 namespace

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151846

--- Comment #4 from vibrationofl...@pm.me ---
(In reply to Noel Grandin from comment #3)
> What is your code doing with InterpretedData that it needs to import it?

I am not useing InterpretedData specifically. I am using XChartTypeTemplate.

These other three I discovered using my OOO UNO TEMPLATE projects that also
allows my test to discover missing interfaces and other imports.

https://github.com/Amourspirit/ooo_uno_tmpl/tree/main/tests/test_imports_dyn

- XTransformation
- XDataInterpreter
- InterpretedData


XChartTypeTemplate is critical to my chart2 module (works fine on 7.3x).
https://github.com/Amourspirit/python_ooo_dev_tools/blob/main/ooodev/office/chart2.py

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152046] Incorrect document layout

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152046

--- Comment #6 from LeroyG  ---
Not present in 7.3.7.2 on Windows 10.0.

nor in
Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (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 152094] The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

Telesto  changed:

   What|Removed |Added

 CC||caol...@redhat.com

--- Comment #3 from Telesto  ---
@Caolan
I should probably drop the topic: likely again bug 61444. However I'm not
underling a word partially...

There are 2 effects: 
A) activating underline causes a shift across to board.
B) There is a shifting of glyphs in a number of area's.   

Both can be seen in the screencast

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #3 from fml2  ---
Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 61444] Text layout broken across formatting changes (color, underline, etc.)

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61444

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=52
   ||028

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152094] The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

--- Comment #2 from Telesto  ---
Created attachment 183651
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183651=edit
Screencast

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152094] The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

--- Comment #1 from Telesto  ---
Created attachment 183650
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183650=edit
Example file

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152094] New: The whole sentence is moving once after file opening when applying formatting and wiggling characters

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152094

Bug ID: 152094
   Summary: The whole sentence is moving once after file opening
when applying formatting and wiggling characters
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
The whole sentence is moving once after file opening when applying formatting
and wiggling characters

Steps to Reproduce:
1. Open the attached file
2. Zoom 490% at 1920x1080 96 dpi screen
3. Scroll horizontal so the first L is at the left corner of the screen
4. Select the fifth 'Lorem' (reading LTR) and press CTRL+U
5. Press CTRL+Z/ CTRL+Y

Note: the first lorem has no formatting. the other lorems have character DF
set. This does matter

Actual Results:
1) Initially a shift across the full line of text
2) CTRL+Z CTRL+Y shows a wiggling EM at the selected LOREM and a moving m at
the next lorem

Expected Results:
Possibly stable results?


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a81e957f5026373f3935390c786c21416fc74fcc
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sc/Module_sc.mk

2022-11-17 Thread Xisco Fauli (via logerrit)
 sc/Module_sc.mk |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 0eec6d44c65f895c6fe2172792717418627db05d
Author: Xisco Fauli 
AuthorDate: Thu Nov 17 20:33:38 2022 +0100
Commit: Xisco Fauli 
CommitDate: Thu Nov 17 21:59:56 2022 +0100

sc: move CppunitTest_sc_parallelism to check

like the other classes inheriting from ScSimpleBootstrapFixture

Change-Id: Ia067bd506274f8526e6567c3f6dc395dd87c480c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142899
Tested-by: Jenkins
Reviewed-by: Xisco Fauli 

diff --git a/sc/Module_sc.mk b/sc/Module_sc.mk
index a87a84f4502a..c297527239ab 100644
--- a/sc/Module_sc.mk
+++ b/sc/Module_sc.mk
@@ -41,6 +41,7 @@ ifneq ($(OS),iOS)
 ifneq ($(filter SCRIPTING,$(BUILD_TYPE)),)
 $(eval $(call gb_Module_add_check_targets,sc,\
Library_scqahelper \
+   CppunitTest_sc_parallelism \
$(if $(and $(filter $(COM),MSC),$(MERGELIBS)),, \
CppunitTest_sc_ucalc) \
CppunitTest_sc_ucalc_condformat \
@@ -202,7 +203,6 @@ $(eval $(call gb_Module_add_subsequentcheck_targets,sc,\
CppunitTest_sc_namedrangesobj \
CppunitTest_sc_opencl_test \
CppunitTest_sc_outlineobj \
-   CppunitTest_sc_parallelism \
CppunitTest_sc_recentfunctionsobj \
CppunitTest_sc_recordchanges \
CppunitTest_sc_scenariosobj \


[Libreoffice-bugs] [Bug 152088] [UI] Navigator (F5, View > Navigator) can not be docked at the left side any more..

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152088

--- Comment #6 from Jean-Baptiste Faure  ---
No problem with Xorg gnome session.

Best regards. JBF

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152093] Blurred lines in dropdown menu for a chart

2022-11-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152093

--- Comment #2 from fml2  ---
Created attachment 183649
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183649=edit
Magnified blurring (400%)

-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   4   >