[Bug 158532] Toolbar buttons remain greyed out after pasting an image and quickly clicking out of it

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158532

--- Comment #2 from Miklos Vajna  ---
Yes, I can reproduce the problem. The intent of the above commit to improve
things for the case when you switch between two images, and this bug is about
switching between the image and the text SfxShell, so there is hope it can be
arranged to restore the old behavior for this bug but keep the old use-case
working.

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

[Bug 158791] New: Styles deck: actually hide hidden leaf styles in Hierarchical view

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158791

Bug ID: 158791
   Summary: Styles deck: actually hide hidden leaf styles in
Hierarchical view
   Product: LibreOffice
   Version: 7.6.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ka...@goodtimes.fi

Description:
All hidden styles were made visible in the hierarchical Styles deck view in
response to bug 119919. This was a mistake.

I agree that it made no sense to detach derivative styles of hidden styles from
the hierarchy and continue to display them. But the solution should have been
to either (1) hide the entire subtree when a parent style is hidden or (2) only
do the greyed-out thing when the style has children but hide the style
completely when it’s a leaf.

At this point, solution 2 would be the obvious incremental fix.

For motivation, just consider list styles. There are no fewer than 40 default
list styles inheriting from “List”. For reasons I do not understand, they
cannot be deleted. Worse, not even their names can be changed, yet the default
names are not semantic. “List 1”, “List 2”, etc. mean nothing. So the user must
either assign them meaning mentally or create custom styles and ignore the
defaults. But ignoring them is hard since they greatly outnumber any custom
list styles in a typical template. It’s not a great situation.


Steps to Reproduce:
1. In the Styles deck, hide a style that has no child styles.


Actual Results:
The style continues to be visible in the "Hierarchical" view.

Expected Results:
The style is actually hidden unless the "Hidden Styles" view is selected. This
used to be the case before.


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

core.git: Branch 'libreoffice-7-6' - sw/qa writerfilter/source

2023-12-19 Thread Justin Luth (via logerrit) 
 sw/qa/extras/rtfexport/data/tdf158586_pageBreak0B.rtf |   15 +++
 sw/qa/extras/rtfexport/rtfexport8.cxx |6 ++
 writerfilter/source/rtftok/rtfdocumentimpl.cxx|2 ++
 3 files changed, 23 insertions(+)

New commits:
commit 9d1438cd46ab947d1e6276cefa29444dace09f8a
Author: Justin Luth 
AuthorDate: Wed Dec 13 20:07:20 2023 -0500
Commit: Miklos Vajna 
CommitDate: Wed Dec 20 08:29:41 2023 +0100

partial revert tdf#153178 writerfilter: do not create text frame spuriously

If HoriAnchor/VertAnchor are assigned, that is enough to create a frame.

make CppunitTest_sw_rtfexport8 CPPUNIT_TEST_NAME=testTdf158586_0B

Note: because of a regression, this was already one page before
this commit, so need to go back to the time of the reverted patch.

Change-Id: Iddbe1cc4ba6d6e95e2d977a227ae6cab5271007e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160743
Reviewed-by: Justin Luth 
Tested-by: Jenkins
Reviewed-by: Miklos Vajna 
Signed-off-by: Xisco Fauli 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160981
Signed-off-by: Xisco Fauli 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160999

diff --git a/sw/qa/extras/rtfexport/data/tdf158586_pageBreak0B.rtf 
b/sw/qa/extras/rtfexport/data/tdf158586_pageBreak0B.rtf
new file mode 100644
index ..587e90500505
--- /dev/null
+++ b/sw/qa/extras/rtfexport/data/tdf158586_pageBreak0B.rtf
@@ -0,0 +1,15 @@
+{
tf1
+
+\paperw8419\paperh5953
+
+\spltpgpar
+
+\ltrpar \sectd
+
+\pard\plain \phpg\pvpg
+
+\page \sect \sectd \sbknone
+
+\pard\plain First page
+\par
+}
diff --git a/sw/qa/extras/rtfexport/rtfexport8.cxx 
b/sw/qa/extras/rtfexport/rtfexport8.cxx
index 80309ff9b65e..bcba0a9beb97 100644
--- a/sw/qa/extras/rtfexport/rtfexport8.cxx
+++ b/sw/qa/extras/rtfexport/rtfexport8.cxx
@@ -56,6 +56,12 @@ DECLARE_RTFEXPORT_TEST(testTdf158586_0, 
"tdf158586_pageBreak0.rtf")
 // assertXPathContent(pLayout, "//page[1]/body/txt"_ostr, "First page");}
 }
 
+DECLARE_RTFEXPORT_TEST(testTdf158586_0B, "tdf158586_pageBreak0B.rtf")
+{
+// The specified page break must be lost because it is in a text frame
+CPPUNIT_ASSERT_EQUAL(1, getPages());
+}
+
 DECLARE_RTFEXPORT_TEST(testTdf158586_1, "tdf158586_pageBreak1.rtf")
 {
 // None of the specified text frame settings initiates a real text frame - 
page break not lost
diff --git a/writerfilter/source/rtftok/rtfdocumentimpl.cxx 
b/writerfilter/source/rtftok/rtfdocumentimpl.cxx
index 36f71beded73..089016934a0d 100644
--- a/writerfilter/source/rtftok/rtfdocumentimpl.cxx
+++ b/writerfilter/source/rtftok/rtfdocumentimpl.cxx
@@ -4010,6 +4010,8 @@ bool RTFFrame::hasProperties() const
 {
 // tdf#153178 \dxfrtext \dfrmtxtx \dfrmtxty \wrapdefault do *not* create 
frame
 return m_nX != 0 || m_nY != 0 || m_nW != 0 || m_nH != 0
+   || (m_nHoriAnchor && m_nHoriAnchor != 
NS_ooxml::LN_Value_doc_ST_HAnchor_text)
+   || (m_nVertAnchor && m_nVertAnchor != 
NS_ooxml::LN_Value_doc_ST_VAnchor_margin)
|| (m_oWrap && *m_oWrap != NS_ooxml::LN_Value_doc_ST_Wrap_auto);
 }

core.git: sw/qa

2023-12-19 Thread Miklos Vajna (via logerrit) 
 sw/qa/extras/rtfexport/rtfexport.cxx |7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

New commits:
commit ea1a05e43e002444d224fa47e87fc79f921ae10b
Author: Miklos Vajna 
AuthorDate: Tue Dec 19 20:02:07 2023 +0100
Commit: Miklos Vajna 
CommitDate: Wed Dec 20 08:28:36 2023 +0100

CppunitTest_sw_rtfexport: avoid SwModelTestBase::getLength()

Better to check the body text, not just the length.

Change-Id: Id98cc408772c5d2c135bdd184d58a5eb12f1c011
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161005
Tested-by: Jenkins
Reviewed-by: Miklos Vajna 

diff --git a/sw/qa/extras/rtfexport/rtfexport.cxx 
b/sw/qa/extras/rtfexport/rtfexport.cxx
index bbb09090500e..629b32d73acd 100644
--- a/sw/qa/extras/rtfexport/rtfexport.cxx
+++ b/sw/qa/extras/rtfexport/rtfexport.cxx
@@ -55,7 +55,10 @@ DECLARE_RTFEXPORT_TEST(testZoom, "zoom.rtf")
 CPPUNIT_ASSERT_EQUAL(sal_Int16(42), nValue);
 }
 
-DECLARE_RTFEXPORT_TEST(testFdo38176, "fdo38176.rtf") { CPPUNIT_ASSERT_EQUAL(9, 
getLength()); }
+DECLARE_RTFEXPORT_TEST(testFdo38176, "fdo38176.rtf")
+{
+CPPUNIT_ASSERT_EQUAL(u"foo ‑­bar"_ustr, getBodyText());
+}
 
 DECLARE_RTFEXPORT_TEST(testFdo49683, "fdo49683.rtf")
 {
@@ -484,7 +487,7 @@ DECLARE_RTFEXPORT_TEST(testFdo61507, "fdo61507.rtf")
 CPPUNIT_ASSERT_EQUAL(u"\u00C9\u00C1\u0150\u0170\u222D"_ustr, 
xDocumentProperties->getTitle());
 
 // Only "Hello.", no additional characters.
-CPPUNIT_ASSERT_EQUAL(6, getLength());
+CPPUNIT_ASSERT_EQUAL(OUString("Hello."), getBodyText());
 }
 
 DECLARE_RTFEXPORT_TEST(testFdo30983, "fdo30983.rtf")

core.git: Branch 'libreoffice-24-2' - desktop/source external/onlineupdate Repository.mk

2023-12-19 Thread Stephan Bergmann (via logerrit) 
 Repository.mk  |1 
 desktop/source/app/updater.cxx |   26 ++-
 external/onlineupdate/Executable_update_service.mk |2 
 external/onlineupdate/Module_onlineupdate.mk   |1 
 external/onlineupdate/Package_updater_ini.mk   |   16 ++
 external/onlineupdate/README.md|9 +
 external/onlineupdate/lo.patch |  151 ++---
 external/onlineupdate/updater.ini  |   12 +
 8 files changed, 189 insertions(+), 29 deletions(-)

New commits:
commit d125fc2a2178b100253ea089b7ad30acafccfb57
Author: Stephan Bergmann 
AuthorDate: Tue Dec 19 16:50:42 2023 +0100
Commit: Stephan Bergmann 
CommitDate: Wed Dec 20 08:09:06 2023 +0100

Improve --enable-online-update-mar Windows MOZ_MAINTENANCE_SERVICE feature

To get the MOZ_MAINTENANCE_SERVICE mode going at all, update.status needs to
contain a "pending-service" token.  For Mozilla, code in its
toolkit/mozapps/update/UpdateService.sys.mjs takes care of writing that.  
For
us, lets always write that in update_checker() (even on Linux, where it's
apparently harmless).

Then, the MOZ_MAINTENANCE_SERVICE code is rather picky with its various 
sanity
checks:  Among other things, it expects argv[0] to be a full path to the 
updater
executable, and it expects the update.mar (and its status and log files) to 
be
in a directory hierarchy named updates/0/ rather than patch/.  So get all 
that
fixed in desktop/source/app/updater.cxx.  And patch in
external/onlineupdate/lo.patch where it expects to find the updater 
executable
(just updater.exe vs. our program/updater.exe).

