[Libreoffice-bugs] [Bug 145371] Global Array of defined user type : values lost

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145371

Dorange-Pattoret Didier  changed:

   What|Removed |Added

 CC||ddora...@dmaths.org

--- Comment #1 from Dorange-Pattoret Didier  ---
Created attachment 175982
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175982=edit
A small extension for tests

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

[Libreoffice-bugs] [Bug 145372] Cross References to Figures Do Not Update

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145372

--- Comment #1 from a...@norsci.com ---
To clarify, when I say "delete the image" I mean delete the frame that contains
the image, the caption, and the field.

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

[Libreoffice-bugs] [Bug 145372] New: Cross References to Figures Do Not Update

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145372

Bug ID: 145372
   Summary: Cross References to Figures Do Not Update
   Product: LibreOffice
   Version: 7.2.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: a...@norsci.com

Description:
When working with a document that contains cross-references to figure numbers,
deleting the figures does not result in the references showing the "Error:
Reference source not found" text. Instead, the field shows the old number.
Using "Update Fields" or pressing F9 does not update them.

Steps to Reproduce:
1. Create a blank Writer document.
2. Insert 4 images.
3. Configure each image to be positioned as a character.
4. Add a caption to each image, which also adds a figure number field to each
one.
5. At the top of the document use the Insert>Cross-reference tool to insert
references to the figure numbers. This simple example just looks like "1 2 3 4"
where each number is a field.
6. Pick an image at random and delete it. While the figure numbering for the
remaining figures does update, the number for the one I deleted remains the
same. So, if I delete figure 2 from the document, the cross references now look
like "1 2 2 3". We *know* that the second reference is wrong, and clicking on
it goes no where, but it is not updated to show the "Error: Reference source
not found" message.
7. Clicking F9 or using the menu to "Update Fields" does not work. Saving the
document and opening it again seems to update the fields. Sometimes clicking
View>"Show Tracked Changes" is enough to update the missing field, but this
doesn't always work.

Actual Results:
The field text for a deleted field target retains the old value.

Expected Results:
The field text for a deleted field target should always show the "Error:
Reference source not found" message.


Reproducible: Always


User Profile Reset: No



Additional Info:
Please fix. This makes working on large documents with lots of cross references
to figures particularly painful.

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

[Libreoffice-bugs] [Bug 145371] New: Global Array of defined user type : values lost

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145371

Bug ID: 145371
   Summary: Global Array of defined user type : values lost
   Product: LibreOffice
   Version: 7.2.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ddora...@dmaths.org

Description:
LO 7.2 : Values of Global Array defined user type are lost at end of runtime.
No problem with LO 7.1 or Aoo 4.1

Steps to Reproduce:
Use joigned extension
1. Run macro 1
2. Run macro 2

Actual Results:
Values of A lost

Expected Results:
Values of A retained


Reproducible: Always


User Profile Reset: Yes



Additional Info:
It works without problem with LO 7.1.2, AOOo 4.1.11 but not with LO 7.2.1
So it's a regression.

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

[Libreoffice-commits] core.git: canvas/source canvas/workben

2021-10-28 Thread Mike Kaganski (via logerrit)
 canvas/source/directx/dx_canvasbitmap.cxx   |   12 ++---
 canvas/source/directx/dx_config.cxx |   10 ++--
 canvas/source/factory/cf_service.cxx|6 +---
 canvas/source/simplecanvas/simplecanvasimpl.cxx |   30 ++--
 canvas/source/tools/canvastools.cxx |6 +---
 canvas/source/tools/parametricpolypolygon.cxx   |   14 ---
 canvas/source/vcl/textlayout.cxx|3 +-
 canvas/workben/canvasdemo.cxx   |   17 -
 8 files changed, 40 insertions(+), 58 deletions(-)

New commits:
commit 1a58461bfa3e980f3113a8a16c09cddda0606e7b
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:12:28 2021 +0300
Commit: Mike Kaganski 
CommitDate: Fri Oct 29 06:50:51 2021 +0200

Prepare for removal of non-const operator[] from Sequence in canvas

Change-Id: Ifb96e496b0994b5fc66975b7aea0a60bcb4a3a03
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124345
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/canvas/source/directx/dx_canvasbitmap.cxx 
b/canvas/source/directx/dx_canvasbitmap.cxx
index adc4b741a4c3..217d3edd2b7b 100644
--- a/canvas/source/directx/dx_canvasbitmap.cxx
+++ b/canvas/source/directx/dx_canvasbitmap.cxx
@@ -97,9 +97,7 @@ namespace dxcanvas
 HBITMAP aHBmp;
 mpBitmap->getBitmap()->GetHBITMAP(Gdiplus::Color(),  
);
 
-uno::Sequence< uno::Any > args(1);
-args[0] <<= reinterpret_cast(aHBmp);
-
+uno::Sequence< uno::Any > args{ 
uno::Any(reinterpret_cast(aHBmp)) };
 aRes <<= args;
 }
 else
@@ -153,9 +151,7 @@ namespace dxcanvas
 
 pGDIPlusBitmap->UnlockBits(  );
 
-uno::Sequence< uno::Any > args(1);
-args[0] <<= reinterpret_cast(hBmpBitmap);
-
+uno::Sequence< uno::Any > args{ 
uno::Any(reinterpret_cast(hBmpBitmap)) };
 aRes <<= args;
 }
 }
@@ -230,9 +226,7 @@ namespace dxcanvas
aSize.getY(), pAlphaBits.get(),
reinterpret_cast(), 
DIB_RGB_COLORS );
 
-uno::Sequence< uno::Any > args(1);
-args[0] <<= reinterpret_cast(hBmpBitmap);
-
+uno::Sequence< uno::Any > args{ 
uno::Any(reinterpret_cast(hBmpBitmap)) };
 aRes <<= args;
 }
 }
diff --git a/canvas/source/directx/dx_config.cxx 
b/canvas/source/directx/dx_config.cxx
index 48609d8c500e..afb52de30f03 100644
--- a/canvas/source/directx/dx_config.cxx
+++ b/canvas/source/directx/dx_config.cxx
@@ -45,9 +45,7 @@ namespace dxcanvas
 {
 try
 {
-uno::Sequence< OUString > aName { "DeviceDenylist" };
-
-uno::Sequence< uno::Any > aProps( GetProperties( aName ));
+uno::Sequence< uno::Any > aProps( GetProperties( { 
"DeviceDenylist" } ));
 uno::Sequence< sal_Int32 > aValues;
 
 if( aProps.getLength() > 0 &&
@@ -70,13 +68,11 @@ namespace dxcanvas
 }
 }
 
-aName[0] = "DenylistCurrentDevice";
-aProps = GetProperties( aName );
+aProps = GetProperties( { "DenylistCurrentDevice" } );
 if( aProps.getLength() > 0 )
 aProps[0] >>= mbDenylistCurrentDevice;
 
-aName[0] = "MaxTextureSize";
-aProps = GetProperties( aName );
+aProps = GetProperties( { "MaxTextureSize" } );
 if( aProps.getLength() > 0 )
 maMaxTextureSize = aProps[0].get();
 else
diff --git a/canvas/source/factory/cf_service.cxx 
b/canvas/source/factory/cf_service.cxx
index d7e612cb6ca9..6cb27699864c 100644
--- a/canvas/source/factory/cf_service.cxx
+++ b/canvas/source/factory/cf_service.cxx
@@ -185,13 +185,11 @@ CanvasFactory::CanvasFactory( 
Reference const & xContext ) :
 {
 // Ugh. Looks like configuration is borked. Fake minimal
 // setup.
-Sequence aServices { 
"com.sun.star.comp.rendering.Canvas.VCL" };
 
m_aAvailableImplementations.emplace_back(OUString("com.sun.star.rendering.Canvas"),
-  aServices );
+Sequence{ "com.sun.star.comp.rendering.Canvas.VCL" } );
 
-aServices[0] = "com.sun.star.comp.rendering.SpriteCanvas.VCL";
 
m_aAvailableImplementations.emplace_back(OUString("com.sun.star.rendering.SpriteCanvas"),
-  aServices );
+Sequence{ "com.sun.star.comp.rendering.SpriteCanvas.VCL" 
} );
 }
 }
 
diff --git a/canvas/source/simplecanvas/simplecanvasimpl.cxx 
b/canvas/source/simplecanvas/simplecanvasimpl.cxx
index 6182d4e2142b..18d2c0e9815d 100644
--- 

[Libreoffice-commits] core.git: 2 commits - basic/source binaryurp/source

2021-10-28 Thread Mike Kaganski (via logerrit)
 basic/source/classes/sbunoobj.cxx   |   17 +++--
 basic/source/classes/sbxmod.cxx |8 +++-
 basic/source/runtime/comenumwrapper.cxx |4 +---
 basic/source/runtime/methods1.cxx   |6 +++---
 basic/source/uno/dlgcont.cxx|4 +---
 basic/source/uno/modsizeexceeded.cxx|4 +---
 basic/source/uno/namecont.cxx   |   16 +---
 binaryurp/source/bridge.cxx |2 +-
 binaryurp/source/bridgefactory.cxx  |5 +++--
 9 files changed, 25 insertions(+), 41 deletions(-)

New commits:
commit f6aef99057c08490af49aec0fd5f2601a83c4e76
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:11:26 2021 +0300
Commit: Mike Kaganski 
CommitDate: Fri Oct 29 06:50:43 2021 +0200

Prepare for removal of non-const operator[] from Sequence in binaryurp

Change-Id: Ibbe07a6de488461a99bb06d558cf740caa606bc9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124344
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/binaryurp/source/bridge.cxx b/binaryurp/source/bridge.cxx
index 9730036ab4a8..3299cd0ed519 100644
--- a/binaryurp/source/bridge.cxx
+++ b/binaryurp/source/bridge.cxx
@@ -950,7 +950,7 @@ void Bridge::removeEventListener(
 void Bridge::sendCommitChangeRequest() {
 assert(mode_ == MODE_REQUESTED || mode_ == MODE_REPLY_1);
 css::uno::Sequence< css::bridge::ProtocolProperty > s(1);
-s[0].Name = "CurrentContext";
+s.getArray()[0].Name = "CurrentContext";
 std::vector< BinaryAny > a { mapCppToBinaryAny(css::uno::Any(s)) };
 sendProtPropRequest(OutgoingRequest::KIND_COMMIT_CHANGE, a);
 }
diff --git a/binaryurp/source/bridgefactory.cxx 
b/binaryurp/source/bridgefactory.cxx
index d2fef4383c06..a2dd1fa97fba 100644
--- a/binaryurp/source/bridgefactory.cxx
+++ b/binaryurp/source/bridgefactory.cxx
@@ -141,12 +141,13 @@ BridgeFactory::getExistingBridges() {
 }
 n = static_cast< sal_Int32 >(n + named_.size());
 css::uno::Sequence< css::uno::Reference< css::bridge::XBridge > > s(n);
+auto r = asNonConstRange(s);
 sal_Int32 i = 0;
 for (auto const& item : unnamed_)
-s[i++] = item;
+r[i++] = item;
 
 for (auto const& item : named_)
-s[i++] = item.second;
+r[i++] = item.second;
 
 return s;
 }