And we shouldn't interfere with the upstream Mozilla maintenance service, so
also rename that in external/onlineupdate/lo.patch.

And `update_service install` wants to read version resources from the
update_service.exe, so provide that (via 
gb_Executable_add_default_nativeres).

Also, `update_service install` wants to read a MozillaMaintenanceDescription
value from an updater.ini, so provide one (with contents of that value 
inspired
by Mozilla's browser/locales/en-US/updater/updater.ini).

As we now have an updater.ini anyway (and which apparently works fine with 
Unix
line ends on both Linux and Windows), also use it on Linux and drop the
onlineupdate/source/update/updater/progressui_gtk.cpp again from
external/onlineupdate/lo.patch.  And update external/onlineupdate/README.md 
how
to manually execute that test against an updater.ini.

Change-Id: I0e3e5e5311be61e1224cda700af2e5d751113a99
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160996
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 
(cherry picked from commit 290f8f908dc8178c8bc34a8bf909246f591a13aa)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161014

diff --git a/Repository.mk b/Repository.mk
index b9cf9c2ddb9c..9ef08e814a20 100644
--- a/Repository.mk
+++ b/Repository.mk
@@ -1096,6 +1096,7 @@ $(eval $(call 
gb_Helper_register_packages_for_install,brand,\
readlicense_oo_files \
readlicense_oo_license \
$(call gb_Helper_optional,DESKTOP,setup_native_packinfo) \
+   $(if $(ENABLE_ONLINE_UPDATE_MAR),updater_ini) \
 ))
 
 ifeq ($(USING_X11), TRUE)
diff --git a/desktop/source/app/updater.cxx b/desktop/source/app/updater.cxx
index 925b6b7116a4..3221d688a47f 100644
--- a/desktop/source/app/updater.cxx
+++ b/desktop/source/app/updater.cxx
@@ -32,6 +32,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 
@@ -173,17 +174,14 @@ void createStr(const OUString& rStr, CharT** pArgs, 
size_t i)
 pArgs[i] = pStr;
 }
 
-CharT** createCommandLine(int * argc)
+CharT** createCommandLine(OUString const & argv0, int * argc)
 {
 OUString aInstallDir = Updater::getInstallationPath();
 
 size_t nCommandLineArgs = rtl_getAppCommandArgCount();
 size_t nArgs = 8 + nCommandLineArgs;
 CharT** pArgs = new CharT*[nArgs];
-{
-OUString aUpdaterName = OUString::fromUtf8(pUpdaterName);
-createStr(aUpdaterName, pArgs, 0);
-}
+createStr(argv0, pArgs, 0);
 {
 // directory with the patch log
 OUString aPatchDir = Updater::getPatchDirURL();
@@ -307,7 +305,7 @@ bool update()
 
 Updater::log("Calling the updater with parameters: ");
 int argc;
-CharT** pArgs = createCommandLine();
+CharT** pArgs = createCommandLine(aUpdaterPath, );
 
 bool bSuccess = true;
 const char* pUpdaterTestReplace = std::getenv("LIBO_UPDATER_TEST_REPLACE");
@@ -676,9 +674,11 @@ void download_file(const OUString& rURL, size_t nFileSize, 
const OUString& rHash
 throw invalid_hash(rHash, aHash);
 }
 
-OUString aPatchDirURL("${$BRAND_BASE_DIR/" LIBO_ETC_FOLDER "/" 
SAL_CONFIGFILE("bootstrap") ":UserInstallation}/patch/");
+OUString aPatchDirURL("${$BRAND_BASE_DIR/"

[Bug 108591] xdg-open path is hardcoded

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=108591

--- Comment #11 from bobbie78  ---
Create a symbolic link at /usr/bin/xdg-open pointing to its actual location.
This maintains LibreOffice's expected path while allowing xdg-open to reside
elsewhere.
You can start playing any game right away in https://unblockedgames-76.io
browser. There are no downloads required.

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

[Bug 158114] Make it easier to find (and deal with) broken linked image

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158114

--- Comment #12 from Jim Raykowski  ---
Created attachment 191527
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191527=edit
demo of icon to indicate image entry has broken link

I didn't find an icon in the icon themes that specifically indicates a broken
file link. I did find the cancel red X icon.

The Treeview class could be made to draw entry text using italics (slant) font
similar to what is done for emphasis, or entry custom rendering could be done.
While this is doable, maybe the icon is enough for now?

The Images context menu Edit... menu item opens the Image dialog where in the 
Rotation tab the link file can be edited. Maybe it would be better to be in the
Options tab?

Gerrit link to patch that does what is shown in the attachment:
https://gerrit.libreoffice.org/c/core/+/161045

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 158114] Make it easier to find (and deal with) broken linked image

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158114

--- Comment #12 from Jim Raykowski  ---
Created attachment 191527
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191527=edit
demo of icon to indicate image entry has broken link

I didn't find an icon in the icon themes that specifically indicates a broken
file link. I did find the cancel red X icon.

The Treeview class could be made to draw entry text using italics (slant) font
similar to what is done for emphasis, or entry custom rendering could be done.
While this is doable, maybe the icon is enough for now?

The Images context menu Edit... menu item opens the Image dialog where in the 
Rotation tab the link file can be edited. Maybe it would be better to be in the
Options tab?

Gerrit link to patch that does what is shown in the attachment:
https://gerrit.libreoffice.org/c/core/+/161045

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

[Bug 154864] Changing starting number of numbered list does nothing

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=154864

--- Comment #13 from Commit Notification 
 ---
Noel Grandin committed a patch related to this issue.
It has been pushed to "libreoffice-24-2":

https://git.libreoffice.org/core/commit/d595b4436320fcd3ce0a84968d16d51f512a1e87

tdf#154864 Changing starting number of numbered list does nothing

It will be available in 24.2.0.0.beta2.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

[Bug 154864] Changing starting number of numbered list does nothing

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=154864

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:24.8.0   |target:24.8.0
   ||target:24.2.0.0.beta2

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

core.git: Branch 'libreoffice-24-2' - sw/qa sw/source

2023-12-19 Thread Noel Grandin (via logerrit) 
 sw/qa/uitest/writer_tests7/tdf144439.py |   22 
 sw/source/core/doc/number.cxx   |   35 +---
 2 files changed, 37 insertions(+), 20 deletions(-)

New commits:
commit d595b4436320fcd3ce0a84968d16d51f512a1e87
Author: Noel Grandin 
AuthorDate: Tue Dec 19 11:40:24 2023 +0200
Commit: Noel Grandin 
CommitDate: Wed Dec 20 07:19:10 2023 +0100

tdf#154864 Changing starting number of numbered list does nothing

regression from
commit cd3c16fbcb4f8e5e4c4448bc7cda96e8476d6aec
Author: Noel Grandin 
Date:   Fri Oct 14 15:14:13 2022 +0200
tdf#129101 CTRL+A & Cut very slow
avoid repeated invalidation of number tree, shaves 90% time off

The problem is that, after the above change, InvalidateListTree is not
called late enough to force invalidation of all necessary stuff.

So simply delay that until we do re-validation in SwNumRule::Validate.

Change-Id: I796cc34fe7d66d4876ee06286a8af7029a759eca
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160974
Tested-by: Jenkins
Reviewed-by: Noel Grandin 
(cherry picked from commit 62afdd6f82c51cee330b278518622eaf1776e2c4)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161011

diff --git a/sw/qa/uitest/writer_tests7/tdf144439.py 
b/sw/qa/uitest/writer_tests7/tdf144439.py
index 34911ee4c542..4d0ce465d5ac 100644
--- a/sw/qa/uitest/writer_tests7/tdf144439.py
+++ b/sw/qa/uitest/writer_tests7/tdf144439.py
@@ -40,6 +40,28 @@ class tdf144439(UITestCase):
 self.assertEqual(Para1.String, "List item")
 self.assertEqual(Para1.getPropertyValue("ListLabelString"), "1.1.")
 
+# this section is checking tdf#154864 - Changing starting number 
of numbered list does nothing
+#
+
+with 
self.ui_test.execute_dialog_through_command(".uno:BulletsAndNumberingDialog") 
as xDialog:
+# Select custom tab
+xTabs = xDialog.getChild("tabcontrol")
+select_pos(xTabs, "5")
+
+# Select numbering
+xNumFmt = xDialog.getChild("numfmtlb")
+select_by_text(xNumFmt, "1, 2, 3, ...")
+
+# Increase "start at"
+xStartAt = xDialog.getChild("startat")
+xStartAt.executeAction("UP", tuple())
+xStartAt.executeAction("UP", tuple())
+
+Paragraphs = document.Text.createEnumeration()
+Para1 = Paragraphs.nextElement()
+self.assertEqual(Para1.String, "List item")
+self.assertEqual(Para1.getPropertyValue("ListLabelString"), "1.3.")
+
 def test_tdf144439_outline(self):
 with self.ui_test.create_doc_in_start_center("writer") as document:
 xWriterDoc = self.xUITest.getTopFocusWindow()
diff --git a/sw/source/core/doc/number.cxx b/sw/source/core/doc/number.cxx
index d2cb98924e0f..9cef97ddc2fe 100644
--- a/sw/source/core/doc/number.cxx
+++ b/sw/source/core/doc/number.cxx
@@ -153,10 +153,17 @@ void SwNumRule::RemoveTextNode( SwTextNode& rTextNode )
 {
 tTextNodeList::iterator aIter =
 std::find( maTextNodeList.begin(), maTextNodeList.end(),  );
+if ( aIter == maTextNodeList.end() )
+return;
 
-if ( aIter != maTextNodeList.end() )
+maTextNodeList.erase( aIter );
+
+// Just in case we remove a node after we have marked the rule invalid, 
but before we have validated the tree
+if (mbInvalidRuleFlag)
 {
-maTextNodeList.erase( aIter );
+SwList* pList = 
rTextNode.GetDoc().getIDocumentListsAccess().getListByName( 
rTextNode.GetListId() );
+if (pList)
+pList->InvalidateListTree();
 }
 }
 
@@ -1051,23 +1058,6 @@ void SwNumRule::SetInvalidRule(bool bFlag)
 if (mbInvalidRuleFlag == bFlag)
 return;
 
-if (bFlag)
-{
-o3tl::sorted_vector< SwList* > aLists;
-for ( const SwTextNode* pTextNode : maTextNodeList )
-{
-// #i111681# - applying patch from cmc
-SwList* pList = 
pTextNode->GetDoc().getIDocumentListsAccess().getListByName( 
pTextNode->GetListId() );
-OSL_ENSURE( pList, " - list at 
which the text node is registered at does not exist. This is a serious issue.");
-if ( pList )
-{
-aLists.insert( pList );
-}
-}
-for ( auto aList : aLists )
-aList->InvalidateListTree();
-}
-
 mbInvalidRuleFlag = bFlag;
 }
 
@@ -1168,8 +1158,13 @@ void SwNumRule::Validate(const SwDoc& rDoc)
 o3tl::sorted_vector< SwList* > aLists;
 for ( const SwTextNode* pTextNode : maTextNodeList )
 {
-aLists.insert( 
pTextNode->GetDoc().getIDocumentListsAccess().getListByName( 
pTextNode->GetListId() ) );
+SwList* pList = 
pTextNode->GetDoc().getIDocumentListsAccess().getListByName( 
pTextNode->GetListId() );
+aLists.insert( pList );
 }
+
+

[Bug 158790] New: unable to open ods files in Google Drive on andriod devices due to MIME type

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158790

Bug ID: 158790
   Summary: unable to open ods files in Google Drive on andriod
devices due to MIME type
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rob...@vrec.ca

Unable to open ods files created in LibreOffice on Andriod device using Google
Drive.

Files created in Collabora (or LibreOffice Viewer) on an Andriod device have a
mime type of:
"Application/vnd.oasis.opendocument.spreadsheet type"
These files stored in Google Drive and can be opened from the mobile apps.

However, if the files it opened in LibreOffice Desktop from Google Drive and
saved, the mimetype gets changed to:
"Application/x-vnd.oasis.opendocument.spreadsheet type"
(the additioin of the "x-")

These files can NOT be opened from the mobile apps.

So it appears the problem is with LiberOffice Desktop or Google Drive. But not
sure how to fix it.

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

[Bug 158753] Chart wizard jumps back to chart type selection when window closes and opens

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158753

--- Comment #2 from rrosn...@gmail.com ---
Your screenshot doesn't show up, but it's the third screen of the wizard.

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

[Bug 158738] It goes out of control when using autocomplete.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158738

--- Comment #2 from ta...@globe.ocn.ne.jp ---
Thank you for your reply.

Actually, I have not been able to reproduce this issue after sending the bug
report earlier. It’s strange because the auto-complete feature used to crash
once every few times.

When the issue occurs again, I will try the safe mode you suggested.

I thought that the many DDE functions embedded in the sheet I am creating to
automatically download real-time stock prices from RSS data might have caused
such a malfunction, but since the issue has not occurred again, I am satisfied
for now.

Thank you very much.

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

[Bug 158789] Allow SUMIF and SUBTOTAL to apply to arrays

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158789

--- Comment #1 from ady  ---
Several points.

In addition to this tdf#158789, you also filed tdf#158788, apparently trying to
solve some issue with how to arrive to some result.

Please understand that most of us are volunteers here. This site is for
reporting bugs and enhancement requests, not a support forum. You could go to
 for that, for instance.

Now, as for the result you seem to be trying to obtain, I am about to post one
possible alternative. This is not a complete solution, and most probably not
even an efficient formula; it is just a way to show you that instead of asking
for changing a function here you could just go to some forum and ask for help
in finding the result you want.

So, here is one way (of several) to obtain an array formula with what you need
(as far as you presented it in comment 0):

 =SUM({-10;10;20;30}*({-10;10;20;30}>0))

to be introduced not with [Enter] but with [Ctrl]+[Shift]+[Enter] (CSE).

For further help with your formula, or better alternatives (they surely are
available out there), I'm going to respectfully and politely ask you to please
use a more adequate site, leaving this for actual bug reports and enhancements
requests. IMO, this is neither. Others might not agree.

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

[Bug 146315] [META] Show/Hide Whitespace bugs and enhancements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=146315
Bug 146315 depends on bug 100252, which changed state.

Bug 100252 Summary: UI - Hidden whitespace line looks a little ugly at the 
outer parts
https://bugs.documentfoundation.org/show_bug.cgi?id=100252

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

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

[Bug 100252] UI - Hidden whitespace line looks a little ugly at the outer parts

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=100252

Dieter  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

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

[Bug 158372] Impress: When importing pictures via drag and drop, orientation changes

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158372

--- Comment #6 from Carla Aranaga  ---
I confirm that the portrait files .jpg open in the incorrect orientation form
when drag and drop.

Right click and 'Original size' does not fix the file orientation.

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcbc0857bf4bc24b5ea36e445a367cce0a382da4
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

core.git: include/tools tools/qa tools/source

2023-12-19 Thread Caolán McNamara (via logerrit) 
 include/tools/bigint.hxx |5 
 tools/qa/cppunit/test_bigint.cxx |   14 ++
 tools/source/generic/bigint.cxx  |  210 ++-
 3 files changed, 117 insertions(+), 112 deletions(-)

New commits:
commit b64f23b235d6fd7c9f6197da0f5f0432fede4294
Author: Caolán McNamara 
AuthorDate: Mon Dec 18 20:49:13 2023 +
Commit: Mike Kaganski 
CommitDate: Wed Dec 20 05:49:41 2023 +0100

ofz#65165 Stack-buffer-overflow READ 4 test case

make VALGRIND=memcheck CppunitTest_tools_test

 Conditional jump or move depends on uninitialised value(s)
at 0x13348ADA: BigInt::DivLong(BigInt const&, BigInt&, BigInt*) const 
(bigint.cxx:306)
by 0x13349A0A: BigInt::operator/=(BigInt const&) (bigint.cxx:635)
by 0x12A58F67: tools::BigIntTest::testLenB1() (test_bigint.cxx:103)
by 0x12A5C6A8: void std::__invoke_impl(std::__invoke_memfun_deref, 
void (tools::BigIntTest::*&)(), tools::BigIntTest*&) (invoke.h:74)

if ( (static_cast(aTmpB.nNum[nLenB1 - 1]) * nQ) >
 ^ nLenB1 is 0
((nTmp - static_cast(aTmpB.nNum[nLenB1]) * nQ) << 32) + 
aTmpA.nNum[j - 2])

Since:

commit bcbc0857bf4bc24b5ea36e445a367cce0a382da4
Date:   Sun Dec 17 21:11:31 2023 +0300

Simplify BigInt

Co-authored-by: Mike Kaganski 
Change-Id: Id8dbff23f7b4312ba666e1443c41b7869713bfbc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160953
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/include/tools/bigint.hxx b/include/tools/bigint.hxx
index a880f81c748b..1a5a2284324a 100644
--- a/include/tools/bigint.hxx
+++ b/include/tools/bigint.hxx
@@ -42,13 +42,12 @@ private:
 
 TOOLS_DLLPRIVATE BigInt MakeBig() const;
 TOOLS_DLLPRIVATE void Normalize();
-TOOLS_DLLPRIVATE static BigInt Mult(BigInt const &, sal_uInt32);
-TOOLS_DLLPRIVATE void Div(sal_uInt32, sal_uInt32 &);
 TOOLS_DLLPRIVATE bool ABS_IsLessLong(BigInt const &) const;
 TOOLS_DLLPRIVATE void AddLong(BigInt &, BigInt &);
 TOOLS_DLLPRIVATE void SubLong(BigInt &, BigInt &);
 TOOLS_DLLPRIVATE void MultLong(BigInt const &, BigInt &) const;
-TOOLS_DLLPRIVATE void DivLong(BigInt const &, BigInt &, BigInt * = 
nullptr) const;
+TOOLS_DLLPRIVATE void DivModLong(BigInt const &, BigInt &, bool) const;
+TOOLS_DLLPRIVATE void DivMod(BigInt const &, bool);
 TOOLS_DLLPRIVATE bool ABS_IsLess(BigInt const &) const;
 
 public:
diff --git a/tools/qa/cppunit/test_bigint.cxx b/tools/qa/cppunit/test_bigint.cxx
index 3c7740fb7651..9a958836bb5e 100644
--- a/tools/qa/cppunit/test_bigint.cxx
+++ b/tools/qa/cppunit/test_bigint.cxx
@@ -30,9 +30,11 @@ class BigIntTest : public CppUnit::TestFixture
 {
 public:
 void testConstructionFromLongLong();
+void testLenB1();
 
 CPPUNIT_TEST_SUITE(BigIntTest);
 CPPUNIT_TEST(testConstructionFromLongLong);
+CPPUNIT_TEST(testLenB1);
 CPPUNIT_TEST_SUITE_END();
 };
 
@@ -91,6 +93,18 @@ void BigIntTest::testConstructionFromLongLong()
 }
 }
 
+void BigIntTest::testLenB1()
+{
+BigInt dy(2634022912);
+sal_Int64 md(-4177526784);
+sal_Int64 mn(2634022912);
+dy *= md;
+dy -= (mn - 1) / 2;
+dy /= mn;
+
+CPPUNIT_ASSERT_EQUAL(sal_Int64(-4177526784), sal_Int64(dy));
+}
+
 CPPUNIT_TEST_SUITE_REGISTRATION(BigIntTest);
 }
 
diff --git a/tools/source/generic/bigint.cxx b/tools/source/generic/bigint.cxx
index eaeb563bd615..8d8afd0c3f64 100644
--- a/tools/source/generic/bigint.cxx
+++ b/tools/source/generic/bigint.cxx
@@ -17,13 +17,15 @@
  *   the License at http://www.apache.org/licenses/LICENSE-2.0 .
  */
 