commit 81a7d46d9f89252146bf3ba4074625bdfe3345f8
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:09:55 2021 +0300
Commit: Mike Kaganski 
CommitDate: Fri Oct 29 06:50:32 2021 +0200

Prepare for removal of non-const operator[] from Sequence in basic

Change-Id: If048bc301c38ac5ac5412a7d8f69231705088a50
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124343
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/basic/source/classes/sbunoobj.cxx 
b/basic/source/classes/sbunoobj.cxx
index c1753a67aca0..f9d378ea8865 100644
--- a/basic/source/classes/sbunoobj.cxx
+++ b/basic/source/classes/sbunoobj.cxx
@@ -542,6 +542,7 @@ static void implSequenceToMultiDimArray( SbxDimArray*& 
pArray, Sequence< sal_Int
 sal_Int32 nLen = xIdlArray->getLen( aValue );
 for ( sal_Int32 index = 0; index < nLen; ++index )
 {
+auto pindices = indices.getArray();
 Any aElementAny = xIdlArray->get( aValue, 
static_cast(index) );
 // This detects the dimension were currently processing
 if ( dimCopy == dimension )
@@ -550,15 +551,16 @@ static void implSequenceToMultiDimArray( SbxDimArray*& 
pArray, Sequence< sal_Int
 if ( sizes.getLength() < dimCopy )
 {
 sizes.realloc( sizes.getLength() + 1 );
-sizes[ sizes.getLength() - 1 ] = nLen;
+sizes.getArray()[ sizes.getLength() - 1 ] = nLen;
 indices.realloc( indices.getLength() + 1 );
+pindices = indices.getArray();
 }
 }
 
 if ( bIsZeroIndex )
-indices[ dimCopy - 1 ] = index;
+pindices[ dimCopy - 1 ] = index;
 else
-indices[ dimCopy - 1] = index + 1;
+pindices[ dimCopy - 1] = index + 1;
 
 implSequenceToMultiDimArray( pArray, indices, sizes, aElementAny, 
dimCopy, bIsZeroIndex,  );
 }
@@ -4385,10 +4387,7 @@ Reference< XInterface > createComListener( const Any& 
aControlAny, const OUStrin
 
 Reference< XInvocation > xProxy = new ModuleInvocationProxy( aPrefix, 
xScopeObj );
 
-Sequence args( 3 );
-args[0] = aControlAny;
-args[1] <<= aVBAType;
-args[2] <<= xProxy;
+Sequence args{ aControlAny, Any(aVBAType), Any(xProxy) };
 
 try
 {
@@ -4524,9 +4523,7 @@ bool SbModule::createCOMWrapperForIface( Any& o_rRetAny, 
SbClassModuleObject* pP
 }
 Reference< XInvocation > xProxy = new ModuleInvocationProxy( 
aPureIfaceName, pProxyClassModuleObject );
 
-Sequence args( 2 );
-args[0] 

[Libreoffice-bugs] [Bug 145127] LibreOfficeKit macOS?

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145127

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 145126] It'd be nice if the formula bar in Calc would accept the LibreOffice Dark application color scheme

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145126

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 145125] EDITING Moving a bulleted paragraph upwards/downwards and rejecting all changes leaves paragraph bulleted

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145125

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 145124] EDITING Moving down a numbered paragraph with change tracking and rejecting all gets duplicated

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145124

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 145122] Linux/KDE: Cursor disappears while creating a table in Base, switching between text and styles in Writer …

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145122

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 145061] Font::identifyFont should also detect Type1C font

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145061

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 141406] Forms do not work with PDF/DOCX

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141406

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 141406] Forms do not work with PDF/DOCX

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141406

--- Comment #4 from QA Administrators  ---
Dear LI AR,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 141353] Upgrading from 7.03 to 7.0.5 Win 10 error 1303

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141353

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 141353] Upgrading from 7.03 to 7.0.5 Win 10 error 1303

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141353

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 141325] Problem with Transaction

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141325

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 141325] Problem with Transaction

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141325

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 139476] if you accidently paste something large into a search box LO freezes for a long time

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139476

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 139476] if you accidently paste something large into a search box LO freezes for a long time

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139476

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 139223] FILESAVE DOC: Loosing parallel wrap on DOC export

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139223

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 139223] FILESAVE DOC: Loosing parallel wrap on DOC export

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139223

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 138575] Pasting images makes LibreOffice Writer slow

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138575

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 138575] Pasting images makes LibreOffice Writer slow

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138575

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 136775] Content appears after save & reload (Track & changes involved)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136775

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136775] Content appears after save & reload (Track & changes involved)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136775

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 136774] Image visible which should probably by hidden (track & changes)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136774

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136774] Image visible which should probably by hidden (track & changes)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136774

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 136627] Memory usage increases with 200 MB after hovering over file send (java runtime related)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136627

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 136627] Memory usage increases with 200 MB after hovering over file send (java runtime related)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136627

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136284] Undo steps cut/off broken after RTF paste

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136284

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 109040] [META] RTF paste special bugs and enhancements

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109040
Bug 109040 depends on bug 136284, which changed state.

Bug 136284 Summary: Undo steps cut/off broken after RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=136284

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136284] Undo steps cut/off broken after RTF paste

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136284

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 136178] File opens with different formatting compared to how it was saved (track & changes involved)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136178

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136178] File opens with different formatting compared to how it was saved (track & changes involved)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136178

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 135751] BUG numéros et nombre de pages

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135751

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 135751] BUG numéros et nombre de pages

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135751

--- Comment #3 from QA Administrators  ---
Dear claude.ol.martin,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 135678] Draw unable to open file properly after creation/saving

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135678

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 135678] Draw unable to open file properly after creation/saving

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135678

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 142015] Tabbed NB 'User Interface...' dialog box is blank

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142015

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

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 142001] Crash in: igc64.dll

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142001

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

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 91664] Form controls in frame in section disappear after hiding

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91664

--- Comment #9 from QA Administrators  ---
Dear Graham Horner,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 84427] FILESAVE: Video files not saved in DOC or DOCX

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84427

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 125934] No application icon on Wayland with the qt5 / kf5 backend

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125934

--- Comment #14 from QA Administrators  ---
Dear Jan-Marek Glogowski,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 124694] Video passing slide boundaries causes weird zoom in or shift (gtk2/gtk3)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124694

--- Comment #19 from QA Administrators  ---
Dear Saren Tasciyan,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 124042] Lots of CoreGraphics calls without a valid context

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124042

--- Comment #9 from QA Administrators  ---
Dear Tor Lillqvist,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 118823] Zooming in or out with blue header toolbar button visible rather slow and lagging (Win-only)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118823

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 145355] EDITING: CellStyle should allow making text all UPPERCASE or all lowercase

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145355

--- Comment #2 from Tom Williams  ---
Thanks for the reply.  Yes, I'm aware I can manually change the case of the
text but I was looking for a way to do it automatically and conditionally.  :)

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

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

2021-10-28 Thread Bjoern Michaelsen (via logerrit)
 sw/inc/dbfld.hxx |5 +--
 sw/inc/ddefld.hxx|8 +++-
 sw/inc/docufld.hxx   |8 +++-
 sw/inc/expfld.hxx|7 +++-
 sw/inc/fldbas.hxx|1 
 sw/inc/reffld.hxx|1 
 sw/source/core/doc/DocumentFieldsManager.cxx |   44 ---
 sw/source/core/fields/fldbas.cxx |5 +++
 8 files changed, 33 insertions(+), 46 deletions(-)

New commits:
commit 86d11097cd4a2ae4a6b4e6b35e28a6075376d67a
Author: Bjoern Michaelsen 
AuthorDate: Mon Oct 25 02:02:09 2021 +0200
Commit: Bjoern Michaelsen 
CommitDate: Fri Oct 29 03:00:47 2021 +0200

use virtual function call for dynamic dispatch

... as it is around since the dawn of C++ and should be stable --
certainly more stable and less errorprone that manual typetagging.

Change-Id: I5dfe2ce40c2334dc8fe60705d358779fa4bf1586
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124131
Tested-by: Jenkins
Reviewed-by: Bjoern Michaelsen 

diff --git a/sw/inc/dbfld.hxx b/sw/inc/dbfld.hxx
index 4fabaff6c253..8904575f319b 100644
--- a/sw/inc/dbfld.hxx
+++ b/sw/inc/dbfld.hxx
@@ -47,8 +47,9 @@ public:
 const OUString& GetColumnName() const {return m_sColumn;}
 const SwDBData& GetDBData() const {return m_aDBData;}
 
-virtual voidQueryValue( css::uno::Any& rVal, sal_uInt16 nWhich ) 
const override;
-virtual voidPutValue( const css::uno::Any& rVal, sal_uInt16 nWhich 
) override;
+virtual void QueryValue( css::uno::Any& rVal, sal_uInt16 nWhich ) const 
override;
+virtual void PutValue( const css::uno::Any& rVal, sal_uInt16 nWhich ) 
override;
+virtual void UpdateFields() override {};
 };
 
 // Classes derived from SwFields. They overlay the expand-function.
diff --git a/sw/inc/ddefld.hxx b/sw/inc/ddefld.hxx
index ccb72ff25b24..c96f0bdaa659 100644
--- a/sw/inc/ddefld.hxx
+++ b/sw/inc/ddefld.hxx
@@ -99,6 +99,8 @@ public:
 void DecRefCnt() {  if( !--m_nRefCount && m_pDoc ) RefCntChgd(); }
 
 void SetCRLFDelFlag( bool bFlag ){ m_bCRLFFlag = bFlag; }
+virtual void UpdateFields() override
+{ UpdateDDE(false); };
 void UpdateDDE(const bool bNotifyShells = true);
 };
 
@@ -115,11 +117,11 @@ public:
 
 /** Get parameter via types.
  Name cannot be changed. */
-virtual OUString  GetPar1() const override;
+virtual OUString GetPar1() const override;
 
 // Command
-virtual OUString  GetPar2() const override;
-virtual voidSetPar2(const OUString& rStr) override;
+virtual OUString GetPar2() const override;
+virtual void SetPar2(const OUString& rStr) override;
 };
 
 #endif // INCLUDED_SW_INC_DDEFLD_HXX
diff --git a/sw/inc/docufld.hxx b/sw/inc/docufld.hxx
index 1b76fe7bf83b..9cad6b71f77c 100644
--- a/sw/inc/docufld.hxx
+++ b/sw/inc/docufld.hxx
@@ -288,9 +288,10 @@ public:
 SwHiddenTextFieldType(bool bSetHidden = true);
 
 virtual std::unique_ptr Copy() const override;
+virtual void UpdateFields() override {};
 
-voidSetHiddenFlag( bool bSetHidden );
-bool GetHiddenFlag() const { return m_bHidden; }
+void SetHiddenFlag( bool bSetHidden );
+bool GetHiddenFlag() const { return m_bHidden; }
 };
 
 class SW_DLLPUBLIC SwHiddenTextField final : public SwField
@@ -357,6 +358,7 @@ public:
 SwHiddenParaFieldType();
 
 virtual std::unique_ptr Copy() const override;
+virtual void UpdateFields() override {};
 };
 
 class SwHiddenParaField final : public SwField