-#include 
+#include 
 
 #include 
 #include 
 
 #include 
-#include 
+#include 
+#include 
+#include 
 
 /**
  * The range in which we can perform add/sub without fear of overflow
@@ -89,45 +91,47 @@ void BigInt::Normalize()
 }
 }
 
-BigInt BigInt::Mult( const BigInt , sal_uInt32 nMul )
+// Normalization in DivLong requires that dividend is multiplied by a number, 
and the resulting
+// value has 1 more 32-bit "digits". 'ret' provides enough room for that. Use 
of std::span gives
+// run-time index checking in debug builds.
+static std::span Mult(std::span aNum, sal_uInt32 
nMul, std::span retBuf)
 {
-assert(!rVal.IsLong());
-BigInt ret;
+assert(aNum.size() <= MAX_DIGITS);
+assert(retBuf.size() >= aNum.size());
 sal_uInt64 nK = 0;
-for ( int i = 0; i < rVal.nLen; i++ )
+for (size_t i = 0; i < aNum.size(); i++)
 {
-sal_uInt64 nTmp = static_cast(rVal.nNum[i]) * nMul + nK;
+sal_uInt64 nTmp = static_cast(aNum[i]) * nMul + nK;
 nK = nTmp >> 32;
-ret.nNum[i] = static_cast(nTmp);
+retBuf[i] = static_cast(nTmp);
 }
 
 if ( nK )
 {
-assert(rVal.nLen < MAX_DIGITS);
-ret.nNum[rVal.nLen] = nK;
-ret.nLen = rVal.nLen + 1;
+assert(retBuf.size() > aNum.size());
+retBuf[aNum.size()] = nK;
+

[Bug 158785] Hyperlink is help-popup/Ctrl-Click are active one character past the end of the hyperlink

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158785

--- Comment #2 from Justin L  ---
proposed fix at https://gerrit.libreoffice.org/c/core/+/161042

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

[Bug 158650] Scrolling is lagging/freezing everywhere

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158650

--- Comment #12 from Sam Ragucci  ---
Switching to Skia/Metal fixed the issue for me (LibreOffice 7.5.9.2 on an iMac
with MacOS 13.6.3) in Calc and Writer, which is great.

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

core.git: sw/source

2023-12-19 Thread Justin Luth (via logerrit) 
 sw/source/core/layout/layact.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 7e32aec38ed386a01c522bbb5cf0e80dd924a815
Author: Justin Luth 
AuthorDate: Tue Dec 19 14:18:55 2023 -0500
Commit: Justin Luth 
CommitDate: Wed Dec 20 04:24:38 2023 +0100

related tdf#111969 fix smart tags job not being fired, due to typo

This fixes quikee's 7.5 regression
commit 01396925b76011ffccb6eea40956a22d58de6f17

If this is a help document, we don't want to run smart tags,
not the other way around.

It was correct originally - assuming this was just
a typo when the tests were pulled out into a function.

Change-Id: Ie21ed256539ce242a7892c1ddc1556319fc45310
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161006
Tested-by: Jenkins
Reviewed-by: Justin Luth 

diff --git a/sw/source/core/layout/layact.cxx b/sw/source/core/layout/layact.cxx
index 84481981fd6e..747470129c96 100644
--- a/sw/source/core/layout/layact.cxx
+++ b/sw/source/core/layout/layact.cxx
@@ -2185,7 +2185,7 @@ bool SwLayIdle::isJobEnabled(IdleJobType eJob, const 
SwViewShell* pViewShell)
 case IdleJobType::SMART_TAGS:
 {
 const SwDoc* pDoc = pViewShell->GetDoc();
-if (!pDoc->GetDocShell()->IsHelpDocument() || pDoc->isXForms() || 
!SwSmartTagMgr::Get().IsSmartTagsEnabled())
+if (pDoc->GetDocShell()->IsHelpDocument() || pDoc->isXForms() || 
!SwSmartTagMgr::Get().IsSmartTagsEnabled())
 return false;
 return true;
 }

[Bug 158520] Writer: Index-tagged headings not considered headings cross-reference-wise

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158520

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Bug 158511] LibreOffice Writer: make it possible to export Custom Properties to PDF

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158511

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Bug 158547] FILEOPEN PPTX Master handout with disabled header/footer/date/page number placeholder

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158547

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158553] FILEOPEN PPTX Page size not applied to Notes/Master Notes/Master Handouts

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158553

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158545] UI: Original size button in image properties -> position and size tab doesn't restore original size for paper size exceeding images in Writer (and breaks image ratio)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158545

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158543] Lots of CPU time used when moving a table left/right or up/down with arrow keys (or when dragging) but no lag

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158543

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158542] FILEOPEN PPTX Handout / Notes (master) page orientation not read

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158542

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158539] Memory usage increases with steps of +/-100 MB on each save and reload after simply image modification (macOS)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158539

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 155957] Recent Special Char Wrong

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=155957

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

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

[Bug 155435] Duplicating sheet containing COUNTIF references to ranges in external files damages formula

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=155435

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

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

[Bug 155957] Recent Special Char Wrong

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=155957

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.

[Bug 155435] Duplicating sheet containing COUNTIF references to ranges in external files damages formula

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=155435

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

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 156004] Crash if i open help menu and click on the checking for update options

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=156004

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

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.

[Bug 155964] Errors while FORMATTING multiple cells

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=155964

--- Comment #3 from QA Administrators  ---
Dear Luciano,

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.

[Bug 72364] PDF import fails on Unix on CIFS mounts (windows shares)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=72364

--- Comment #14 from QA Administrators  ---
Dear Lionel Elie Mamane,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 53290] [Find and replace] Backreference is not evaluated if word boundary is present in search string

2023-12-19 Thread bugzilla-daemon

[Bug 47479] LibO Calc Macro .getCellRangeByName with named range

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=47479

--- Comment #10 from QA Administrators  ---
Dear Kossem,

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.

[Bug 145895] VIEWING: Opening a certain document with "Show Whitespace" deselected shows page break

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=145895

--- Comment #3 from QA Administrators  ---
Dear LeroyG,

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.

[Bug 139376] Chapter numbering broken after clear paragraph formatting followed by undo

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=139376

--- 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.

[Bug 138949] Collabora LO VANILLA - ODB file open fails to create a connection to a mysql instance over the mysql native connector

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=138949

--- Comment #9 from QA Administrators  ---
Dear Alex Thurgood,

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.

[Bug 131138] Cannot export a master document to EPUB.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=131138

--- Comment #9 from QA Administrators  ---
Dear Thomas Leigh,

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.

[Bug 129420] Decrease performance when select many aleatory cells with Ctrl pressed.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=129420

--- Comment #18 from QA Administrators  ---
Dear Yerinier Ferrás,

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.

[Bug 123986] Split Table disabled when in table cell crossing page boundary

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=123986

--- Comment #7 from QA Administrators  ---
Dear DM,

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.

[Bug 123633] Web view and hide whitespace causes view position to jitter until entire document is reformatted

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=123633

--- Comment #15 from QA Administrators  ---
Dear matt,

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.

[Bug 127054] Whitespace is not Hidden if Column Breaks are Used

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=127054

--- Comment #3 from QA Administrators  ---
Dear Harald Koester,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 126868] Deselecting "Show Whitespace" changes document content / formatting

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=126868

--- Comment #5 from QA Administrators  ---
Dear DarkTrick,

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.

[Bug 118456] In Whitespace Mode Deleting a Page Break Leaves a Grey Line

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=118456

--- Comment #5 from QA Administrators  ---
Dear Harald Koester,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 123184] FILESAVE XLSX, Changes made in Calc with change tracking turned on are not highlighted in Excel.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=123184

--- Comment #6 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 105743] Textflow changes on hiding whitespace && two columns-layout

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=105743

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

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.

[Bug 100252] UI - Hidden whitespace line looks a little ugly at the outer parts

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=100252

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

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.

[Bug 158789] New: Allow SUMIF and SUBTOTAL to apply to arrays

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158789

Bug ID: 158789
   Summary: Allow SUMIF and SUBTOTAL to apply to arrays
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jw...@jwatt.org

The following resolves to 0 rather, than resolving to 60, which it would
resolve to if a cell reference range to cells of the same values was given.

=SUMIF({-10,10,20,30},">0")

Could support for passing arrays to SUMIF and SUBTOTAL be added?

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

[Bug 158729] Cropped images change on compression

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158729

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

Crop might differ from screenshot, as crop might be based on screen resolution.
This was the case, unsure if it still a topic

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

[Bug 158729] Cropped images change on compression

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158729

--- Comment #15 from Telesto  ---
Created attachment 191525
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191525=edit
Screenshot

Top image untoched.
Second image compress PNG with reduce image resolution change checked, blurry
Third image compressed JPG, with reduce image resolution change checked. Crop
lost and skewed

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

[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5, comment 9)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158112

--- Comment #19 from libretist  ---
The bug is much easier to reproduce in Writer, see bug 158786

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

[Bug 158774] Serious slowdown in recent Libreoffice calc release

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158774

--- Comment #6 from Telesto  ---
(In reply to Andy from comment #0)
> if you navigate the cells in 7.6.4 things move way way slower, it is almost   
>   > unusable

UI render: default; VCL: win

This is should be Skia/Raster. Tools -> Options -> View. Cjeck Force Skia
Software Rendering and restart

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

[Bug 158788] Applying math formula (MAX()) to individual array elements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158788

--- Comment #1 from Jonathan Watt  ---
MAX() is presumably acting as intended, and I'm not seeing anything in the
built-in functions to support this behavior. So, unless I'm missing something,
I guess this bug report is to request something like an MAPPLY() function,
which would allow a non-array supporting function to be passed in by name
(perhaps as a string) along with an array, and would apply the function to each
array element individually.

Or alternatively a whole bunch of MMAX, MMIN, etc. functions.

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

[Bug 158788] New: Applying math formula (MAX()) to individual array elements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158788

Bug ID: 158788
   Summary: Applying math formula (MAX()) to individual array
elements
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jw...@jwatt.org

I'm trying to clamp the values in an array to some lower and upper bounds,
before doing further operations on the resulting array.

I can provide a fuller spreadsheet example as an attachment if necessary, but
the following demonstrates the issue:

=SUM(MAX({-10,10,20,30},0))

What I'd like to achieve, is for MAX() to be applied to each array element in
turn, resulting in an array with values {0,10,20,30}, with SUM() returning the
value 60.

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

[Bug 158774] Serious slowdown in recent Libreoffice calc release

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158774

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #5 from m.a.riosv  ---
Opening 21 seconds with
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcbc0857bf4bc24b5ea36e445a367cce0a382da4
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

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

[Bug 158765] Problems trying to print documents on "Folio" size paper

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158765

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

[Bug 158765] Problems trying to print documents on "Folio" size paper

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158765

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #7 from m.a.riosv  ---
Created attachment 191524
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191524=edit
Sample file

Reproducible
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded
and
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcbc0857bf4bc24b5ea36e445a367cce0a382da4
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

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

[Bug 158760] Button option for hyperlink does not work

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158760

m.a.riosv  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||miguelangelrv@libreoffice.o
   ||rg
 Resolution|--- |NOTABUG

--- Comment #1 from m.a.riosv  ---
Menu/Form/Design mode, disable it.

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

[Bug 156443] Windows: alt+numpad doesn't work for Unicode decimal codes, like in WordPad/Word

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=156443

V Stuart Foote  changed:

   What|Removed |Added

 Blocks||158112


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158112
[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5,
comment 9)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5, comment 9)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158112

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||156443


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156443
[Bug 156443] Windows: alt+numpad doesn't work for Unicode decimal codes, like
in WordPad/Word
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158112] Sidebar pane shortcuts conflict with Alt+NumPad input (comment 5, comment 9)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158112

V Stuart Foote  changed:

   What|Removed |Added

 CC||s...@wolke7.net

--- Comment #18 from V Stuart Foote  ---
*** Bug 158786 has been marked as a duplicate of this bug. ***

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

[Bug 158786] [regression] alt+number codes for unicode symbols don't work anymore after updating to LibreOffice 7.6.3.2

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158786

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||vsfo...@libreoffice.org

--- Comment #3 from V Stuart Foote  ---


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

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

[Bug 158758] Print Preview doesn't preview comments

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158758

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please attach a sample file.

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

[Bug 158755] FORMATTING: Hidden styles appear unchanged in hierarchical list (styles sidebar)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158755

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Created attachment 191523
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191523=edit
Screenshot

Looks greyed out for me.
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 158753] Chart wizard jumps back to chart type selection when window closes and opens

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158753

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

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

[Bug 158753] Chart wizard jumps back to chart type selection when window closes and opens

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158753

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Created attachment 191522
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191522=edit
Chart wizard screenshot.

Sorry, where is dataset editor?

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

[Bug 158751] Pasting text in vertically merged cells does not show the entire text

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158751

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Reproducible
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bcbc0857bf4bc24b5ea36e445a367cce0a382da4
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Seems a refresh issue.

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

[Bug 158746] Precise object positioning is a game of patience.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158746

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Have you enabled in Draw
Menu/View/Grid and Help lines/Help lines While moving.

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

[Bug 158739] Crash (assert): Inserting Formula and hovering over insert text leads to assert in Skia/Vulkan graphics (Win11)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158739

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #11 from m.a.riosv  ---
Perhaps update the graphics drivers from the vendors could help.

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

[Bug 158738] It goes out of control when using autocomplete.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158738

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please test in safe mode, Menu/Help/Restart in Safe Mode

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

[Bug 119908] FILEOPEN: DOCX: Layout differences with justified paragraph. MS 2013 introduced a new "smart justify" that can shrink as well as expand.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=119908

--- Comment #28 from László Németh  ---
Created attachment 191521
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191521=edit
composite screenshots of before (black) and after (red)

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

[Bug 158776] DOCX import: unnecessary shrinking of spaces

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158776

László Németh  changed:

   What|Removed |Added

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

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

[Bug 119908] FILEOPEN: DOCX: Layout differences with justified paragraph. MS 2013 introduced a new "smart justify" that can shrink as well as expand.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=119908

László Németh  changed:

   What|Removed |Added

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

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

[Bug 158776] DOCX import: unnecessary shrinking of spaces

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158776

--- Comment #4 from László Németh  ---
Created attachment 191520
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191520=edit
composite screenshots of before (black) and after (red)

right composite screenshot shows fixing the last line break difference using
space shrinking instead of line shrinking

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

[Bug 158787] New: Slowness of LibreOffice available on the Microsoft Store

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158787

Bug ID: 158787
   Summary: Slowness of LibreOffice available on the Microsoft
Store
   Product: LibreOffice
   Version: 7.5.9.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: leonardouger...@outlook.com

Description:
I expensively purchased LibreOffice directly from the Microsoft Store,
especially to appreciate and recognize the effort for the incredible and
powerful software that I have been using for years. However, the version
available on the Microsoft Store is unusually slow in all its modules compared
to the version downloaded directly from the website
(https://pt-br.libreoffice.org/). It is not for this reason that I will stop
using the software, but I leave my suggestion for improvement, and I hope that
The Document Foundation will do its due diligence to make the Microsoft Store
version equivalent, if not better, to the one directly available directly on
its website, previously mentioned.

Steps to Reproduce:
1. Open the application
2.
3.

Actual Results:
The problem occurs as reported in the details field.

Expected Results:
The software should work equivalently to the version available directly on the
website, or at least not show abnormal slowness, as happened.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: pt-BR (pt_BR); UI: pt-BR
Calc: threaded

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

[Bug 156956] Xterm windows all have the same name when LANG=en_US (non-UTF8 locale)

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=156956

--- Comment #8 from Duncan Roe  ---
Actually no. I did mistakenly think UTF-8 would mess up my input settings. Am
using UTF-8 now.
OK with me if you close this.

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

[Bug 158786] [regression] alt+number codes for unicode symbols don't work anymore after updating to LibreOffice 7.6.3.2

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158786

libretist  changed:

   What|Removed |Added

   Hardware|x86-64 (AMD64)  |All

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

[Bug 158786] [regression] alt+number codes for unicode symbols don't work anymore after updating to LibreOffice 7.6.3.2

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158786

libretist  changed:

   What|Removed |Added

 CC||s...@wolke7.net

--- Comment #2 from libretist  ---
Created attachment 191519
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191519=edit
screenshot of the keyboard shortcut customization window

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

[Bug 158786] [regression] alt+number codes for unicode symbols don't work anymore after updating to LibreOffice 7.6.3.2

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158786

--- Comment #1 from libretist  ---
Created attachment 191518
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191518=edit
screenshot to demonstrate the problem

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

[Bug 158786] New: [regression] alt+number codes for unicode symbols don't work anymore after updating to LibreOffice 7.6.3.2

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158786

Bug ID: 158786
   Summary: [regression] alt+number codes for unicode symbols
don't work anymore after updating to LibreOffice
7.6.3.2
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: s...@wolke7.net

Description:
In previous LibreOffice version ALT+number codes inserted unicode symbols in a
Writer text document. (For example ALT+168 inserts the "¿" symbol.)

However after updating to LibreOffice 7.6.3.2 this is broken, because the
ALT+number shortcut now opens different sidebars in Writer. For example ALT+2
opens the "style" sidebar.

Unfortunately Tools > customize > keyboard > shortcut keys cannot be used to
change this behaviour, because no ALT+number keyboard shortcuts show up for
deletion.

See images in this thread:
https://ask.libreoffice.org/t/regression-cannot-enter-alt-number-codes-for-unicode-symbols-anymore-after-updating-to-libreoffice-7-6-3-2/99658

The suggested workaround in this thread using ALT+X is too cumbersome.

Steps to Reproduce:
(on a Windows computer)
1. enter ALT+168

Actual Results:
the "properties" sidebar opens

Expected Results:
the "¿" symbol should be inserted


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.3.2 (X86_64) / LibreOffice Community
Build ID: 29d686fea9f6705b262d369fede658f824154cc0
CPU threads: 1; OS: Windows 10.0 Build 16299; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: threaded

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

[Bug 88559] Display of inherited attributes from parent styles in Styles dialog

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=88559

--- Comment #31 from Eyal Rozenberg  ---
(In reply to bintoro from comment #30)
> But IMO text
> fields are the ones that would benefit the most from granular control and
> inheritance indicators. 

I disagree. Plus, even if this were true, other fields would still benefit from
this.

> We already have a “Reset to Parent” button. On tabs
> that consist mostly of checkboxes etc., I’m happy to reset the entire tab

You may be, but others aren't... :-(

Plus, some tabs consist of textual, checkbox and other widgets.

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

[Bug 158776] DOCX import: unnecessary shrinking of spaces

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158776

--- Comment #3 from László Németh  ---
Created attachment 191517
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191517=edit
Writer PDF export

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

[Bug 158776] DOCX import: unnecessary shrinking of spaces

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158776

--- Comment #2 from László Németh  ---
Created attachment 191516
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191516=edit
MSO PDF export

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

[Bug 158714] EDITING - Crash when entering diacritics in Calc.

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158714

--- Comment #9 from tunaira...@yahoo.co.uk ---
Regarding step 2, I don't even get the chance to type the "a", it freezes
immediately when I press the acute key.

I tried on Writer and it doesn't happen, even if I type the acute in a table
cell.

In Calc, it also doesn't happen if I just select the cell, then type the acute
in the formula entry bar.

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

core.git: Branch 'libreoffice-7-6' - android/source

2023-12-19 Thread Weblate (via logerrit) 
 android/source/res/values-ast/strings.xml|  107 +
 android/source/res/values-el/strings.xml |  133 +++
 android/source/res/values-in/strings.xml |2 
 android/source/res/values-it/strings.xml |6 +
 android/source/res/values-ne/strings.xml |   29 +
 android/source/res/values-uk/strings.xml |  133 ++-
 android/source/res/values-zh-rTW/strings.xml |  133 ++-
 7 files changed, 540 insertions(+), 3 deletions(-)

New commits:
commit 532a0e1facd6bb787230a60802f15877268e7390
Author: Weblate 
AuthorDate: Tue Dec 19 09:16:23 2023 +0100
Commit: Michael Weghorn 
CommitDate: Tue Dec 19 22:52:08 2023 +0100

Added translation for android-viewer using Weblate (Indonesian)

Change-Id: I8174ba6f73fb268663932ce32e532c56e9d69ac0

android-viewer translated using Weblate

Asturian currently translated at 100.0% (130 of 130 strings)

Change-Id: I7daf63d0b55732b73040b31f3b45c34cb1f56c8e

android-viewer translated using Weblate

Nepali currently translated at 20.0% (26 of 130 strings)

Change-Id: I7e76830ae8936b8b37feff50b8b84e39219bc4cc

android-viewer translated using Weblate

Greek currently translated at 100.0% (130 of 130 strings)

Change-Id: I9de3a2139b0ab03f01fdae4d856d2ef64d832da8

android-viewer translated using Weblate

Ukrainian currently translated at 100.0% (130 of 130 strings)

Change-Id: I05c1c430f780de502fe8b44c85dca861232ad418

android-viewer translated using Weblate

Asturian currently translated at 100.0% (130 of 130 strings)

Change-Id: I73ee6013b162289d74e31b4be96cdedc7395d846

android-viewer translated using Weblate

Asturian currently translated at 100.0% (130 of 130 strings)

Change-Id: Id711497212fdc4e4bea54641305774f9b8cafb8f

android-viewer translated using Weblate

Chinese (Traditional) currently translated at 100.0% (130 of 130 strings)

Change-Id: Ic75c6c4e12a83627a99492d33c6db5fa736ba79b

android-viewer translated using Weblate

Greek currently translated at 46.9% (61 of 130 strings)

Change-Id: I8619ab89325b106c0812f51c867ccdfe668af995

android-viewer translated using Weblate

Asturian currently translated at 48.4% (63 of 130 strings)

Change-Id: Ib99da613b37f8e57e27846e246d23d40e5f84738

Added translation for android-viewer using Weblate (Nepali)

Change-Id: I5a2b46b53a4355241c8843b04fb9d911ca80a969

Added translation for android-viewer using Weblate (Greek)

Change-Id: I77d2275960986c0fe39a09af509b56153f345d4b

android-viewer translated using Weblate

Italian currently translated at 15.3% (20 of 130 strings)

Change-Id: I1b6872f9d073e69adc5be562063dfd08f1286605

android-viewer translated using Weblate

Italian currently translated at 15.3% (20 of 130 strings)

Change-Id: I0b24c9c12d7ca6ec189574fa4863d40cb9071af0

android-viewer translated using Weblate

Asturian currently translated at 29.2% (38 of 130 strings)

Change-Id: I934f4b5bae13f81f1c1c6c1cfda55e28e2851c14

android-viewer translated using Weblate

Asturian currently translated at 29.2% (38 of 130 strings)

Change-Id: I9ac61dc87aef8ea4c13fbfef53af1727986bc0f9

android-viewer translated using Weblate

Chinese (Traditional) currently translated at 100.0% (130 of 130 strings)

Change-Id: Ie15b5a8ef4d1019449308674c626a9468295fc22
Co-authored-by: Adolfo Jayme Barrientos 
Co-authored-by: Cheng-Chia Tseng 
Co-authored-by: Dimitris Spingos 
Co-authored-by: Elisabetta Manuele 
Co-authored-by: Po-Yen Huang 
Co-authored-by: Saroj Dhakal 
Co-authored-by: Weblate 
Co-authored-by: Weblate 
Co-authored-by: Xandru Martino Ruz 
Co-authored-by: ciampix 
Co-authored-by: Євген Кондратюк 
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/ast/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/el/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/it/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/ne/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/uk/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings-7-6/zh_Hant/
Translation: android-viewer/android-strings-7-6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160908
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/android/source/res/values-ast/strings.xml

[Bug 132007] Improve the password-protected document unlock prompt dialog's text strings and layout

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=132007

Amos Aidoo  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |aidooamo...@gmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

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

core.git: android/source

2023-12-19 Thread Weblate (via logerrit) 
 android/source/res/values-ast/strings.xml|   95 +
 android/source/res/values-cy/strings.xml |2 
 android/source/res/values-el/strings.xml |  121 +++
 android/source/res/values-in/strings.xml |2 
 android/source/res/values-it/strings.xml |7 +
 android/source/res/values-ne/strings.xml |   23 +
 android/source/res/values-sl/strings.xml |2 
 android/source/res/values-uk/strings.xml |  121 ++-
 android/source/res/values-zh-rTW/strings.xml |  121 ++-
 9 files changed, 490 insertions(+), 4 deletions(-)

New commits:
commit 78e72be805e9b41617d752e0da8c04b7bf5dd269
Author: Weblate 
AuthorDate: Tue Dec 19 09:16:25 2023 +0100
Commit: Michael Weghorn 
CommitDate: Tue Dec 19 22:51:13 2023 +0100

Added translation for android-viewer using Weblate (Indonesian)

Change-Id: I55e7159ff10e7bb0ee32651a8f23f2f3a4e1282c

android-viewer translated using Weblate

Asturian currently translated at 100.0% (118 of 118 strings)

Change-Id: Ica863fed7663f5f5c17820a4010262101fcc358c

android-viewer translated using Weblate

Nepali currently translated at 16.9% (20 of 118 strings)

Change-Id: Ifc64ae37b7faa5bad89f70178565595630993420

android-viewer translated using Weblate

Greek currently translated at 100.0% (118 of 118 strings)

Change-Id: Icb257e6a5cfd38de5a27425f69294e059796e596

android-viewer translated using Weblate

Ukrainian currently translated at 100.0% (118 of 118 strings)

Change-Id: Iddf1e095b789f2a324fbc614d57b98ab3df8ed0e

android-viewer translated using Weblate

Asturian currently translated at 100.0% (118 of 118 strings)

Change-Id: I318be3807e77e190d857f1d9edd25fc9d7a60c0a

android-viewer translated using Weblate

Asturian currently translated at 100.0% (118 of 118 strings)

Change-Id: If8105733d78073254da1ccd16817581d53ab55b8

android-viewer translated using Weblate

Chinese (Traditional) currently translated at 100.0% (118 of 118 strings)

Change-Id: I7ef697098031684e32aed137b2ac6bd844ed94fb

Added translation for android-viewer using Weblate (Nepali)

Change-Id: I2d68cb2696827a6cd6e2ad634873857344c8ac9f

android-viewer translated using Weblate

Greek currently translated at 57.6% (68 of 118 strings)

Change-Id: Ic029d631692c1f47a9d7eeda13ce6ac38a59c3b8

android-viewer translated using Weblate

Greek currently translated at 56.7% (67 of 118 strings)

Change-Id: Id3456928ecb1a9aab0c27e77fbe49a02540fd8c4

android-viewer translated using Weblate

Asturian currently translated at 58.4% (69 of 118 strings)

Change-Id: Ibaf90837a1f25d070f9dd8ac183fbca6c26e85c4

android-viewer translated using Weblate

Italian currently translated at 11.8% (14 of 118 strings)

Change-Id: I64eb0e5cbf5a6ab050c6ef18a1adae68317005d8

android-viewer translated using Weblate

Asturian currently translated at 32.2% (38 of 118 strings)

Change-Id: Ie470cf5f249a0e498413571cd0b56a5421f5710a

android-viewer translated using Weblate

Asturian currently translated at 32.2% (38 of 118 strings)

Change-Id: I687ae9fe76f85a03f0876f4eda55d943f51b43fb

android-viewer translated using Weblate

Slovenian currently translated at 100.0% (118 of 118 strings)

Change-Id: I0c0cc15c6d5f245311c12d05afd4742db649389d

android-viewer translated using Weblate

Chinese (Traditional) currently translated at 100.0% (118 of 118 strings)

Change-Id: I2ddc5b6a36a512e6e4d1e52c96e282b0ff05f2ea

android-viewer translated using Weblate

Welsh currently translated at 100.0% (118 of 118 strings)

Change-Id: I34dbcafeaf61e7400d07910976ff71fdbe8ae4b0

Added translation for android-viewer using Weblate (Greek)

Change-Id: Idfc6ee0a0988f3c414e6e6beee58a96ab5fb9547
Co-authored-by: Adolfo Jayme Barrientos 
Co-authored-by: Andika Triwidada 
Co-authored-by: Cheng-Chia Tseng 
Co-authored-by: Dimitris Spingos 
Co-authored-by: Elisabetta Manuele 
Co-authored-by: Martin Srebotnjak 
Co-authored-by: Po-Yen Huang 
Co-authored-by: Rhoslyn Prys 
Co-authored-by: Saroj Dhakal 
Co-authored-by: Weblate 
Co-authored-by: Weblate 
Co-authored-by: Xandru Martino Ruz 
Co-authored-by: Євген Кондратюк 
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings/ast/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings/cy/
Translate-URL: 
https://translations.documentfoundation.org/projects/android-viewer/android-strings/el/
Translate-URL:

core.git: Branch 'distro/collabora/co-23.05' - oox/source sd/qa sd/source xmloff/source

2023-12-19 Thread Balazs Varga (via logerrit) 
 oox/source/ppt/presentationfragmenthandler.cxx |7 -
 oox/source/ppt/slidepersist.cxx|6 
 sd/qa/unit/data/pptx/tdf157740.pptx|binary
 sd/qa/unit/export-tests-ooxml1.cxx |   16 +-
 sd/qa/unit/export-tests-ooxml2.cxx |   12 -
 sd/source/core/drawdoc3.cxx|   38 -
 sd/source/filter/eppt/epptbase.hxx |2 
 sd/source/filter/eppt/epptooxml.hxx|2 
 sd/source/filter/eppt/pptx-epptooxml.cxx   |  160 ++---
 sd/source/ui/inc/unopage.hxx   |1 
 sd/source/ui/unoidl/unopage.cxx|   13 +-
 xmloff/source/draw/ximpbody.cxx|   19 ++
 12 files changed, 149 insertions(+), 127 deletions(-)

New commits:
commit 397da200a5250bc23df7692354ccb4910783f61e
Author: Balazs Varga 
AuthorDate: Sun Dec 3 23:41:01 2023 +0100
Commit: Henry Castro 
CommitDate: Tue Dec 19 22:47:04 2023 +0100

tdf#157740 FILESAVE PPTX: fix explosion of the number of master slides

- Export correctly the "supported" master slides with the actual slides 
names.
- Set SlideLayout property at ODF import as well for MasterSlides layout 
type.
- When we copy a slide with the master slide also copy the SlideLayout 
property
value as well.

Change-Id: Idb6b88ebe87a83818d8eb27a1fa087652a002c0c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160290
Tested-by: Jenkins
Reviewed-by: Henry Castro 
Reviewed-by: Balazs Varga 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160985
Tested-by: Jenkins CollaboraOffice 

diff --git a/oox/source/ppt/presentationfragmenthandler.cxx 
b/oox/source/ppt/presentationfragmenthandler.cxx
index 1586a8a26174..91824210e239 100644
--- a/oox/source/ppt/presentationfragmenthandler.cxx
+++ b/oox/source/ppt/presentationfragmenthandler.cxx
@@ -212,11 +212,11 @@ void PresentationFragmentHandler::importMasterSlide(const 
ReferencegetFragmentPathFromRelation(rEntry.second);
-
 if (!rEntry.second.maType.endsWith("relationships/slideLayout"))
 continue;
 
+aLayoutFragmentPath = 
xMasterRelations->getFragmentPathFromRelation(rEntry.second);
+
 sal_Int32 nIndex;
 if( rFilter.getMasterPages().empty() )
 {
@@ -271,6 +271,9 @@ void PresentationFragmentHandler::importMasterSlide(const 
ReferencecreateBackground( rFilter );
 pMasterPersistPtr->createXShapes( rFilter );
 
+uno::Reference< beans::XPropertySet > 
xSet(pMasterPersistPtr->getPage(), uno::UNO_QUERY_THROW);
+xSet->setPropertyValue("SlideLayout", 
Any(pMasterPersistPtr->getLayoutFromValueToken()));
+
 oox::drawingml::ThemePtr pTheme = pMasterPersistPtr->getTheme();
 if (pTheme)
 {
diff --git a/oox/source/ppt/slidepersist.cxx b/oox/source/ppt/slidepersist.cxx
index 0f7479e8ede9..d31416e43f5b 100644
--- a/oox/source/ppt/slidepersist.cxx
+++ b/oox/source/ppt/slidepersist.cxx
@@ -105,6 +105,7 @@ sal_Int16 SlidePersist::getLayoutFromValueToken() const
 case XML_titleOnly: nLayout = 19; break;
 case XML_twoObj:
 case XML_twoColTx:  nLayout =  3; break;
+case XML_twoObjAndObj:
 case XML_twoObjAndTx:   nLayout = 15; break;
 case XML_twoObjOverTx:  nLayout = 16; break;
 case XML_tx:nLayout =  1; break;
@@ -112,19 +113,18 @@ sal_Int16 SlidePersist::getLayoutFromValueToken() const
 case XML_txAndClipArt:  nLayout =  6; break;
 case XML_txAndMedia:nLayout =  6; break;
 case XML_txAndObj:  nLayout = 10; break;
+case XML_objAndTwoObj:
 case XML_txAndTwoObj:   nLayout = 12; break;
 case XML_txOverObj: nLayout = 17; break;
 case XML_vertTitleAndTx:nLayout = 22; break;
 case XML_vertTitleAndTxOverChart: nLayout = 21; break;
 case XML_vertTx:nLayout = 23; break;
+case XML_objOnly:   nLayout = 32; break;
 
 case XML_twoTxTwoObj:
-case XML_twoObjAndObj:
 case XML_objTx:
 case XML_picTx:
 case XML_secHead:
-case XML_objOnly:
-case XML_objAndTwoObj:
 case XML_mediaAndTx:
 case XML_dgm:
 case XML_cust:
diff --git a/sd/qa/unit/data/pptx/tdf157740.pptx 
b/sd/qa/unit/data/pptx/tdf157740.pptx
new file mode 100644
index ..009e9eeb1da0
Binary files /dev/null and b/sd/qa/unit/data/pptx/tdf157740.pptx differ
diff --git a/sd/qa/unit/export-tests-ooxml1.cxx 
b/sd/qa/unit/export-tests-ooxml1.cxx
index 30df5ba06789..e7726d27e29e 100644
--- a/sd/qa/unit/export-tests-ooxml1.cxx
+++ b/sd/qa/unit/export-tests-ooxml1.cxx
@@ -263,14 +263,14 @@ void SdOOXMLExportTest1::testTdf149128()
 save("Impress Office Open XML");
 
 xmlDocUniquePtr pXmlDoc = parseExport("ppt/slides/slide1.xml");
-assertXPath(pXmlDoc,

core.git: Branch 'libreoffice-7-6' - oox/source sd/qa sd/source xmloff/source

2023-12-19 Thread Balazs Varga (via logerrit) 
 oox/source/ppt/slidepersist.cxx  |6 
 sd/qa/unit/data/pptx/tdf157740.pptx  |binary
 sd/qa/unit/export-tests-ooxml1.cxx   |4 
 sd/qa/unit/export-tests-ooxml2.cxx   |   20 +-
 sd/source/core/drawdoc3.cxx  |   38 +++-
 sd/source/filter/eppt/epptbase.hxx   |2 
 sd/source/filter/eppt/epptooxml.hxx  |6 
 sd/source/filter/eppt/pptx-epptooxml.cxx |  284 +++
 xmloff/source/draw/ximpbody.cxx  |   19 ++
 9 files changed, 142 insertions(+), 237 deletions(-)

New commits:
commit a4640043ed772b5dcc1ee9d36cfd8b0e4759f894
Author: Balazs Varga 
AuthorDate: Sun Dec 3 23:41:01 2023 +0100
Commit: Henry Castro 
CommitDate: Tue Dec 19 22:46:42 2023 +0100

tdf#157740 FILESAVE PPTX: fix explosion of the number of master slides

- Export correctly the "supported" master slides with the actual slides 
names.
- Set SlideLayout property at ODF import as well for MasterSlides layout 
type.
- When we copy a slide with the master slide also copy the SlideLayout 
property
value as well.

Change-Id: Idb6b88ebe87a83818d8eb27a1fa087652a002c0c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160290
Tested-by: Jenkins
Reviewed-by: Henry Castro 
Reviewed-by: Balazs Varga 
(cherry picked from commit bff76421e234df7246a7f49c71a11432f86e09d1)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160869
Reviewed-by: Xisco Fauli 
Signed-off-by: Xisco Fauli 
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160986

diff --git a/oox/source/ppt/slidepersist.cxx b/oox/source/ppt/slidepersist.cxx
index 0f7479e8ede9..d31416e43f5b 100644
--- a/oox/source/ppt/slidepersist.cxx
+++ b/oox/source/ppt/slidepersist.cxx
@@ -105,6 +105,7 @@ sal_Int16 SlidePersist::getLayoutFromValueToken() const
 case XML_titleOnly: nLayout = 19; break;
 case XML_twoObj:
 case XML_twoColTx:  nLayout =  3; break;
+case XML_twoObjAndObj:
 case XML_twoObjAndTx:   nLayout = 15; break;
 case XML_twoObjOverTx:  nLayout = 16; break;
 case XML_tx:nLayout =  1; break;
@@ -112,19 +113,18 @@ sal_Int16 SlidePersist::getLayoutFromValueToken() const
 case XML_txAndClipArt:  nLayout =  6; break;
 case XML_txAndMedia:nLayout =  6; break;
 case XML_txAndObj:  nLayout = 10; break;
+case XML_objAndTwoObj:
 case XML_txAndTwoObj:   nLayout = 12; break;
 case XML_txOverObj: nLayout = 17; break;
 case XML_vertTitleAndTx:nLayout = 22; break;
 case XML_vertTitleAndTxOverChart: nLayout = 21; break;
 case XML_vertTx:nLayout = 23; break;
+case XML_objOnly:   nLayout = 32; break;
 
 case XML_twoTxTwoObj:
-case XML_twoObjAndObj:
 case XML_objTx:
 case XML_picTx:
 case XML_secHead:
-case XML_objOnly:
-case XML_objAndTwoObj:
 case XML_mediaAndTx:
 case XML_dgm:
 case XML_cust:
diff --git a/sd/qa/unit/data/pptx/tdf157740.pptx 
b/sd/qa/unit/data/pptx/tdf157740.pptx
new file mode 100644
index ..009e9eeb1da0
Binary files /dev/null and b/sd/qa/unit/data/pptx/tdf157740.pptx differ
diff --git a/sd/qa/unit/export-tests-ooxml1.cxx 
b/sd/qa/unit/export-tests-ooxml1.cxx
index 17a5ce94cbf6..407eef46f7b9 100644
--- a/sd/qa/unit/export-tests-ooxml1.cxx
+++ b/sd/qa/unit/export-tests-ooxml1.cxx
@@ -110,11 +110,11 @@ CPPUNIT_TEST_FIXTURE(SdOOXMLExportTest1, testTdf149128)
 
 xmlDocUniquePtr pXmlDoc = parseExport("ppt/slides/slide1.xml");
 assertXPath(pXmlDoc, 
"/p:sld/p:cSld/p:spTree/p:cxnSp/p:nvCxnSpPr/p:cNvCxnSpPr/a:stCxn", "id",
-"42");
+"8");
 assertXPath(pXmlDoc, 
"/p:sld/p:cSld/p:spTree/p:cxnSp/p:nvCxnSpPr/p:cNvCxnSpPr/a:stCxn", "idx",
 "0");
 assertXPath(pXmlDoc, 
"/p:sld/p:cSld/p:spTree/p:cxnSp/p:nvCxnSpPr/p:cNvCxnSpPr/a:endCxn", "id",
-"43");
+"9");
 assertXPath(pXmlDoc, 
"/p:sld/p:cSld/p:spTree/p:cxnSp/p:nvCxnSpPr/p:cNvCxnSpPr/a:endCxn", "idx",
 "2");
 }
diff --git a/sd/qa/unit/export-tests-ooxml2.cxx 
b/sd/qa/unit/export-tests-ooxml2.cxx
index ed6568d0bc1f..65102c143c1d 100644
--- a/sd/qa/unit/export-tests-ooxml2.cxx
+++ b/sd/qa/unit/export-tests-ooxml2.cxx
@@ -157,6 +157,22 @@ CPPUNIT_TEST_FIXTURE(SdOOXMLExportTest2, testTdf153107)
 "tl");
 }
 
+CPPUNIT_TEST_FIXTURE(SdOOXMLExportTest2, testTdf157740_slideMasters)
+{
+createSdImpressDoc("pptx/tdf157740.pptx");
+saveAndReload("Impress Office Open XML");
+
+// Test how many slidemaster we have
+xmlDocUniquePtr pXmlDocContent = parseExport("ppt/presentation.xml");
+assertXPath(pXmlDocContent, 
"/p:presentation/p:sldMasterIdLst/p:sldMasterId", 7);
+
+pXmlDocContent = parseExport("ppt/slideMasters/slideMaster1.xml");
+

[Bug 158754] v.7.5.9 Scrolling sheets on a Mac

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158754

--- Comment #4 from Patrick Luby  ---
Update: a tester has found a workaround without having to install any beta
versions: switch to Skia/Metal rendering.

To enable Skia/Metal rendering, do the following steps:

1. Open the Options dialog by selecting the LibreOffice > Preferences menu
2. Select LibreOffice > View in the left panel
3. In the right panel, check the "Use Skia for all rendering" and uncheck
"Force Skia software rendering" checkboxes as shown in the following screen
snapshot:
 https://bugs.documentfoundation.org/attachment.cgi?id=191409
4. Press the "OK" button and restart if prompted

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

[Bug 158705] scroll bar - thumb wheel display super slow, jerky

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=158705

--- Comment #3 from Patrick Luby  ---
Update: a tester has found a workaround without having to install any beta
versions: switch to Skia/Metal rendering.

To enable Skia/Metal rendering, do the following steps:

1. Open the Options dialog by selecting the LibreOffice > Preferences menu
2. Select LibreOffice > View in the left panel
3. In the right panel, check the "Use Skia for all rendering" and uncheck
"Force Skia software rendering" checkboxes as shown in the following screen
snapshot:
 https://bugs.documentfoundation.org/attachment.cgi?id=191409
4. Press the "OK" button and restart if prompted

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

[Bug 127204] [META] Formatting bugs and Improvements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=127204
Bug 127204 depends on bug 123864, which changed state.

Bug 123864 Summary: No feedback for screen reader when radio button for 
underline attribute changes
https://bugs.documentfoundation.org/show_bug.cgi?id=123864

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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

[Bug 103429] [META] Split and group buttons in toolbar and sidebar bugs and enhancements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=103429
Bug 103429 depends on bug 123864, which changed state.

Bug 123864 Summary: No feedback for screen reader when radio button for 
underline attribute changes
https://bugs.documentfoundation.org/show_bug.cgi?id=123864

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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

[Bug 101912] [META] Accessibility (a11y) bugs and enhancements

2023-12-19 Thread bugzilla-daemon 
https://bugs.documentfoundation.org/show_bug.cgi?id=101912
Bug 101912 depends on bug 123864, which changed state.

Bug 123864 Summary: No feedback for screen reader when radio button for 
underline attribute changes
https://bugs.documentfoundation.org/show_bug.cgi?id=123864

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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

core.git: vcl/qa vcl/unx

2023-12-19 Thread Michael Weghorn (via logerrit) 
 vcl/qa/cppunit/a11y/atspi2/atspi2.cxx |   11 +++
 vcl/unx/gtk3/a11y/atklistener.cxx |2 +-
 vcl/unx/gtk3/a11y/atkwrapper.cxx  |   12 
 vcl/unx/gtk3/a11y/atkwrapper.hxx  |2 +-
 4 files changed, 17 insertions(+), 10 deletions(-)

New commits:
commit a30f8ee1121aa2448be047f104a099b3272e6bde
Author: Michael Weghorn 
AuthorDate: Mon Nov 13 11:45:06 2023 +0100
Commit: Michael Weghorn 
CommitDate: Tue Dec 19 22:33:22 2023 +0100

tdf#123864 gtk3 a11y: Consider states when mapping BUTTON_DROPDOWN

Take the checkable state into account when mapping the
`AccessibleRole::BUTTON_DROPDOWN` role.

There is no direct ATK equivalent for
`AccessibleRole::BUTTON_DROPDOWN`.
Don't always use ATK_ROLE_PUSH_BUTTON, but
use ATK_ROLE_TOGGLE_BUTTON when the button is CHECKABLE,
i.e. it can be toggled.

With this in place, Orca now announces the state of
the underline button (on/off) when using the gtk3
VCL plugin.

Related Orca source code that requires the toggle button
role: [1]

The state is not announced when using the qt6 VCL
plugin yet, and Qt currently doesn't have a toggle button
role, so that would have to be added there first to
do something similar there.

For gtk4, mapping could probably be done similarly,
but more is missing for Orca to announce things in
custom widgets (e.g. event handling),
so leave that for later.

[1] 
https://gitlab.gnome.org/GNOME/orca/-/blob/b80bb951a651f5f12a5ddfb2a5b1c151568d045b/src/orca/scripts/apps/soffice/speech_generator.py#L177

Change-Id: If69e08d2e4939cc709d44e89cc2fd1d01691a70b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160904
Tested-by: Jenkins
Reviewed-by: Michael Weghorn 

diff --git a/vcl/qa/cppunit/a11y/atspi2/atspi2.cxx 
b/vcl/qa/cppunit/a11y/atspi2/atspi2.cxx
index e24bf8078613..04d885d623c3 100644
--- a/vcl/qa/cppunit/a11y/atspi2/atspi2.cxx
+++ b/vcl/qa/cppunit/a11y/atspi2/atspi2.cxx
@@ -25,7 +25,7 @@
 using namespace css;
 
 // from gtk3/a11y/atkwrapper.cxx
-static AtspiRole mapToAtspiRole(sal_Int16 nRole)
+static AtspiRole mapToAtspiRole(sal_Int16 nRole, sal_Int64 nStates)
 {
 switch (nRole)
 {
@@ -103,7 +103,6 @@ static AtspiRole mapToAtspiRole(sal_Int16 nRole)
 MAP_DIRECT(TREE);
 MAP(VIEW_PORT, VIEWPORT);
 MAP_DIRECT(WINDOW);
-MAP(BUTTON_DROPDOWN, PUSH_BUTTON);
 #if ATSPI_ROLE_COUNT > 130 /* ATSPI_ROLE_PUSH_BUTTON_MENU is 129 */
 MAP(BUTTON_MENU, PUSH_BUTTON_MENU);
 #else
@@ -130,7 +129,10 @@ static AtspiRole mapToAtspiRole(sal_Int16 nRole)
 
 #undef MAP_DIRECT
 #undef MAP
-
+case css::accessibility::AccessibleRole::BUTTON_DROPDOWN:
+if (nStates & css::accessibility::AccessibleStateType::CHECKABLE)
+return ATSPI_ROLE_TOGGLE_BUTTON;
+return ATSPI_ROLE_PUSH_BUTTON;
 default:
 SAL_WARN("vcl.gtk", "Unmapped accessible role: " << nRole);
 return ATSPI_ROLE_UNKNOWN;
@@ -265,7 +267,8 @@ void Atspi2TestTree::compareObjects(const 
uno::ReferencegetAccessibleRole());
+const AtspiRole nLORole
+= mapToAtspiRole(xLOContext->getAccessibleRole(), 
xLOContext->getAccessibleStateSet());
 const auto nAtspiRole = pAtspiAccessible.getRole();
 CPPUNIT_ASSERT_EQUAL(nLORole, nAtspiRole);
 /* name (no need to worry about debugging suffixes as 
AccessibilityTools::nameEquals does, as
diff --git a/vcl/unx/gtk3/a11y/atklistener.cxx 
b/vcl/unx/gtk3/a11y/atklistener.cxx
index 3ba088c8..f647c52a5c36 100644
--- a/vcl/unx/gtk3/a11y/atklistener.cxx
+++ b/vcl/unx/gtk3/a11y/atklistener.cxx
@@ -630,7 +630,7 @@ void AtkListener::notifyEvent( const 
accessibility::AccessibleEventObject& aEven
 case accessibility::AccessibleEventId::ROLE_CHANGED:
 {
 uno::Reference< accessibility::XAccessibleContext > xContext = 
getAccessibleContextFromSource( aEvent.Source );
-atk_object_wrapper_set_role( mpWrapper, 
xContext->getAccessibleRole() );
+atk_object_wrapper_set_role(mpWrapper, 
xContext->getAccessibleRole(), xContext->getAccessibleStateSet());
 break;
 }
 
diff --git a/vcl/unx/gtk3/a11y/atkwrapper.cxx b/vcl/unx/gtk3/a11y/atkwrapper.cxx
index 49b1d371ae12..c946a6e3daaf 100644
--- a/vcl/unx/gtk3/a11y/atkwrapper.cxx
+++ b/vcl/unx/gtk3/a11y/atkwrapper.cxx
@@ -167,7 +167,7 @@ AtkStateType mapAtkState( sal_Int64 nState )
 return type;
 }
 
-static AtkRole mapToAtkRole( sal_Int16 nRole )
+static AtkRole mapToAtkRole(sal_Int16 nRole, sal_Int64 nStates)
 {
 switch (nRole)
 {
@@ -310,7 +310,11 @@ static AtkRole mapToAtkRole( sal_Int16 nRole )
 case accessibility::AccessibleRole::WINDOW:
 return ATK_ROLE_WINDOW;
 case accessibility::AccessibleRole::BUTTON_DROPDOWN:
+{
+if (nStates & css::accessibility::AccessibleStateType::CHECKABLE)
+

  1   2   3   4   5   >