@@ -577,6 +579,7 @@ public:
 SwRefPageSetFieldType();
 
 virtual std::unique_ptr Copy() const override;
+virtual void UpdateFields() override {};
 
 private:
 /// noop, there is nothing to update!
@@ -652,6 +655,7 @@ class SwJumpEditFieldType final : public SwFieldType
 public:
 SwJumpEditFieldType( SwDoc& rDoc );
 virtual std::unique_ptr Copy() const override;
+virtual void UpdateFields() override {};
 
 SwCharFormat* GetCharFormat();
 };
diff --git a/sw/inc/expfld.hxx b/sw/inc/expfld.hxx
index e82f9b23772f..25d442ee107a 100644
--- a/sw/inc/expfld.hxx
+++ b/sw/inc/expfld.hxx
@@ -72,6 +72,7 @@ class SAL_DLLPUBLIC_RTTI SwGetExpFieldType final : public 
SwValueFieldType
 public:
 SwGetExpFieldType(SwDoc* pDoc);
 virtual std::unique_ptr Copy() const override;
+virtual void UpdateFields() override {};
 
 /** Overlay, because get-field cannot be changed and therefore
  does not need to be updated. Update at changing of set-values! */
@@ -180,8 +181,9 @@ public:
 void SetOutlineLvl( sal_uInt8 n )   { m_nLevel = n; }
 void SetChapter(SwSetExpField& rField, const SwNode& rNd, SwRootFrame 
const* pLayout);
 
-virtual voidQueryValue( css::uno::Any& rVal, sal_uInt16 nWhich ) 
const override;
-virtual voidPutValue( const css::uno::Any& rVal, sal_uInt16 

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

2021-10-28 Thread Bjoern Michaelsen (via logerrit)
 sw/inc/ddefld.hxx|1 
 sw/source/core/doc/DocumentFieldsManager.cxx |6 +
 sw/source/core/fields/ddefld.cxx |  100 ++-
 3 files changed, 57 insertions(+), 50 deletions(-)

New commits:
commit cae107bab822acc198569750ae5b9a272f7ae996
Author: Bjoern Michaelsen 
AuthorDate: Mon Oct 25 00:52:32 2021 +0200
Commit: Bjoern Michaelsen 
CommitDate: Fri Oct 29 02:59:36 2021 +0200

consolidate DDE updates in FieldType

Change-Id: I70243dad4cd62ab1f601d010e0bcf441831ec556
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124130
Reviewed-by: Michael Stahl 
Tested-by: Jenkins

diff --git a/sw/inc/ddefld.hxx b/sw/inc/ddefld.hxx
index a9ca4db81b52..ccb72ff25b24 100644
--- a/sw/inc/ddefld.hxx
+++ b/sw/inc/ddefld.hxx
@@ -99,6 +99,7 @@ public:
 void DecRefCnt() {  if( !--m_nRefCount && m_pDoc ) RefCntChgd(); }
 
 void SetCRLFDelFlag( bool bFlag ){ m_bCRLFFlag = bFlag; }
+void UpdateDDE(const bool bNotifyShells = true);
 };
 
 // DDE-field
diff --git a/sw/source/core/doc/DocumentFieldsManager.cxx 
b/sw/source/core/doc/DocumentFieldsManager.cxx
index b15e043aa795..530f4ea22bec 100644
--- a/sw/source/core/doc/DocumentFieldsManager.cxx
+++ b/sw/source/core/doc/DocumentFieldsManager.cxx
@@ -49,6 +49,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -405,8 +406,9 @@ void DocumentFieldsManager::UpdateFields( bool bCloseDB )
 
 case SwFieldIds::Dde:
 {
-SwMsgPoolItem aUpdateDDE( RES_UPDATEDDETBL );
-pFieldType->CallSwClientNotify(sw::LegacyModifyHint(nullptr, 
));
+assert(dynamic_cast(pFieldType.get()));
+auto pDDEFieldType = 
static_cast(pFieldType.get());
+pDDEFieldType->UpdateDDE(false);
 break;
 }
 case SwFieldIds::GetExp:
diff --git a/sw/source/core/fields/ddefld.cxx b/sw/source/core/fields/ddefld.cxx
index 590fcef86cad..8b326d02cd62 100644
--- a/sw/source/core/fields/ddefld.cxx
+++ b/sw/source/core/fields/ddefld.cxx
@@ -97,54 +97,8 @@ public:
 return SUCCESS;
 }
 
-OSL_ENSURE(m_rFieldType.GetDoc(), "no pDoc");
-
-// no dependencies left?
-if (!m_rFieldType.IsModifyLocked() && !ChkNoDataFlag())
-{
-SwViewShell* pSh = 
m_rFieldType.GetDoc()->getIDocumentLayoutAccess().GetCurrentViewShell();
-SwEditShell* pESh = m_rFieldType.GetDoc()->GetEditShell();
-
-// Search for fields. If no valid found, disconnect.
-SwMsgPoolItem aUpdateDDE( RES_UPDATEDDETBL );
-m_rFieldType.LockModify();
-
-std::vector vFields;
-std::vector vTables;
-m_rFieldType.GatherFields(vFields, false);
-m_rFieldType.GatherDdeTables(vTables);
-const bool bDoAction = vFields.size() || vTables.size();
-if(bDoAction)
-{
-if(pESh)
-pESh->StartAllAction();
-else if(pSh)
-pSh->StartAction();
-}
-
-// DDE fields attribute in the text
-for(auto pFormatField: vFields)
-{
-if(pFormatField->GetTextField())
-pFormatField->UpdateTextNode( nullptr,  );
-}
-// a DDE tables in the text
-for(auto pTable: vTables)
-pTable->ChangeContent();
-
-m_rFieldType.UnlockModify();
-
-if(bDoAction)
-{
-if(pESh)
-pESh->EndAllAction();
-else if(pSh)
-pSh->EndAction();
-
-if(pSh)
-pSh->GetDoc()->getIDocumentState().SetModified();
-}
-}
+if(!ChkNoDataFlag())
+m_rFieldType.UpdateDDE();
 
 return SUCCESS;
 }
@@ -332,6 +286,56 @@ void SwDDEFieldType::PutValue( const uno::Any& rVal, 
sal_uInt16 nWhichId )
 SetCmd( sNewCmd.makeStringAndClear() );
 }
 
+void SwDDEFieldType::UpdateDDE(const bool bNotifyShells)
+{
+auto pDoc = GetDoc();
+assert(pDoc);
+if(IsModifyLocked())
+return;
+SwViewShell* pSh = bNotifyShells ? 
pDoc->getIDocumentLayoutAccess().GetCurrentViewShell() : nullptr;
+SwEditShell* pESh = bNotifyShells ? pDoc->GetEditShell() : nullptr;
+
+// Search for fields. If no valid found, disconnect.
+LockModify();
+
+std::vector vFields;
+std::vector vTables;
+GatherFields(vFields, false);
+GatherDdeTables(vTables);
+const bool bDoAction = vFields.size() || vTables.size();
+if(bDoAction)
+{
+if(pESh)
+pESh->StartAllAction();
+else if(pSh)
+pSh->StartAction();
+}
+
+// DDE fields attribute in the text
+SwMsgPoolItem aUpdateDDE(RES_UPDATEDDETBL);
+for(auto pFormatField: vFields)
+{
+if(pFormatField->GetTextField())
+pFormatField->UpdateTextNode( nullptr,  );
+}
+// a DDE tables in the text
+for(auto pTable: vTables)
+pTable->ChangeContent();
+
+UnlockModify();
+
+

[Libreoffice-bugs] [Bug 139503] No playing item in presentation mode (GDI)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139503

Aron Budea  changed:

   What|Removed |Added

 CC||ba...@caesar.elte.hu

--- Comment #12 from Aron Budea  ---
Telesto, what are your GPU details? Ie. cache\opengl_device.log

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

[Libreoffice-bugs] [Bug 145355] EDITING: CellStyle should allow making text all UPPERCASE or all lowercase

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145355

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
What you are asking meaning change the cell content. Modify the format never
carries a change on the content.
I guess you know there is an option to Menu/Format/Text to do it.

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

[Libreoffice-bugs] [Bug 145353] Editing within a CALC Cell with wordwrap .. does not remove deleted characters from next line in the cell!

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145353

V.S. Umamaheswaran  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0
   Assignee|libreoffice-b...@lists.free |bhanudo...@rogers.com
   |desktop.org |

--- Comment #2 from V.S. Umamaheswaran  ---
Created attachment 175981
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175981=edit
Contains screen captures showing the problem along with a Readme file.

I have attached samples showing (what I think is a) Bug, as requested.

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

[Libreoffice-bugs] [Bug 145340] Collabora Android 6.4.13

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145340

Aron Budea  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|UNCONFIRMED |RESOLVED
 CC||ba...@caesar.elte.hu

--- Comment #2 from Aron Budea  ---
This issue should be fixed now by the following commit:
https://github.com/CollaboraOnline/online/commit/c6e67fd7da95ffec0fc5cd2a3170c46f2bc52e41

The data loss is unfortunate, however there is an attempted fix for that as
well (it wasn't consistently reproducible), please wait for the next update, or
give the latest snapshot a try:
https://www.collaboraoffice.com/downloads/Collabora-Office-Android-Snapshot/

If either issue persists, use the following URL to report issues related to the
Collabora Office app:
https://github.com/CollaboraOnline/online/issues/

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

[Libreoffice-bugs] [Bug 122735] objects outside the selected group don't become pale

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

Regina Henschel  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 145359] Enter group: the other shapes are not dimmed & cannot add a other shape in the group

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145359

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||2735

--- Comment #2 from Regina Henschel  ---
Your bug reports two independent problems. The problem "are not dimmed" is
already reported in bug 122735. So your report should focus on the problem
"functionality to add an existing shape to a group is missing". Please change
the summary accordingly. That would then be an enhancement request.

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

[Libreoffice-bugs] [Bug 139162] Copy Paste in LibreOffice Online documents non-libre>libre and libre>libre (Collabora/Owncloud)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139162

Aron Budea  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||ba...@caesar.elte.hu
 Resolution|--- |MOVED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aron Budea  ---
Please check again with a fresh CODE/Collabora Online version, if the issue
still persists, open an issue at:
https://github.com/CollaboraOnline/online/issues/

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

[Libreoffice-bugs] [Bug 122735] objects outside the selected group don't become pale

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122735

Regina Henschel  changed:

   What|Removed |Added

 CC||alex.pyatt...@gmail.com

--- Comment #6 from Regina Henschel  ---
*** Bug 136882 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 136882] Enter group does not have any visual feedback

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136882

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #2 from Regina Henschel  ---
The problem is already tracked in bug 122735.

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

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

[Libreoffice-bugs] [Bug 134116] LibO Writer 6.4.4 crashes with serial correspondence

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134116

Aron Budea  changed:

   What|Removed |Added

  Alias|asdfgh  |

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

[Libreoffice-bugs] [Bug 144896] problem with SUMIF, SUBTOTAL and AUTO FILTER leaving trace numbers when total should be 0

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144896

Michael Warner  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|UNCONFIRMED |RESOLVED

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

[Libreoffice-bugs] [Bug 134116] LibO Writer 6.4.4 crashes with serial correspondence

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134116

--  changed:

   What|Removed |Added

  Alias||asdfgh

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

[Libreoffice-bugs] [Bug 145370] New: spell checking initiated by F7 doesn't start where you'd expect, and endnotes are also checked

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145370

Bug ID: 145370
   Summary: spell checking initiated by F7 doesn't start where
you'd expect, and endnotes are also checked
   Product: LibreOffice
   Version: 7.2.0.4 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@cspv.hu

Description:
hi, 

I've been using the appimage 7. for an hour only, 
and I like it, but when I press f7 to activate spell checking, 
what happens is not what I'd expect 

Steps to Reproduce:
1. press f7
2. 
3.

Actual Results:
if I place the cursor at the beginning of the doc, it works okay..

but later on / deeper in the doc, when I press it while having the cursor on 
or before a word which I'd like to add to the dictionary, the checking doesn't
start there...

moreover, it goes to the endnotes, too! and when it is not the same language as
the body text, every word will be underlined as "wrong"

Expected Results:
this has worked perfectly for long...
I use 6.something, and works perfectly, and I can't remember when I last had a
problem with getting a word checked...
that is, getting the  spell checking start where I wish...


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.4 / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded


-
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

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

[Libreoffice-bugs] [Bug 145369] lines and spaces occasionally inserted -- (doesn't happen in Writer 7)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145369

--- Comment #1 from peter josvai  ---
Created attachment 175980
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175980=edit
spaces and lines created by placing the cursor into the body of an empty
document

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

[Libreoffice-bugs] [Bug 145369] New: lines and spaces occasionally inserted -- (doesn't happen in Writer 7)

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145369

Bug ID: 145369
   Summary: lines and spaces occasionally inserted -- (doesn't
happen in Writer 7)
   Product: LibreOffice
   Version: 6.4.7.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@cspv.hu

Description:
this is a strange behavior..

I'm using version 6.4.7.6
so I downloaded the v7 app image, 7.2.0.4
and it works perfectly.. without this undesired behavior...

I'm only reporting this because perhaps nobody has,and this might be helpful
some day in the future if(ever) this should show up again :)

Steps to Reproduce:
1. you have a document, with nothing typed in it yet
2. place your cursor somewhere, like, in line 15
3.

Actual Results:
to your surprise, you are able to do this...
although nothing has been typed "that far"...
you can place your cursor there...

moreover, the spaces thus created, on the fly, will remain there... for real..

you can also place the cursor to a  nearer spot, like line 5 instead of line
15, 
and the spaces will magically rearrange..


Expected Results:
if you haven't typed, added characters / spaces to your doc, you shouldn't be
able to place your cursor


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

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

[Libreoffice-bugs] [Bug 145368] Comment boxes in LibreOffice Writer are smaller than their text

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145368

--- Comment #1 from Tohotom  ---
Created attachment 175979
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175979=edit
Screenshot of tbe broken comment box

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

[Libreoffice-bugs] [Bug 145368] New: Comment boxes in LibreOffice Writer are smaller than their text

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145368

Bug ID: 145368
   Summary: Comment boxes in LibreOffice Writer are smaller than
their text
   Product: LibreOffice
   Version: 7.2.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: megteheted_toho...@yahoo.com

Description:
Comment boxes in LibreOffice Writer are one line smaller than the the text
entered in them. Boxes will resize with the text, but always cut/hide the last
line.

Steps to Reproduce:
1.Open LO Writer document
2.Insert comment
3.Enter text in comment box

Actual Results:
The last line will remain hidden.

Expected Results:
Last line should be visible.


Reproducible: Always


User Profile Reset: No



Additional Info:
Using Kubuntu 20.04, with LO 7.2.2 installed form fresh PPA

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

[Libreoffice-bugs] [Bug 144158] MalwareBytes instantly and completely shuts down Libreoffice when clicking Tools / Options / Advanced

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144158

--- Comment #14 from xordevore...@gmail.com ---
Declare it not your bug if you want but it means I'm skipping using parts of LO
affected by it.

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

[Libreoffice-bugs] [Bug 145367] MIN(SUM(), 333) is damaged on edit

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145367

--- Comment #2 from Dave McKellar  ---
Created attachment 175978
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175978=edit
Screenshot: The damanged formula in LibreOffice Writer

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

[Libreoffice-bugs] [Bug 145367] MIN(SUM(), 333) is damaged on edit

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145367

--- Comment #1 from Dave McKellar  ---
Created attachment 175977
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175977=edit
Screenshot of a the RTF file in a text editor showing the codes.  The field
formula is highlighted

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

[Libreoffice-bugs] [Bug 145367] New: MIN(SUM(), 333) is damaged on edit

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145367

Bug ID: 145367
   Summary: MIN(SUM(),333) is damaged on edit
   Product: LibreOffice
   Version: 7.2.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dmckel...@gmail.com

Created attachment 175976
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175976=edit
A RTF doc made with Microsoft Word - load this info LibreOffice Writer

1. Create a RTF document in Microsoft Word with field formula of
MIN(SUM(),333)
2. Load that RTF into LibreOffice Writer
3. Right click on the field formula and select "Edit fields" and the value
becomes incorrect and the formula has changed to MIN(SUM()|333) which is
invalid syntax.

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

[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145357

Timur  changed:

   What|Removed |Added

 Resolution|FIXED   |NOTABUG

--- Comment #11 from Timur  ---
https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status

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

[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #3 from phv  ---
I worry that too much information may overload the interface, especially when
the information is following the text. I would prefer that the label only
appears when the mouse hovers over the break mark. Today, no symbol clearly
indicates that the break is a clickable element.

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

[Libreoffice-ux-advise] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #3 from phv  ---
I worry that too much information may overload the interface, especially when
the information is following the text. I would prefer that the label only
appears when the mouse hovers over the break mark. Today, no symbol clearly
indicates that the break is a clickable element.

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

[Libreoffice-bugs] [Bug 138347] Link to call Basic script with vnd.sun.star.script: not working in Writer. Same thing working in Calc (also with HYPERLINK()).

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138347

--- Comment #5 from Wolfgang Jäger  ---
Created attachment 175975
  --> https://bugs.documentfoundation.org/attachment.cgi?id=175975=edit
Exemplifying relevant differences by three insetzed hyperlinks

(In reply to Andreas Heinisch from comment #4)
> I tried to investigate this error. Here are my findings:
> 
> For both Calc and Writer the URL will be open in:
> https://opengrok.libreoffice.org/xref/core/sfx2/source/appl/appopen.
> cxx?r=5021a10f#1078
> 
> The only difference is that the target of the URL is "empty" for Calc and
> "_blank" for Writer, ...

> Imho, this is not a macro problem, but a problem in the target handling in
> appopen.cxx and the supported protocols for the "_blank" target.

I can't go the same ways, but would doubt the "... but a problem in the target
handling..." as the only background. 

After all ordinary external links assigned to text portions in Writer are
working as expected, and for a link made to call a script, I would expect the
target frame irrelevant.  

A new example exemplifying differences I suppose to be part of the bug's
backround is attached as "bug_tdf#138347_example2 .

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

[Libreoffice-bugs] [Bug 145366] New: writer latency

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145366

Bug ID: 145366
   Summary: writer latency
   Product: LibreOffice
   Version: 7.2.1.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jon.nico...@wanadoo.fr

Description:
When I use libreoffice writer on windows 11 I have latency in typing and with
the mouse.

Steps to Reproduce:
I am using Windows 11 21H2.
I am having a latency problem with libreoffice 7.2.2.
I am using writer in normal mode, what I type and when I click in different
places there is a delay.
If I restart the application in safe mode without disabling or other settings
the problem goes away.
How to fix the problem?

Thank you

Actual Results:
I disabled OpenGL as indicated in your solution but identical result.

Expected Results:
Problem still present


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
The software should work without latency like when I start it in safe mode

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

[Libreoffice-commits] core.git: 2 commits - solenv/gbuild vcl/unx

2021-10-28 Thread Stephan Bergmann (via logerrit)
 solenv/gbuild/CppunitTest.mk |9 +
 solenv/gbuild/PythonTest.mk  |3 ---
 vcl/unx/gtk3/gtkinst.cxx |   10 ++
 3 files changed, 11 insertions(+), 11 deletions(-)

New commits:
commit e06ba31a037ea3ff192c9a00db6152179eb298a6
Author: Stephan Bergmann 
AuthorDate: Thu Oct 28 14:08:59 2021 +0200
Commit: Stephan Bergmann 
CommitDate: Thu Oct 28 20:41:00 2021 +0200

Fix passing DYLD_LIBRARY_PATH into lldb on macOS

...making sure that the shell expands the leading

  DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH:+$DYLD_LIBRARY_PATH:}...

before it reaches lldb.

(This gets rid of gb_{Cppunit,Pyhton}_{PRE,POST}GDBTRACE again.  No idea why
c38a4d9ce248b4b3fcc9208b25dfa599fe506ac0 "Make the CPPUNITTRACE="lldb --" 
thing
work again (on macOS)" used -s with a temp file rather than -o to pass that 
env
var into lldb.)

Change-Id: I9ae5217a9629981c8652fc5aca8f97fa6eb99729
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124331
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/solenv/gbuild/CppunitTest.mk b/solenv/gbuild/CppunitTest.mk
index 895cb3edca49..bf29724d7eaf 100644
--- a/solenv/gbuild/CppunitTest.mk
+++ b/solenv/gbuild/CppunitTest.mk
@@ -32,14 +32,10 @@ gb_PythonTest_GDBTRACE := $(subst gdb,\
PYTHONWARNINGS=default gdb -return-child-result -ex 
"add-auto-load-safe-path $(INSTDIR)" -ex "set environment $(subst =, 
,$(gb_PythonTest_PRECOMMAND))" $(if $(PYTHONWARNINGS),-ex 'set environment 
PYTHONWARNINGS $(PYTHONWARNINGS)') $(gb_CppunitTest_malloc_check) 
$(gb_CppunitTest_DEBUGCPPUNIT),\
$(CPPUNITTRACE))
 else ifneq ($(filter lldb,$(CPPUNITTRACE)),)
-gb_CppunitTest_PREGDBTRACE := lo_dyldpathfile=$(call var2file,$(shell 
$(gb_MKTEMP)),500,settings set target.env-vars 
$(gb_CppunitTest_CPPTESTPRECOMMAND))
 gb_CppunitTest_GDBTRACE := $(subst lldb,\
-   lldb -s $$lo_dyldpathfile $(gb_CppunitTest_malloc_check),\
+   lldb -o "env $(gb_CppunitTest_CPPTESTPRECOMMAND)" 
$(gb_CppunitTest_malloc_check),\
$(CPPUNITTRACE))
-gb_CppunitTest_POSTGDBTRACE := rm $$lo_dyldpathfile
-gb_PythonTest_PREGDBTRACE := lo_dyldpathfile=$(call var2file,$(shell 
$(gb_MKTEMP)),500,settings set target.env-vars $(gb_PythonTest_PRECOMMAND))
 gb_PythonTest_GDBTRACE := $(gb_CppunitTest_GDBTRACE)
-gb_PythonTest_POSTGDBTRACE := $(gb_CppunitTest_POSTGDBTRACE)
 else
 gb_CppunitTest_GDBTRACE := $(CPPUNITTRACE)
 gb_PythonTest_GDBTRACE := $(gb_CppunitTest_GDBTRACE)
@@ -133,7 +129,6 @@ else
( \
$(if $(gb_CppunitTest_localized),for l in $(WITH_LANG_LIST) ; 
do \
printf 'LO_TEST_LOCALE=%s\n' "$$l" && 
LO_TEST_LOCALE="$$l" ) \
-   $(if 
$(gb_CppunitTest_PREGDBTRACE),$(gb_CppunitTest_PREGDBTRACE) &&) \
$(if $(gb_CppunitTest__vcl_no_svp), \
$(filter-out 
SAL_USE_VCLPLUGIN=svp,$(gb_TEST_ENV_VARS)),$(gb_TEST_ENV_VARS)) \
$(EXTRA_ENV_VARS) \
@@ -146,8 +141,6 @@ else
$(gb_CppunitTest_CPPTESTCOMMAND) \
$(call gb_LinkTarget_get_target,$(call 
gb_CppunitTest_get_linktarget,$*)) \
$(call gb_CppunitTest__make_args) "-env:CPPUNITTESTTARGET=$@" \
-   $(if $(gb_CppunitTest_POSTGDBTRACE), \
-   ; RET=$$? && $(gb_CppunitTest_POSTGDBTRACE) && (exit 
$$RET)) \
$(if $(gb_CppunitTest_localized),|| exit $$?; done) \
) \
$(if $(gb_CppunitTest__interactive),, \
diff --git a/solenv/gbuild/PythonTest.mk b/solenv/gbuild/PythonTest.mk
index bc404d4fb817..4e81261d2354 100644
--- a/solenv/gbuild/PythonTest.mk
+++ b/solenv/gbuild/PythonTest.mk
@@ -49,7 +49,6 @@ else
$(if $(value gb_CppunitTest_postprocess), \
rm -fr $@.core && mkdir $@.core && cd $@.core 
&&)) \
{ \
-   $(if $(gb_PythonTest_PREGDBTRACE),$(gb_PythonTest_PREGDBTRACE) 
&&) \
$(if $(filter 
gdb,$(gb_PythonTest_GDBTRACE)),,$(gb_PythonTest_PRECOMMAND)) \
$(if $(G_SLICE),G_SLICE=$(G_SLICE)) \
$(if 
$(GLIBCXX_FORCE_NEW),GLIBCXX_FORCE_NEW=$(GLIBCXX_FORCE_NEW)) \
@@ -64,8 +63,6 @@ else
$(ICECREAM_RUN) $(gb_PythonTest_GDBTRACE) 
$(gb_CppunitTest_VALGRINDTOOL) $(gb_CppunitTest_RR) \
$(gb_PythonTest_COMMAND) \
$(if 
$(PYTHON_TEST_NAME),$(PYTHON_TEST_NAME),$(MODULES)) \
-   $(if $(gb_PythonTest_POSTGDBTRACE), \
-   ; RET=$$? && $(gb_PythonTest_POSTGDBTRACE) && (exit 
$$RET)) \
; } \
$(if $(gb_CppunitTest__interactive),, \
> $@.log 2>&1 \
commit 39fbcc330b20f2f4d1c93024734f1b330edd5408
Author: Caolán McNamara 
AuthorDate: Thu Oct 28 17:11:08 2021 +0100
Commit: Caolán McNamara 
CommitDate: Thu Oct 28 20:40:45 2021 +0200

gtk4: use a GtkPicture for 

[Libreoffice-commits] core.git: svx/uiconfig

2021-10-28 Thread Caolán McNamara (via logerrit)
 svx/uiconfig/ui/textunderlinecontrol.ui |   11 ---
 1 file changed, 11 deletions(-)

New commits:
commit 4f5b5a19f450ae0b2dcdb99d26f48cf3aea352ad
Author: Caolán McNamara 
AuthorDate: Thu Oct 28 14:31:47 2021 +0100
Commit: Caolán McNamara 
CommitDate: Thu Oct 28 20:40:27 2021 +0200

center the content of the underline control

Change-Id: If93af6e031bd108903d9528a43bd7e06fcd8340e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124339
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/svx/uiconfig/ui/textunderlinecontrol.ui 
b/svx/uiconfig/ui/textunderlinecontrol.ui
index eef6a69adb68..81edf621ed39 100644
--- a/svx/uiconfig/ui/textunderlinecontrol.ui
+++ b/svx/uiconfig/ui/textunderlinecontrol.ui
@@ -77,7 +77,6 @@
 True
 none
 True
-0
   
   
 False
@@ -93,7 +92,6 @@
 Single
 image_spacing_1
 none
-0
 True
   
   
@@ -110,7 +108,6 @@
 Double
 image_spacing_2
 none
-0
 True
   
   
@@ -127,7 +124,6 @@
 Bold
 image_spacing_3
 none
-0
 True
   
   
@@ -144,7 +140,6 @@
 Dotted
 image_spacing_4
 none
-0
 True
   
   
@@ -161,7 +156,6 @@
 Dotted (Bold)
 image_spacing_5
 none
-0
 True
   
   
@@ -178,7 +172,6 @@
 Dash
 image_spacing_6
 none
-0
 True
   
   
@@ -195,7 +188,6 @@
 Long Dash
 image_spacing_7
 none
-0
 True
   
   
@@ -212,7 +204,6 @@
 Dot Dash
 image_spacing_8
 none
-0
 True
   
   
@@ -229,7 +220,6 @@
 Dot Dot Dash
 image_spacing_9
 none
-0
 True
   
   
@@ -246,7 +236,6 @@
 Wave
 image_spacing_10
 none
-0
 True
   
   


[Libreoffice-commits] core.git: offapi/com

2021-10-28 Thread Michael Weghorn (via logerrit)
 offapi/com/sun/star/accessibility/XAccessibleSelection.idl |5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

New commits:
commit d13307b93bfc21c7e5996c43e359906c255b0830
Author: Michael Weghorn 
AuthorDate: Thu Oct 28 14:01:04 2021 +0200
Commit: Michael Weghorn 
CommitDate: Thu Oct 28 20:36:30 2021 +0200

XAccessibleSelection: Don't reference non-existing methods in doc

There are no 'XAccessibleSelection::deselectSelectedChild'
and 'XAccessibleSelection::getSelectedChild' methods, so don't
mention them in the documentation for
'getSelectedAccessibleChildCount'.

First, there's 'XAccessibleSelection::getSelectedAccessibleChild',
but not 'XAccessibleSelection::getSelectedChild', so update that
accordingly.

Second, there's no 'XAccessibleSelection::deselectSelectedChild',
and 'XAccessibleSelection::deselectAccessibleChild' doesn't take an
index into the selection, but a child index, s. its documentation
and the commit message of pending Gerrit change
Change-Id: I3c63c647e61baaa6288ffd545d8d89d8b94231de
("gtk3 a11y: Use correct index when deselecting child")
on how the semantics of AT-SPI functions with corresponding
names differ.

(The comment was added in

commit daacf7ed0bc8a1a2447c4b1cb340c97f82918af8
Date:   Thu Apr 24 16:35:46 2003 +

INTEGRATION: CWS uaa02 (1.1.2); FILE ADDED
2003/04/02 10:06:50 obr 1.1.2.3: #108113# Renamed 
deselectSelectedAccessibleChild to deselectAccessibleChild
2003/03/14 10:40:52 af 1.1.2.2: #108113# Removed references to the 
drafts directory.
2003/03/11 15:00:39 af 1.1.2.1: #108113# Moved from 
drafts/com/sun/star/accessibility.

and

> 2003/04/02 10:06:50 obr 1.1.2.3: #108113# Renamed 
deselectSelectedAccessibleChild to deselectAccessibleChild

sounds like there might temporarily have existed a draft implementation
that actually took an index into the selection rather than
a child index.)

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

diff --git a/offapi/com/sun/star/accessibility/XAccessibleSelection.idl 
b/offapi/com/sun/star/accessibility/XAccessibleSelection.idl
index cc10cca44177..0d9d18820d02 100644
--- a/offapi/com/sun/star/accessibility/XAccessibleSelection.idl
+++ b/offapi/com/sun/star/accessibility/XAccessibleSelection.idl
@@ -97,9 +97,8 @@ interface XAccessibleSelection : 
::com::sun::star::uno::XInterface
 selected.
 
 This number specifies the valid interval of indices that can be
-used as arguments for the methods
-XAccessibleSelection::getSelectedChild() and
-XAccessibleSelection::deselectSelectedChild().
+used as arguments for the method
+XAccessibleSelection::getSelectedAccessibleChild().
 
 @return
 Returns the number of selected children of this object or 0 if


[Libreoffice-commits] core.git: vcl/unx

2021-10-28 Thread Michael Weghorn (via logerrit)
 vcl/unx/gtk3/a11y/atkselection.cxx |8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

New commits:
commit eec233bf33ac0d9ac1ba0ecc669a5ecf58626ef2
Author: Michael Weghorn 
AuthorDate: Tue Oct 26 16:51:35 2021 +0200
Commit: Michael Weghorn 
CommitDate: Thu Oct 28 20:36:14 2021 +0200

gtk3 a11y: Use correct index when deselecting child

The AT-SPI selection interface provides two functions
to unselect:

 gboolean atspi_selection_deselect_selected_child (AtspiSelection *obj, 
gint selected_child_index, GError **error);
 gboolean atspi_selection_deselect_child (AtspiSelection *obj, gint 
child_index, GError **error);

For the first one, 'atspi_selection_deselect_selected_child',
"child_index is the index in the selected-children list,
not the index in the parent container." [1]

For the second one, 'atspi_selection_deselect_child',
"child_index is the index of the child in the parent container". [2]

ATKSelection, on the other hand, only has

gboolean
atk_selection_remove_selection (AtkSelection *selection,
gint i);

where the index 'i' is "a gint specifying the index in the selection set.
(e.g. the ith selection as opposed to the ith child)." [3]

That means, the meaning of the index in
'atk_selection_remove_selection' is the same as in
'atspi_selection_deselect_selected_child', while
'XAccessibleSelection::deselectAccessibleChild' expects
an index in the parent container, not in the selection
set.

Therefore, convert the index from an index in the
selection to a child index first before passing
it into 'XAccessibleSelection::deselectAccessibleChild'.

(For ATK, the mapping from the two AT-SPI to the
ATK function is done in libatk-bridge.)

Example to reproduce wrong behaviour without this
change in place:

1) select cells B1 to E5 in Calc
2) start Accerciser
3) select the Calc table in Accerciser
4) get AT-SPI selection interface for the table by typing the following
   in the IPython Console in Accerciser:

sel = acc.querySelection()

5) check whether child 0 (i.e. cell A1) is selected

In : sel.isChildSelected(0)
Out: False

-> OK

6) check whether child 1 (i.e. cell B1) is selected:

In : sel.isChildSelected(1)
Out: True

-> OK

7a) try to unselect cell B1:
In : sel.deselectChild(1)
Out: True

-> NOK: selection remains unchanged, cell B1 is still selected

Alternatively, intead of step 7a:
7b) try to unselect cell C1 (2nd item in the selection):

In : sel.deselectSelectedChild(1)
Out: True

-> NOK: cell B1 gets unselected instead of C1

[1] 
https://developer-old.gnome.org/libatspi/unstable/libatspi-atspi-selection.html#atspi-selection-deselect-selected-child
[2] 
https://developer-old.gnome.org/libatspi/unstable/libatspi-atspi-selection.html#atspi-selection-deselect-child
[3] 
https://gnome.pages.gitlab.gnome.org/atk/AtkSelection.html#atk-selection-remove-selection

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

diff --git a/vcl/unx/gtk3/a11y/atkselection.cxx 
b/vcl/unx/gtk3/a11y/atkselection.cxx
index 91759e8d0b21..22d515f1b6fa 100644
--- a/vcl/unx/gtk3/a11y/atkselection.cxx
+++ b/vcl/unx/gtk3/a11y/atkselection.cxx
@@ -141,7 +141,13 @@ selection_remove_selection( AtkSelection *selection,
 = getSelection( selection );
 if( pSelection.is() )
 {
-pSelection->deselectAccessibleChild( i );
+css::uno::Reference xAcc = 
pSelection->getSelectedAccessibleChild(i);
+if (!xAcc.is())
+return false;
+
+css::uno::Reference 
xAccContext = xAcc->getAccessibleContext();
+const sal_Int32 nChildIndex = 
xAccContext->getAccessibleIndexInParent();
+pSelection->deselectAccessibleChild(nChildIndex);
 return true;
 }
 }


[Libreoffice-bugs] [Bug 145365] Calc UI scrolls sheet tabs after renaming a tab

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145365

sarp...@aol.com changed:

   What|Removed |Added

Summary|Calc UI scrolls sheet tabs  |Calc UI scrolls sheet tabs
   |after renaming one  |after renaming a tab

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

[Libreoffice-bugs] [Bug 145365] New: Calc UI scrolls sheet tabs after renaming one

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145365

Bug ID: 145365
   Summary: Calc UI scrolls sheet tabs after renaming one
   Product: LibreOffice
   Version: 7.2.0.4 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sarp...@aol.com

Description:
I create a bunch of empty tabs, and start renaming them to the appropriate
names. So I scroll the first unnamed one to the left, so I can see which names
I've done as I work across the page and through the tabs. I hope.

But when I rename one, Calc scrolls my view so that the newly renamed tab is
all the way to the right, and I can't see the next one needing renaming.

It's possible this is regarded as desired behavior for some. For me there are
two problems. The first is that it moves something I'm working on, without my
permission or command, and requires me to quit working and scroll my work back
to where I put it. I have scroll bars to move the tabs with. There's no need
for the software to move them in this situation.

The second is that not only does it move my work, it actively hides it from me,
in a way that I can't really picture a use for. It would be one thing if this
were an incomplete feature, but this behavior seems intentional.

Is it possible there's an option to turn this behavior off that I haven't
found?

Steps to Reproduce:
1. Create enough new tabs to overflow the tab bar.
2. Rename enough tabs to overflow tab bar
3. Scroll the first default-named tab to the left
4. Select and rename the first default-named tab

Actual Results:
After step 4, the renamed tab moves all the way to the right, if there are
enough tabs before it, and the next tab after it is scrolled partially or
completely off the screen. Tabs renamed in the middle of the screen seem to
move around more or less at random, sometimes depending on the length of the
previous name.

Expected Results:
After step 4, the tabs stay scrolled where I left them, unless there is some
other reason to move them. But even if my new name is too long to display, I'd
still expect the tabs to remain where I had left them.

i.e. if the newly renamed tab is in the visible portion of the tab bar, don't
scroll the tabs at all. If the new name is too long for the visible portion,
I'd still prefer that the beginning stay visible (i.e. no scrolling) than
scrolling to the end of the name, or to the next tab.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.2.0.4 (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Libreoffice-commits] core.git: avmedia/source

2021-10-28 Thread Mike Kaganski (via logerrit)
 avmedia/source/framework/mediaitem.cxx |   22 ++
 avmedia/source/viewer/mediawindow_impl.cxx |9 +
 2 files changed, 15 insertions(+), 16 deletions(-)

New commits:
commit eee0b76a8c3dab62d1751db2f29f7f075c65b0c5
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:02:46 2021 +0300
Commit: Mike Kaganski 
CommitDate: Thu Oct 28 20:09:59 2021 +0200

Prepare for removal of non-const operator[] from Sequence in avmedia

Change-Id: Iefa86987f6ce43610177b7c4122744d37386ad6c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124335
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/avmedia/source/framework/mediaitem.cxx 
b/avmedia/source/framework/mediaitem.cxx
index b2b2b8d72b82..127ad8af243f 100644
--- a/avmedia/source/framework/mediaitem.cxx
+++ b/avmedia/source/framework/mediaitem.cxx
@@ -133,18 +133,16 @@ bool MediaItem::GetPresentation( SfxItemPresentation,
 
 bool MediaItem::QueryValue( css::uno::Any& rVal, sal_uInt8 ) const
 {
-uno::Sequence< uno::Any > aSeq( 10 );
-
-aSeq[ 0 ] <<= m_pImpl->m_URL;
-aSeq[ 1 ] <<= static_cast(m_pImpl->m_nMaskSet);
-aSeq[ 2 ] <<= static_cast< sal_Int32 >( m_pImpl->m_eState );
-aSeq[ 3 ] <<= m_pImpl->m_fTime;
-aSeq[ 4 ] <<= m_pImpl->m_fDuration;
-aSeq[ 5 ] <<= m_pImpl->m_nVolumeDB;
-aSeq[ 6 ] <<= m_pImpl->m_bLoop;
-aSeq[ 7 ] <<= m_pImpl->m_bMute;
-aSeq[ 8 ] <<= m_pImpl->m_eZoom;
-aSeq[ 9 ] <<= m_pImpl->m_sMimeType;
+uno::Sequence< uno::Any > aSeq{ uno::Any(m_pImpl->m_URL),
+
uno::Any(static_cast(m_pImpl->m_nMaskSet)),
+uno::Any(static_cast< sal_Int32 >( 
m_pImpl->m_eState )),
+uno::Any(m_pImpl->m_fTime),
+uno::Any(m_pImpl->m_fDuration),
+uno::Any(m_pImpl->m_nVolumeDB),
+uno::Any(m_pImpl->m_bLoop),
+uno::Any(m_pImpl->m_bMute),
+uno::Any(m_pImpl->m_eZoom),
+uno::Any(m_pImpl->m_sMimeType) };
 
 rVal <<= aSeq;
 
diff --git a/avmedia/source/viewer/mediawindow_impl.cxx 
b/avmedia/source/viewer/mediawindow_impl.cxx
index 2637eedf8147..fcc06488e913 100644
--- a/avmedia/source/viewer/mediawindow_impl.cxx
+++ b/avmedia/source/viewer/mediawindow_impl.cxx
@@ -415,7 +415,6 @@ void MediaWindowImpl::onURLChanged()
 if (mxPlayer.is())
 {
 Resize();
-uno::Sequence aArgs( 3 );
 uno::Reference xPlayerWindow;
 const Point aPoint;
 const Size aSize(mpChildWindow->GetSizePixel());
@@ -425,9 +424,11 @@ void MediaWindowImpl::onURLChanged()
 // tdf#139609 gtk doesn't need the handle, and fetching it is 
undesirable
 if (!pEnvData || pEnvData->toolkit != SystemEnvData::Toolkit::Gtk)
 nParentWindowHandle = mpChildWindow->GetParentWindowHandle();
-aArgs[0] <<= nParentWindowHandle;
-aArgs[1] <<= awt::Rectangle(aPoint.X(), aPoint.Y(), aSize.Width(), 
aSize.Height());
-aArgs[2] <<= reinterpret_cast(mpChildWindow.get());
+uno::Sequence aArgs{
+uno::Any(nParentWindowHandle),
+uno::Any(awt::Rectangle(aPoint.X(), aPoint.Y(), aSize.Width(), 
aSize.Height())),
+uno::Any(reinterpret_cast(mpChildWindow.get()))
+};
 
 try
 {


[Libreoffice-commits] core.git: accessibility/source

2021-10-28 Thread Mike Kaganski (via logerrit)
 accessibility/source/extended/AccessibleGridControlTable.cxx |3 -
 accessibility/source/extended/AccessibleGridControlTableBase.cxx |3 -
 accessibility/source/standard/vclxaccessiblemenuitem.cxx |   22 
+-
 3 files changed, 17 insertions(+), 11 deletions(-)

New commits:
commit ada320547db4c7ddbb05d10df4140ea988f29973
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:01:34 2021 +0300
Commit: Mike Kaganski 
CommitDate: Thu Oct 28 20:09:41 2021 +0200

Prepare for removal of non-const operator[] from Sequence in accessibility

Change-Id: I9454befb46767255451c490eab17e331eb8bb9dc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124334
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/accessibility/source/extended/AccessibleGridControlTable.cxx 
b/accessibility/source/extended/AccessibleGridControlTable.cxx
index ffb8108d0f24..8938ba83a122 100644
--- a/accessibility/source/extended/AccessibleGridControlTable.cxx
+++ b/accessibility/source/extended/AccessibleGridControlTable.cxx
@@ -238,8 +238,9 @@ void SAL_CALL 
AccessibleGridControlTable::selectAllAccessibleChildren()
 
 ensureIsAlive();
 Sequence< sal_Int32 > selectedRows = getSelectedAccessibleRows();
+auto selectedRowsRange = asNonConstRange(selectedRows);
 for(tools::Long i=0; i&
 {
 sal_Int32 const selectionCount( m_aTable.GetSelectedRowCount() );
 rSeq.realloc( selectionCount );
+auto pSeq = rSeq.getArray();
 for ( sal_Int32 i=0; i 
VCLXAccessibleMenuItem::getAccessibleActionKe
 {
 Reference< XAccessibleContext > xParentContext( 
xParent->getAccessibleContext() );
 if ( xParentContext.is() && xParentContext->getAccessibleRole() == 
AccessibleRole::MENU_BAR )
-aSeq1[0].Modifiers |= awt::KeyModifier::MOD2;
+aSeq1.getArray()[0].Modifiers |= awt::KeyModifier::MOD2;
 }
 pKeyBindingHelper->AddKeyBinding( aSeq1 );
 
@@ -490,14 +490,18 @@ Reference< XAccessibleKeyBinding > 
VCLXAccessibleMenuItem::getAccessibleActionKe
 static_cast< sal_Int16 >(aAccelKeyCode.GetFunction())
 }
 };
-if ( aAccelKeyCode.IsShift() )
-aSeq3[0].Modifiers |= awt::KeyModifier::SHIFT;
-if ( aAccelKeyCode.IsMod1() )
-aSeq3[0].Modifiers |= awt::KeyModifier::MOD1;
-if ( aAccelKeyCode.IsMod2() )
-aSeq3[0].Modifiers |= awt::KeyModifier::MOD2;
-if ( aAccelKeyCode.IsMod3() )
-aSeq3[0].Modifiers |= awt::KeyModifier::MOD3;
+if (aAccelKeyCode.GetModifier() != 0)
+{
+auto pSeq3 = aSeq3.getArray();
+if ( aAccelKeyCode.IsShift() )
+pSeq3[0].Modifiers |= awt::KeyModifier::SHIFT;
+if ( aAccelKeyCode.IsMod1() )
+pSeq3[0].Modifiers |= awt::KeyModifier::MOD1;
+if ( aAccelKeyCode.IsMod2() )
+pSeq3[0].Modifiers |= awt::KeyModifier::MOD2;
+if ( aAccelKeyCode.IsMod3() )
+pSeq3[0].Modifiers |= awt::KeyModifier::MOD3;
+}
 pKeyBindingHelper->AddKeyBinding( aSeq3 );
 }
 }


[Libreoffice-commits] core.git: 2 commits - basctl/source include/com include/comphelper include/oox include/toolkit include/vbahelper

2021-10-28 Thread Mike Kaganski (via logerrit)
 basctl/source/basicide/baside3.cxx   |3 ++-
 basctl/source/dlged/dlged.cxx|   20 
 basctl/source/dlged/dlgedobj.cxx |3 +--
 basctl/source/dlged/managelang.cxx   |3 ++-
 include/com/sun/star/uno/Sequence.hxx|3 ++-
 include/comphelper/sequence.hxx  |   10 ++
 include/oox/helper/containerhelper.hxx   |3 ++-
 include/toolkit/helper/macros.hxx|2 +-
 include/vbahelper/vbahelperinterface.hxx |7 +--
 9 files changed, 25 insertions(+), 29 deletions(-)

New commits:
commit dd97bfce9900e6bae40eece36124f8b22e70ff47
Author: Mike Kaganski 
AuthorDate: Thu Oct 28 16:03:49 2021 +0300
Commit: Mike Kaganski 
CommitDate: Thu Oct 28 20:09:27 2021 +0200

Prepare for removal of non-const operator[] from Sequence in basctl

Change-Id: Icc6ea4eea08a1cd3fffbfb211f420ab91602e8de
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124336
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/basctl/source/basicide/baside3.cxx 
b/basctl/source/basicide/baside3.cxx
index 085228971eae..23eb5ab1e0eb 100644
--- a/basctl/source/basicide/baside3.cxx
+++ b/basctl/source/basicide/baside3.cxx
@@ -1010,13 +1010,14 @@ bool implImportDialog(weld::Window* pWin, const 
ScriptDocument& rDocument, const
 if( nOnlyInImportLanguageCount > 1 )
 {
 Sequence< lang::Locale > aRemainingLocaleSeq( 
nOnlyInImportLanguageCount - 1 );
+auto pRemainingLocaleSeq = 
aRemainingLocaleSeq.getArray();
 lang::Locale aTmpLocale;
 int iSeq = 0;
 for( int i = 0 ; i < nOnlyInImportLanguageCount ; ++i )
 {
 aTmpLocale = aOnlyInImportLanguages[i];
 if( !localesAreEqual( aFirstLocale, aTmpLocale ) )
-aRemainingLocaleSeq[iSeq++] = aTmpLocale;
+pRemainingLocaleSeq[iSeq++] = aTmpLocale;
 }
 pCurMgr->handleAddLocales( aRemainingLocaleSeq );
 }
diff --git a/basctl/source/dlged/dlged.cxx b/basctl/source/dlged/dlged.cxx
index 203fa9cc44b9..13ff7a17ca36 100644
--- a/basctl/source/dlged/dlged.cxx
+++ b/basctl/source/dlged/dlged.cxx
@@ -182,8 +182,14 @@ DlgEditor::DlgEditor (
 ,pVScroll(nullptr)
 ,pDlgEdModel(new DlgEdModel())
 ,pDlgEdPage(new DlgEdPage(*pDlgEdModel))
-,m_ClipboardDataFlavors(1)
-,m_ClipboardDataFlavorsResource(2)
+// set clipboard data flavors
+,m_ClipboardDataFlavors{ { /* MimeType */ "application/vnd.sun.xml.dialog",
+   /* HumanPresentableName */ "Dialog 6.0",
+   /* DataType */ cppu::UnoType>::get() } }
+,m_ClipboardDataFlavorsResource{ m_ClipboardDataFlavors[0],
+ { /* MimeType */ 
"application/vnd.sun.xml.dialogwithresource",
+   /* HumanPresentableName */ "Dialog 8.0",
+   /* DataType */ cppu::UnoType>::get() } }
 ,pObjFac(new DlgEdFactory(xModel))
 ,rWindow(rWindow_)
 ,pFunc(new DlgEdFuncSelect(*this))
@@ -207,16 +213,6 @@ DlgEditor::DlgEditor (
 
 pDlgEdModel->InsertPage(pDlgEdPage);
 
-// set clipboard data flavors
-m_ClipboardDataFlavors[0].MimeType = 
"application/vnd.sun.xml.dialog" ;
-m_ClipboardDataFlavors[0].HumanPresentableName = "Dialog 6.0" ;
-m_ClipboardDataFlavors[0].DataType = cppu::UnoType>::get();
-
-m_ClipboardDataFlavorsResource[0] =  
m_ClipboardDataFlavors[0];
-m_ClipboardDataFlavorsResource[1].MimeType = 
"application/vnd.sun.xml.dialogwithresource" ;
-m_ClipboardDataFlavorsResource[1].HumanPresentableName = "Dialog 8.0" ;
-m_ClipboardDataFlavorsResource[1].DataType = 
cppu::UnoType>::get();
-
 aMarkIdle.SetInvokeHandler( LINK( this, DlgEditor, MarkTimeout ) );
 
 rWindow.SetMapMode( MapMode( MapUnit::Map100thMM ) );
diff --git a/basctl/source/dlged/dlgedobj.cxx b/basctl/source/dlged/dlgedobj.cxx
index 6353ddf9ecd6..c9ae1de4ae6e 100644
--- a/basctl/source/dlged/dlgedobj.cxx
+++ b/basctl/source/dlged/dlgedobj.cxx
@@ -1685,8 +1685,7 @@ void DlgEdObj::MakeDataAware( const Reference< 
frame::XModel >& xModel )
 aValue.Name = "BoundCell";
 aValue.Value <<= aApiAddress;
 
-Sequence< Any > aArgs( 1 );
-aArgs[ 0 ] <<= aValue;
+Sequence< Any > aArgs{ Any(aValue) };
 
 if ( xBindable.is() )
 {
diff --git a/basctl/source/dlged/managelang.cxx 
b/basctl/source/dlged/managelang.cxx
index d36c23803e7a..c7cd423cccee 100644
--- a/basctl/source/dlged/managelang.cxx
+++ b/basctl/source/dlged/managelang.cxx
@@ -162,12 +162,13 @@ IMPL_LINK_NOARG(ManageLanguageDialog, DeleteHdl, 
weld::Button&, void)
 

[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #2 from Adriano  ---
Yes, when formatting marks are enabled, the user should see clear marks for all
break types at the place of the break and should easily identify the break type
from those marks.
This will make breaks easier to work with, including deleting them.
Implementing this will improve the work with text in Writer.

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

[Libreoffice-ux-advise] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #2 from Adriano  ---
Yes, when formatting marks are enabled, the user should see clear marks for all
break types at the place of the break and should easily identify the break type
from those marks.
This will make breaks easier to work with, including deleting them.
Implementing this will improve the work with text in Writer.

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

[Libreoffice-bugs] [Bug 145364] New: calc problem with header

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145364

Bug ID: 145364
   Summary: calc problem with header
   Product: LibreOffice
   Version: 7.2.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: paolo...@gmail.com

Description:
chiedo scusa ma non parlo inglese. Riporto la traduzione con google.
Versione calc 7.2.2.2 su Kubuntu 18.04
non è possibile inserire testo nell'intestazione "area a sinistra". E' come se
nonm fosse attiva

I apologize but I don't speak English. I report the translation with google.
Calc version 7.2.2.2 on Kubuntu 18.04
it is not possible to insert text in the "left area" header. It is as if nonm
were active 

Actual Results:
formato
stile di pagina
intestazione
attiva riga di intestazione
modifica
area a sinistra (non attiva!)

Expected Results:
non è possibile scrivere nell'area  a sinistra


Reproducible: Always


User Profile Reset: No



Additional Info:
permettere di scrivere

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

[Libreoffice-bugs] [Bug 118734] FILEOPEN: Only one bookmark displayed in navigator instead of 2

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118734

--- Comment #8 from Dave Lovelace  ---
I tested this again, as requested.

If the comment starts at the same point as the bookmark, the comment still
vanishes.

However, IF the bookmark was INSIDE the selected text that the comment applies
to, then the bookmark remains.

Am I really the only one who uses both bookmarks and comments a lot?  It's
really hard for me to believe that fixing this has such low priority.  For me,
it's a MAJOR pain.  I need to be able to comment on things in my text, and also
to bookmark places so I can find them (and see them in sequence).

Version info:
Version: 7.1.6.2 (x64) / LibreOffice Community
Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

(There are many more deficiencies with bookmarks, some of which other people
have certainly complained about, BTW.  Whoever implemented them must not be
someone who actually uses them.)

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

[Libreoffice-bugs] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #1 from Tomaz Vajngerl  ---
I agree - the break aren't that easy to spot how we currently implement them.

Maybe we don't need to change the dotted line for the page/column break - just
add an additional break marker at the place of the break when formatting marks
are enabled.

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

[Libreoffice-ux-advise] [Bug 145351] Please make the visual indicators of breaks more practical

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145351

--- Comment #1 from Tomaz Vajngerl  ---
I agree - the break aren't that easy to spot how we currently implement them.

Maybe we don't need to change the dotted line for the page/column break - just
add an additional break marker at the place of the break when formatting marks
are enabled.

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

[Libreoffice-bugs] [Bug 145363] KDE Plasma: Enters loop when editing bullet style

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145363

David  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #3 from David  ---
7.x, 6.x, 7.3 alpha.  Appimages earlier than 6.x work, but the issue may have
only began though after upgrading to latest Debian Stable.

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-2021' - xmlsecurity/qa xmlsecurity/source

2021-10-28 Thread Tomaž Vajngerl (via logerrit)
 xmlsecurity/qa/unit/signing/signing.cxx   |  136 --
 xmlsecurity/source/helper/documentsignaturehelper.cxx |2 
 xmlsecurity/source/helper/ooxmlsecexporter.cxx|4 
 xmlsecurity/source/helper/xsecctl.cxx |   23 +--
 xmlsecurity/source/helper/xsecsign.cxx|   10 -
 5 files changed, 152 insertions(+), 23 deletions(-)

New commits:
commit b883bc9d8ca4a9c6037166b2eff09095aef145e0
Author: Tomaž Vajngerl 
AuthorDate: Wed Oct 27 14:15:17 2021 +0200
Commit: Tomaž Vajngerl 
CommitDate: Thu Oct 28 19:09:14 2021 +0200

xmlsec: signing the document fails the 3rd time (invalid signature)

Signing the document 3 or more times produces an invalid signature.
The cause of this is that xmlsec is confused because we have 3
signatures, which all have the same SignedProperties with the ID
"idSignedProperties", but it expect them to be unique.

This issue is fixed by making the ID unique with adding the ID of
the Signature to the SignedProperties ID, so this makes them unique
inside the same Signature.

Also UnsignedProperties have a unique ID usign the same approach,
but they aren't referenced - luckily.

Change-Id: I53c7249a82fc0623586548db9fa25bdc0e7c4101
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124278
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 
(cherry picked from commit fd5463343ab7f784070f1ab87a345eed20803d07)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124327
Tested-by: Jenkins CollaboraOffice 

diff --git a/xmlsecurity/qa/unit/signing/signing.cxx 
b/xmlsecurity/qa/unit/signing/signing.cxx
index 9695a84af3bf..3f632366bf94 100644
--- a/xmlsecurity/qa/unit/signing/signing.cxx
+++ b/xmlsecurity/qa/unit/signing/signing.cxx
@@ -937,13 +937,13 @@ CPPUNIT_TEST_FIXTURE(SigningTest, testXAdESNotype)
 // attribute", i.e. the signature without such an attribute was not 
preserved correctly.
 assertXPathNoAttribute(pXmlDoc,

"/odfds:document-signatures/dsig:Signature[1]/dsig:SignedInfo/"
-   "dsig:Reference[@URI='#idSignedProperties']",
+   "dsig:Reference[starts-with(@URI, 
'#idSignedProperties')]",
"Type");
 
 // New signature always has the Type attribute.
 assertXPath(pXmlDoc,
 "/odfds:document-signatures/dsig:Signature[2]/dsig:SignedInfo/"
-"dsig:Reference[@URI='#idSignedProperties']",
+"dsig:Reference[starts-with(@URI, '#idSignedProperties')]",
 "Type", "http://uri.etsi.org/01903#SignedProperties;);
 }
 
@@ -1002,12 +1002,132 @@ CPPUNIT_TEST_FIXTURE(SigningTest, testXAdES)
 // Assert that the digest of the signing certificate is included.
 assertXPath(pXmlDoc, "//xd:CertDigest", 1);
 
-// Assert that the Type attribute on the idSignedProperties reference is
-// not missing.
-assertXPath(pXmlDoc,
-"/odfds:document-signatures/dsig:Signature/dsig:SignedInfo/"
-"dsig:Reference[@URI='#idSignedProperties']",
-"Type", "http://uri.etsi.org/01903#SignedProperties;);
+// Assert that the Type attribute is set on all URI's that start with 
#idSignedProperties
+assertXPath(pXmlDoc, "//dsig:Reference[starts-with(@URI, 
'#idSignedProperties')]", "Type",
+"http://uri.etsi.org/01903#SignedProperties;);
+}
+
+CPPUNIT_TEST_FIXTURE(SigningTest, testSigningMultipleTimes_ODT)
+{
+createDoc("");
+
+utl::TempFile aTempFile;
+aTempFile.EnableKillingFile();
+uno::Reference xStorable(mxComponent, uno::UNO_QUERY);
+utl::MediaDescriptor aMediaDescriptor;
+aMediaDescriptor["FilterName"] <<= OUString("writer8");
+xStorable->storeAsURL(aTempFile.GetURL(), 
aMediaDescriptor.getAsConstPropertyValueList());
+
+DocumentSignatureManager aManager(mxComponentContext, 
DocumentSignatureMode::Content);
+CPPUNIT_ASSERT(aManager.init());
+uno::Reference xStorage
+= comphelper::OStorageHelper::GetStorageOfFormatFromURL(
+ZIP_STORAGE_FORMAT_STRING, aTempFile.GetURL(), 
embed::ElementModes::READWRITE);
+CPPUNIT_ASSERT(xStorage.is());
+aManager.setStore(xStorage);
+aManager.getSignatureHelper().SetStorage(xStorage, "1.2");
+
+// Create a signature.
+uno::Reference xCertificate
+= getCertificate(aManager, svl::crypto::SignatureMethodAlgorithm::RSA);
+if (!xCertificate.is())
+return;
+sal_Int32 nSecurityId;
+aManager.add(xCertificate, mxSecurityContext, /*rDescription=*/OUString(), 
nSecurityId,
+ /*bAdESCompliant=*/true);
+
+// Read back the signature and make sure that it's valid.
+aManager.read(/*bUseTempStream=*/true);
+{
+std::vector& rInformations
+= aManager.getCurrentSignatureInformations();
+CPPUNIT_ASSERT_EQUAL(static_cast(1), 

[Libreoffice-bugs] [Bug 144625] Regression: a macro stopped working with upgrade of LO.

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144625

--- Comment #7 from Michael Warner  ---
You will need to reduce your test case down to the smallest possible thing that
demonstrates the issue. It can't be reliant on the existence of other paths or
system configuration that doesn't contribute to testing this specific issue at
hand.

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

[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145357

Leon  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Leon  ---
(In reply to Regina Henschel from comment #9)
> If you use View > Value Highlighting, then text is black, numbers are blue
> and formulas are green. In that mode you see, that cell content in E3:E10
> and G3:G10 is text.
> 
> Changes in cell format on existing content cannot be used for changes
> between data type text and data type number.
> 
> To change existing 'text with decimal point' to 'number with comma
> separator', you can do these steps:
> 1. cut the text to clipboard
> 2. Format the (still marked) cells to "General". That is in Format > Cells >
> Tab numbers. Make sure the field 'language' in that tab is correct.
> 3. (cells still marked) Use the item "Unformated text (TSV-Calc)" from the
> drop-down list of the 'Paste' button in the toolbar. You get the "Text
> Import" dialog.
> 4. In that dialog click on column header (shows "Standard" as default) in
> the section 'Fields' and then select item "US English" in field 'Column
> type'. OK.
> 
> To change the display of the formula result in cell E11 to "number with
> comma separator", go to Format > Cell > Tab numbers. Change the language to
> -in your case- "English (South Africa)".
> 
> Do all your tries on a copy of the document!
> 
> For more assistance in formatting and data type handling in Calc please use
> user mailing list or Ask.
> 
> For me this is not a bug.

thanks. I basically simply do a mass replace of period to comma. I am unable to
find the place where it is set as a dot. It did not used to exhibit this
behaviour so I am not sure where this chnaged in the locale settings.

Will close because it basically is a formatting issue where commas must be
used, and not periods as decimal separator.

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

[Libreoffice-bugs] [Bug 145357] SUM function does not calculate values

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145357

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de

--- Comment #9 from Regina Henschel  ---
If you use View > Value Highlighting, then text is black, numbers are blue and
formulas are green. In that mode you see, that cell content in E3:E10 and
G3:G10 is text.

Changes in cell format on existing content cannot be used for changes between
data type text and data type number.

To change existing 'text with decimal point' to 'number with comma separator',
you can do these steps:
1. cut the text to clipboard
2. Format the (still marked) cells to "General". That is in Format > Cells >
Tab numbers. Make sure the field 'language' in that tab is correct.
3. (cells still marked) Use the item "Unformated text (TSV-Calc)" from the
drop-down list of the 'Paste' button in the toolbar. You get the "Text Import"
dialog.
4. In that dialog click on column header (shows "Standard" as default) in the
section 'Fields' and then select item "US English" in field 'Column type'. OK.

To change the display of the formula result in cell E11 to "number with comma
separator", go to Format > Cell > Tab numbers. Change the language to -in your
case- "English (South Africa)".

Do all your tries on a copy of the document!

For more assistance in formatting and data type handling in Calc please use
user mailing list or Ask.

For me this is not a bug.

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

[Libreoffice-commits] core.git: svx/uiconfig

2021-10-28 Thread Caolán McNamara (via logerrit)
 svx/uiconfig/ui/toolbarpopover.ui |2 --
 1 file changed, 2 deletions(-)

New commits:
commit a93329244a7d24b8a89d8f287b6123e56d13786d
Author: Caolán McNamara 
AuthorDate: Thu Oct 28 14:23:36 2021 +0100
Commit: Caolán McNamara 
CommitDate: Thu Oct 28 18:14:05 2021 +0200

gtk[3 vs 4]: remove can-focus entirely from toolbarpopover.ui

so tab-cycling inside sidebar popovers work as wanted

In gtk3 a can-focus of True means that tab-cycling doesn't work
correctly as the container is seen as a candidate itself

In gtk4 a can-focus of False means that focus cannot enter any
child of it.

So it needs to be false for gtk3 and true for gtk4, leaving it
unspecified gets a desired working default.

Change-Id: I423094657854ed02bc28496dfc9a30efa1e945da
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124338
Tested-by: Caolán McNamara 
Reviewed-by: Caolán McNamara 

diff --git a/svx/uiconfig/ui/toolbarpopover.ui 
b/svx/uiconfig/ui/toolbarpopover.ui
index 3a0f83bf3405..d7684d73ebe7 100644
--- a/svx/uiconfig/ui/toolbarpopover.ui
+++ b/svx/uiconfig/ui/toolbarpopover.ui
@@ -3,13 +3,11 @@
 
   
   
-True
 True
 4
 
   
 True
-True
 vertical
 6
 


Re: ESC meeting minutes: 2021-10-28

2021-10-28 Thread Luboš Luňák
On Thursday 28 of October 2021, Stephan Bergmann wrote:
> + tests that failed more than twice in last seven days
>3 CppunitTest_sc_ucalc_copypaste   gerrit_windows
>3 CppunitTest_smoketestgerrit_linux_clang_dbgutil
>3 CppunitTest_xmlsecurity_signing  
> gerrit_linux_clang_dbgutil
>3 UITest_calc_tests8   gerrit_linux_clang_dbgutil
>3 UITest_writer_tests3 gerrit_linux_clang_dbgutil
>4 CppunitTest_sc_ucalc_sharedformula   gerrit_windows
>6 UITest_writer_tests7 gerrit_linux_clang_dbgutil
>   15 Killed by the kill-wrapper   gerrit_linux_clang_dbgutil

 FWIW, I think those Calc Windows failures were all tb68-bytemark failing on 
illegal instruction, and https://gerrit.libreoffice.org/c/core/+/124249 has 
already taken care of it.

 Had nobody noticed that before? It seems likely that tb68-bytemark was 
consistently failing every master build since May.

-- 
 Luboš Luňák
 l.lu...@collabora.com


[Libreoffice-bugs] [Bug 145285] Cannot export: Exporting Drawing Crashes EVERY time on macOS

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145285

steve  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #11 from steve  ---
No trouble exporting with 7.3 nightly build.
Retested 7.2.2.2 with sample file:

- open Export crashes trying to export the 3rd page as JPEG
- select page 3
- select file > export
- switch `File type` to jpeg and press enter to save
- confirm default export options

no trouble at all, jpg exported as expected.

Do you have access to a second mac at a friends or neighbours? Would be curious
if it works there, but it does not seem to be a general problem in LibreOffice
or your file, as export here works fine in both versions of LO. So it is
something profile or machine specific with your setup.

Lets wait how the nightly behaves for you.

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

[Libreoffice-bugs] [Bug 145363] KDE Plasma: Enters loop when editing bullet style

2021-10-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145363

BogdanB  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

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

  1   2   3   >