[Bug 143887] Errormessage give unusable information for normal user - most content for developer

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143887

--- Comment #4 from Robert Großkopf  ---
Behavior is still the same in LO 24.2.3.2 on OpenSUSE 15.6 64bit rpm Linux.

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

core.git: accessibility/source

2024-05-19 Thread HakimOttey (via logerrit)
 accessibility/source/extended/accessibletabbar.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit ad3f86880bd6f5a0800a2820177715dc88c13a3c
Author: HakimOttey 
AuthorDate: Wed May 1 17:45:38 2024 -0400
Commit: Michael Weghorn 
CommitDate: Mon May 20 07:47:44 2024 +0200

Change for loop to have getAccessibleChildCount in accessibletabbar

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

diff --git a/accessibility/source/extended/accessibletabbar.cxx 
b/accessibility/source/extended/accessibletabbar.cxx
index 711d2a7b8c5c..beae5dd61331 100644
--- a/accessibility/source/extended/accessibletabbar.cxx
+++ b/accessibility/source/extended/accessibletabbar.cxx
@@ -358,7 +358,7 @@ namespace accessibility
 OExternalLockGuard aGuard( this );
 
 Reference< XAccessible > xChild;
-for ( size_t i = 0; i < m_aAccessibleChildren.size(); ++i )
+for( sal_Int64 i = 0; i < getAccessibleChildCount(); ++i )
 {
 Reference< XAccessible > xAcc = getAccessibleChild( i );
 if ( xAcc.is() )


Re: Build fail in mariadb on fedora 40

2024-05-19 Thread Heiko Tietze

On 18.05.24 2:51 PM, Dr. David Alan Gilbert wrote:

It looks like others started hitting it; see:
   https://gerrit.libreoffice.org/c/core/+/167806
Run into the same issue on a VM with Arch Linux. Latest master compiles now 
flawless.


OpenPGP_signature.asc
Description: OpenPGP digital signature


GSoC Project Introduction: More and Better Tests

2024-05-19 Thread Adam Seskunas
Hello Everyone,

My name is Adam Seskunas and I'm one of the GSoC contributors for
LibreOffice. My project, as the name suggests, is to write more and better
tests for LibreOffice. In particular, I will be focusing on writing filter
tests for writer.  The project will consist of two main parts, the first of
which will be to convert some JUnit tests to CppUnit, and the second part
will consist of writing missing unit tests.  A more detailed description as
well as a link to the project proposal can be found here
https://summerofcode.withgoogle.com/myprojects/details/pUU5JIpy

I'd like to take this opportunity to thank Hossein and Xisco for agreeing
to mentor me through the project. And I'd like to give a big thanks to
Ilmari for helping me get involved with LibreOffice over the past year and
encouraging me to apply for the GSoC. And last of all, a big thanks to all
of the community members, everyone has been welcoming and friendly, it's
been a very positive experience contributing to LibreOffice.

In the next week I will be working on refining the list of tests I will be
working on and gathering information about each test I plan to work on. In
my next update I hope to have a finalized list of tests to publish.

Adam Seskunas


[Bug 145673] UI: comment box doesn't expand while typing (scrollbar instead)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145673

--- Comment #9 from Mohit Marathe  ---
(In reply to Heiko Tietze from comment #7)
> Guess it's just a tricky implementation to expand while typing if there is
> sufficient space. It would improve UX but is not crucial.

Hello,

Currently, I'm working on this and am curious as to what is the consensus on
this? Should we stick to scrollbar? I think expanding the comment box (as
required) will surely improve the UX (although I still have to figure out how
will I do that).

Thanks,
Mohit

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

[Bug 91723] UI: File Properties Dialog width changes with length of Created and Modified

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91723

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
Can't reproduce in:

Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Nor in 7.5.0.3.

With no name filled into the Options dialog, the File > Properties dialog has
only one row of tabs, even with the minimal 1024x768 resolution[1].

I then used the name "My first name is very very long My last name is also very
very long", and the text can fit in between the buttons now. Looks like the
dialog was re-organised at some stage.

Gordo and Martin, what resolution do you use? Is this still an issue in
currently-maintained versions?

[1]: https://www.libreoffice.org/get-help/system-requirements/

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

[Bug 157871] Inconsistent drag selection vs drag and drop of hyperlink for gtk3 and osx VCL plugins

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157871

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
(In reply to ToanTran from comment #2)
> It is consistently reproducible for me with the mentioned steps above
> 
> Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
> Build ID: b5d194d1d37131f921853b78d659c63178de2bc6
> CPU threads: 8; OS: macOS 13.2.1; UI render: Skia/Metal; VCL: osx
> Locale: en-US (en_VN.UTF-8); UI: en-US
> Calc: threaded

ToanTran, can you please clarify what you mean by "consistently reproducible"?
Because the symptoms are not consistent for me: sometimes it drags-and-drops
the hyperlink, sometimes it selects characters. Which is the issue.
If it only moves the hyperlink, then that's what's observed with most VCL
plugins in bug 39015.

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

[Bug 161179] New: contains all the string

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161179

Bug ID: 161179
   Summary: contains all the string
   Product: Document Liberation Project
   Version: unspecified
  Hardware: PowerPC
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: General
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: devendra.singh94...@gmail.com

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

[Bug 160933] Writer does not follow the link to open document

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160933

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Bug 160936] Draw freezes after save until forced context switch or timeout.

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160936

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160933] Writer does not follow the link to open document

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160933

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Bug 160933] Writer does not follow the link to open document

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160933

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

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

[Bug 160940] Some shapes were wrongly imported from CDR files by Government of Serbia

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160940

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 157870] Office simply freezes and shuts down without warning

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157870

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 157870] Office simply freezes and shuts down without warning

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157870

--- Comment #3 from QA Administrators  ---
Dear Caroll Reimer,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Bug 34552] EDITING: Calc loses row height value when modifying a cell

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34552

--- Comment #26 from QA Administrators  ---
Dear Christopher M. Penalver,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 96802] Android Viewer does not switch edit mode to viewer mode on odp

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96802

--- Comment #5 from QA Administrators  ---
Dear Gülşah Köse,

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Bug 98986] Mailmerge - modifying documents with "Edit Individual Documents" before sending/printing is not possible from 5.2

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98986

--- Comment #7 from QA Administrators  ---
Dear Oliver Specht (CIB),

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 147426] Media sidebars Position and time items not updating while playing media file

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147426

--- Comment #4 from QA Administrators  ---
Dear Gabor Kelemen (allotropia),

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 145894] external/python3 FTBFS on arm64 linux

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145894

--- Comment #4 from QA Administrators  ---
Dear Jiaxun Yang,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 143887] Errormessage give unusable information for normal user - most content for developer

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143887

--- Comment #3 from QA Administrators  ---
Dear Robert Großkopf,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 133108] Shortcut for "Default Paragraph" has no effect (Strg + Umschalt + 0)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133108

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 161177] Function EXPREG not escape dot character correctly

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161177

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m_a_riosv  ---
Please what is your decimal separator '.' or ','

Please attach a sample file, reduce the size as much as possible without
private information, and paste the information in Menu/Help/About LibreOffice,
there is a copy icon.

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

[Bug 161018] EDITING Calc says "adapt row height" for a short amount of time whenever I select a cell

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161018

m_a_riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   Keywords||bibisectRequest, regression

--- Comment #6 from m_a_riosv  ---
Not reproducible with
Version: 24.2.0.0.alpha1 (X86_64) / LibreOffice Community
Build ID: 06946980c858649160c634007e5fac9a5aa81f38
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 160634] Alternate substitution feature does not work when AAT tables are present in font

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160634

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|REOPENED|UNCONFIRMED
 Ever confirmed|1   |0

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

[Bug 135066] Frozen UI or Crash when interacting with embedded OLE object's Tabbed UI after re-entering edit mode if containing document uses classic toolbar UI

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135066

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
*** Bug 135213 has been marked as a duplicate of this bug. ***

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

[Bug 133092] [META] Crash bugs

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|135213  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=135213
[Bug 135213] Crash: Select Hyperlink from Tab. Text document is imported from
Other application.(i.e. impress)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 135213] Crash: Select Hyperlink from Tab. Text document is imported from Other application.(i.e. impress)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135213

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=13 |
   |5066|
 Blocks|133092  |
 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |DUPLICATE
 Status|NEEDINFO|RESOLVED

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
Fixed in 7.2 by 9f06c54ca1819b6d4df48f33772cfa5ceb90dccd (and reproduced right
before it). Please see bug 135066 comment 7 for details.

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


Referenced Bugs:

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

[Bug 160634] Alternate substitution feature does not work when AAT tables are present in font

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160634

--- Comment #12 from Y. Kawara  ---
Sorry, I meant AAT and OpenType tables.

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

[Bug 161018] EDITING Calc says "adapt row height" for a short amount of time whenever I select a cell

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161018

--- Comment #5 from m_a_riosv  ---
Created attachment 194207
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194207=edit
Sample file modified.

I can see it with
Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

But I think it has something to do in how the sheet is formatted.

Applying a direct format for the font to an entire column, make that all cells
in the column has that format not only the cells with data, what induces LO to
recalculate the row heights.
In your file, the entire sheet has a direct format for the font.

Test cleaning the direct format [Ctrl+M] for the rows below the last data, in
your sample file, from row 19 up to the last.

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

[Bug 108589] [META] OLE/Embedded object edit transition mode issues

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108589

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||135066


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=135066
[Bug 135066] Frozen UI or Crash when interacting with embedded OLE object's
Tabbed UI after re-entering edit mode if containing document uses classic
toolbar UI
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107237] [META] Notebookbar Tabbed

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107237

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||135066


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=135066
[Bug 135066] Frozen UI or Crash when interacting with embedded OLE object's
Tabbed UI after re-entering edit mode if containing document uses classic
toolbar UI
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108589] [META] OLE/Embedded object edit transition mode issues

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108589
Bug 108589 depends on bug 135066, which changed state.

Bug 135066 Summary: Frozen UI or Crash when interacting with embedded OLE 
object's Tabbed UI after re-entering edit mode if containing document uses 
classic toolbar UI
https://bugs.documentfoundation.org/show_bug.cgi?id=135066

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Bug 107237] [META] Notebookbar Tabbed

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107237
Bug 107237 depends on bug 135066, which changed state.

Bug 135066 Summary: Frozen UI or Crash when interacting with embedded OLE 
object's Tabbed UI after re-entering edit mode if containing document uses 
classic toolbar UI
https://bugs.documentfoundation.org/show_bug.cgi?id=135066

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Bug 133092] [META] Crash bugs

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 135066, which changed state.

Bug 135066 Summary: Frozen UI or Crash when interacting with embedded OLE 
object's Tabbed UI after re-entering edit mode if containing document uses 
classic toolbar UI
https://bugs.documentfoundation.org/show_bug.cgi?id=135066

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Bug 135066] Frozen UI or Crash when interacting with embedded OLE object's Tabbed UI after re-entering edit mode if containing document uses classic toolbar UI

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135066

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

  Component|Impress |UI
 Whiteboard||target:7.2.0
   Severity|normal  |critical
 Status|NEW |RESOLVED
 CC||stephane.guillou@libreoffic
   ||e.org,
   ||szymon.k...@collabora.com
Crash report or||["libgobject-2.0.so.0.7200.
crash signature||4","SfxDispatcher::GetFrame
   ||","libc.so.6"]
Summary|Freeze UI and Crash: Insert |Frozen UI or Crash when
   |secondly table from Tab on  |interacting with embedded
   |writer document that is |OLE object's Tabbed UI
   |inserted impress|after re-entering edit mode
   ||if containing document uses
   ||classic toolbar UI
 Resolution|--- |FIXED
 Blocks||107237, 108589

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
Tested in 7.0.0.3:

- all components with classic toolbar interface: not reproduced
- all components with tabbed UI: not reproduced
- only Impress with tabbed UI: not reproduced
- only Writer with tabbed UI: reproduced, with crash signature
"libgobject-2.0.so.0.7200.4" when killed after hang ->
https://crashreport.libreoffice.org/stats/crash_details/30b3ea38-d22f-4823-b86e-1804f3010db3
- the other way around (only Impress with tabbed UI, inserting Presentation OLE
object in Writer document, inserting two tables successively), I reproduce the
same thing.

Note that:
- you don't even need to insert a first table: even without editing the object
in the first instance, the hang happens after re-entering edit mode.
- also happens between other components (e.g. Calc + Writer), so not
Impress-specific
- also happens with other kinds of interaction with the tabbed UI. For example,
when inserting an image in a Presentation OLE object when Calc uses classic
toolbars, I get a crash signature "SfxDispatcher::GetFrame":
https://crashreport.libreoffice.org/stats/crash_details/5d8a8edb-f4a0-4455-a97c-63f679c0f555

In 7.1, I get direct crash with signature "libc.so.6":
https://crashreport.libreoffice.org/stats/crash_details/de4ad25d-56d1-402c-8f24-7cbaa697f9d5

Not reproduced in 7.2.0.4 nor in a recent daily build:

Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 1b45ca1aa7d7cb8e7adcc07f8c60e26a413eca8c
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

Fix bibisected with linux-64-7.2 to first _good_ build
[7052746687af637a721d0d16c814a9769f887993] which points to:

commit  9f06c54ca1819b6d4df48f33772cfa5ceb90dccd
author  Szymon Kłos Tue Apr 06 07:08:30 2021 +0200
committer   Szymon Kłos Mon Apr 19 08:37:31 2021 +0200
notebookbar: minify for online
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/114154

Thanks Szymon!


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107237
[Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=108589
[Bug 108589] [META] OLE/Embedded object edit transition mode issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160634] Alternate substitution feature does not work when AAT tables are present in font

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160634

--- Comment #11 from Y. Kawara  ---
To the previous message I would like to stress that there is a good reason to
both have ATT and GSUB tables, as not all features exist in both sets, as seen
from the N/A features described there:

https://fontforge.org/docs/techref/gposgsub.html#gposgsub-conversion

In that sense, I think LibreOffice UI's (and Inkscape's) approach at reading
tables and enabling features is correct.

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

[Bug 161176] Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

--- Comment #5 from m_a_riosv  ---
Created attachment 194206
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194206=edit
PDF printed with Microsoft print to PDF

I can't reproduce the issue.
Neither through print to 'Microsoft print to PDF', or Menu/File/Export
as/Export as PDF.

Please test in safe mode, Menu/Help/Restart in Safe Mode

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

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #13 from ady  ---
(In reply to Theo from comment #11)
> Created attachment 194202 [details]
> test spreadsheet with unprotected macro library

No crash with this test2. I made 3 copies of this file.

I first used LO 7.6.6. Open test2.ods (original), follow steps from comment 0.
no crash.

I repeated the steps using LO 24.2.3.2, also with (a copy of) the original
test2.ods. No crash.

Then I take the third copy of test2.ods, open it with LO 7.6.6, add a password
as in comment 0, save the file, close LO 7.6.6., open the saved-file with LO
24.2.3.2, remove the password as described in comment 5, save, close, reload.
No crash.

There is a delay (with no clues/hints to the user) after each password (re-)set
and I have to be patient, but no crash.

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

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #12 from Stéphane Guillou (stragu) 
 ---
(In reply to Theo from comment #11)
> Created attachment 194202 [details]
> test spreadsheet with unprotected macro library
Thanks. If I test with this file, I only get a short hang: set password, save,
close, open, remove password -> hang for a few seconds, but eventually
finishes.
Whereas with attachment 194193, I eventually kill LO as it doesn't look it'll
ever finish it. (No high CPU or memory use though.)

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

[Bug 161046] No substitute fonts when opening a file without the file's font installed locally

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161046

--- Comment #3 from Jon  ---
I have discovered that this problem appears to only occur when installing from
the rpm on LibreOffice's site. It did not occur when I installed it from
Fedora's respository.

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

[Bug 160754] Add UI to control NoGapAfterNoteNumber compatibility flag

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160754

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Footnote indent is broken   |Add UI to control
   |in this example |NoGapAfterNoteNumber
   ||compatibility flag
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
Let's change the focus of the report to "Add UI to control NoGapAfterNoteNumber
compatibility flag" then.

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

Re: Compiling nearly every file now compiles sqlbison.cxx and/or sqlflex.cxx

2024-05-19 Thread Patrick Luby


> On May 19, 2024, at 4:37 PM, Caolán McNamara  
> wrote:
> 
> On Sun, 2024-05-19 at 16:30 -0400, Patrick Luby wrote:
>> cd vcl && touch skia/gdiimpl.cxx && make
> 
> maybe adding -d to the end of the make might give a hint as to what
> could be going on

I did a make -d and no sql* files were listed as dependencies. Then I edited 
config_host.mk and added -E to clang++ everywhere, did "cd vcl && touch 
skia/gdiimpl.cxx && make”, looked at the .o file, and no sql* includes.

So, I just did a git bisect and found that commit 
0cf755adbb39591e9f6d273bfe5dce2469a86dbf causes this behaviour. Pretty wild 
that undefining _FORTIFY_SOURCE causes all these warnings.

Any ideas? I’d like to just wrap a push/pop —implicit-fallthrough around 
whatever code compiles these sql* files.

Patrick




[Bug 161178] Inserting text objets over image messes the result on every reopening

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161178

--- Comment #2 from philippe  ---
Created attachment 194205
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194205=edit
The document which shows the problem (chapter 4.2... almost images show the
problem)

I attached my original file which makes the problem all the time (but it does
it with all me other files, for the other ones I anded up using Word which
works great doing the same thing).

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

[Bug 161178] Inserting text objets over image messes the result on every reopening

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161178

--- Comment #1 from philippe  ---
Created attachment 194204
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194204=edit
Shows that 2 and 4 have moved (they were over the image) 6 and 7 have gone
under the image (which was before below everything)

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

[Bug 161178] New: Inserting text objets over image messes the result on every reopening

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161178

Bug ID: 161178
   Summary: Inserting text objets over image messes the result on
every reopening
   Product: LibreOffice
   Version: 24.2.3.2 release
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: philippem...@outlook.com

Description:
I've inserted an image in my document (as anchored to a character) and added
text objects over the image (achored to the same character). The text objects
are over the image. I save and close and reopen and some of the text objects
have moved or are under the image. I always have to review all my images for
the same reason.

It happens on 24.2.3.2 but it happened with ALL previous versions (just updated
to the very latest see it is works better).

Steps to Reproduce:
1.Insert an image
2.Add several text objects over the image
3.Save and close document
4.Reopen, normally some of the the text objects have moved or have gone under
the image, you must review all of them all the time.

Actual Results:
Objects move by themselves and Zorder is changed

Expected Results:
The objects stay where they were put and the zorder doesn't change


Reproducible: Always


User Profile Reset: No

Additional Info:
I could send an image showing the result AFTER reopening, I can do it with
almost all my images with text objects and every time I reopen the document.
I'm considering creating an image outside of LO because I'm tired of fixing the
same things again and again, better create a fixed bitmap but that would be
accepting to be defeated. Just can't believe it doesn't happen to the others.

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

[Bug 161018] EDITING Calc says "adapt row height" for a short amount of time whenever I select a cell

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161018

--- Comment #4 from aer0a...@gmail.com ---
Created attachment 194203
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194203=edit
One of the spreadsheets where this bug happened

I've attached a sample file of one of the spreadsheets where this bug happened

Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 2; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-AU (en_AU); UI: en-GB
Calc: CL threaded

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

[Bug 161018] EDITING Calc says "adapt row height" for a short amount of time whenever I select a cell

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161018

--- Comment #3 from aer0a...@gmail.com ---
The bug usually starts when I change the font for a column

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

[Bug 161177] New: Function EXPREG not escape dot character correctly

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161177

Bug ID: 161177
   Summary: Function EXPREG not escape dot character correctly
   Product: LibreOffice
   Version: 24.2.3.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: aldrinpdscas...@gmail.com

Description:
Function EXPREG don't treat escape dot character correctly in regex.

Steps to Reproduce:
1. Put a cell the value 0.
2. In another cell use this formula escaping dot:
EXPREG(cell;"[0-9]+(\.[0-9]+)?")

Expected Results:
0.


Reproducible: Always


User Profile Reset: No

Additional Info:
If take out the metacharacter to scape and use only dot it is works.

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

[Bug 160754] Footnote indent is broken in this example

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160754

--- Comment #9 from Dan  ---
Regarding the workaround of "Tools->Footnote/Endnote Settings, and add a space
in the 'After' field", it works while you are editing the document. Save and
reopen the document and you have to do it again...

So, the only way I know to fix the problem is to select all, create an empty
document, paste everything into the empty document and move forward from there.
The ability to flip the MS compatibility flag would be nice.

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

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #11 from Theo  ---
Created attachment 194202
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194202=edit
test spreadsheet with unprotected macro library

I created test2.ods in the same way as test.ods: an empty spreadsheet with the
macro library imported.
The only difference compared to test.ods should be that in test2.ods the macro
library is not password protected. For the rest the files should be identical.

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

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #10 from Theo  ---
In response to comment #9:
The file in the attachment was just created today; an empty spreadsheet, just
with the macro library imported from the actual file. 

The source is a rather complex spreadsheet that has a history going back to
2015. 

In the test file I protected the macro library with the password ‘test’
(without the quotes obviously).

I’ll make a second test file with the same library but then not password
protected.  

I can confirm that I can use the original spreadsheet in the intended way, that
is with password protection, without any issues with versions 7.x

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

[Bug 54743] [FORMATTING] Shift+F3 works unexpected (uppercase and lowercase)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=54743

--- Comment #16 from Mihail Balabanov  ---
Re-confirmed with Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: bg-BG (bg_BG); UI: bg-BG
Calc: CL threaded

The cycling appears to depend on an global internal counter and not on the
state of the selected text/the text containing the cursor. In a new document, I
type

example
Example

Then I cycle the first line like this:

example -> Example -> Example -> EXAMPLE -> example

The internal counter is now primed for Title Case. At this point, I try to
cycle the second line and I get:

Example -> Example -> Example -> EXAMPLE -> example

The first two presses of F3 don't change the word (they are, respectively,
Title Case and Sentence case), giving the impression that the feature is not
working. The expected result is to detect the current state of the selected
text and to continue cycling from that state onward regardless of any previous
cycle case operation on another selection, so:

Example -> EXAMPLE -> example -> Example -> ...

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

[Bug 161162] visual glitch on tabbed user interface

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161162

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Not reproduced with Ubuntu 22.04 + GNOME 42.9, 150% fractional scaling and:

Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Can you please share a screenshot of the issue, and more details about your
desktop environment and windowing system / compositor?

Thank you!

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

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
(In reply to ady from comment #7)
> While I can replicate the crash in LO 24.2.3.2 when starting with attachment
> 194193 [details], which already has a password for the macro library, I was
> trying to replicate the complete procedure, starting with no password,
> setting a password, and _then_ removing it.
> 
> I tried to reproduce the steps using attachment 194193 [details] with LO
> 7.6.6. The Old Password ("test") is not accepted, so the rest of the details
> don't matter.
> 
> Since this procedure failed for me (i.e. old password not accepted in LO
> 7.6.6), I am now wondering whether the problem could be related to the
> changes to encryption that were introduced for LO 24.2.
I was commenting at the same time, and see the same results.
The files meta.xml shows the file was last saved with LO 24.2.2.

Theo, do you have more details on the history the file went through? Would be
good to know how we can reproduce from scratch.

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

[Bug 108914] [META] Password protected file bugs and enhancements

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108914

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160888


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160888
[Bug 160888] Cannot unprotect protected macro library (hang)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160888] Cannot unprotect protected macro library (hang)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=10
   ||5844
 CC||michael.st...@allotropia.de
 Ever confirmed|0   |1
Summary|Cannot unprotect protected  |Cannot unprotect protected
   |macro library   |macro library (hang)
Version|24.2.2.2 release|24.2.0.1 rc
   Keywords||bibisected, bisected,
   ||regression
  Regression By||Michael Stahl
 OS|macOS (All) |All
 Blocks||108914
 Status|UNCONFIRMED |NEW
   Hardware|ARM |All

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
(In reply to Theo from comment #4)
> Created attachment 194193 [details]
> test spreadsheet with macro libraries included
With the sample file, I get a hang when trying to remove the password from
LocalAddOns.

Repro in recent daily build and:

Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

In 7.6.7.2, using "test" as the password would result in "Invalid password"
(are you sure you used that password?), but no freeze. I don't know why it is
considered invalid, but at least the hang is a regression.

Bibisected with linux-64-24.2 repo to first bad build
[1921ab0d30238da3949395ee4c2450a264a69568] which points to
4995e0669da0e499743b21c60da1ca8b14a1c78c which is a cherrypick of:

commit  2f512aaa6c39390a5a0eb1d1e37f070127d068a4
author  Michael Stahl   Tue Dec 19 19:13:00 2023 +0100
committer   Michael Stahl   Wed Dec 20 18:29:36 2023 +0100
tdf#105844 offapi,package,sfx2: use Argon2 for wholesome ODF encryption
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161009

Michael, can you please have a look?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108914
[Bug 108914] [META] Password protected file bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 161169] Login Screen shown incorrect error message

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161169

LeroyG  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #2 from LeroyG  ---
What the message say?

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

[Bug 161169] Login Screen shown incorrect error message

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161169

--- Comment #1 from LeroyG  ---
*** Bug 161170 has been marked as a duplicate of this bug. ***

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

[Bug 161170] Login Screen shown incorrect error message

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161170

LeroyG  changed:

   What|Removed |Added

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

--- Comment #1 from LeroyG  ---


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

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

[Bug 160888] Cannot unprotect protected macro library

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #7 from ady  ---
While I can replicate the crash in LO 24.2.3.2 when starting with attachment
194193, which already has a password for the macro library, I was trying to
replicate the complete procedure, starting with no password, setting a
password, and _then_ removing it.

I tried to reproduce the steps using attachment 194193 with LO 7.6.6. The Old
Password ("test") is not accepted, so the rest of the details don't matter.

Since this procedure failed for me (i.e. old password not accepted in LO
7.6.6), I am now wondering whether the problem could be related to the changes
to encryption that were introduced for LO 24.2.

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

[Bug 161176] Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

--- Comment #4 from Klaas  ---
Created attachment 194201
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194201=edit
Original odt-file with printer problems

Original odt-file with background-color problems

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

[Bug 161176] Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

--- Comment #3 from m_a_riosv  ---
Sorry, but that serves only to visualize the issue.

Please attach the ODT file that produces that PDF, it is need to see how it is
configured.

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

Re: Compiling nearly every file now compiles sqlbison.cxx and/or sqlflex.cxx

2024-05-19 Thread Caolán McNamara
On Sun, 2024-05-19 at 16:30 -0400, Patrick Luby wrote:
> cd vcl && touch skia/gdiimpl.cxx && make

maybe adding -d to the end of the make might give a hint as to what
could be going on


Re: Compiling nearly every file now compiles sqlbison.cxx and/or sqlflex.cxx

2024-05-19 Thread Patrick Luby


> On May 19, 2024, at 3:33 PM, Caolán McNamara  
> wrote:
> 
> On Sun, 2024-05-19 at 13:22 -0400, Patrick Luby wrote:
>> A couple of weeks ago I started seeing my builds slow down and my
>> build log filled with compiler warnings in sqlbison.cxx and
>> sqlflex.cxx on macOS.
>> 
>> Is anyone else seeing this? I see these warnings even when compiling
>> files in vcl. Seems to me that something in the build is not working
>> right since I see one of these files is recompiled for each and every
>> other C++ file that is compiled.
> 
> That seems very odd. Checking a gerrit macos build log like
> https://ci.libreoffice.org/job/gerrit_mac/167726/consoleFull
> I just see the expected handful of sqlbison and sqlflex warnings as
> those individual files are compiled once.
> 
> I can't see any reason why compiling vcl would have any connection to
> something in connectivity.
> 
> What is your configure line? wondering if there is some
> --enable-mergelibs or --enable-pch thing that could be a trigger.

Maybe. I have neither of those enabled in my local build. But after a full 
build, I can get this behaviour to occur by the following steps:

cd vcl && touch skia/gdiimpl.cxx && make

And I see. Maybe there is a build tool getting rebuilt?:

/Volumes/LOBuilds/lode/dev/core/workdir/LexTarget/connectivity/source/parse/sqlflex.cxx:6117:14:
 warning: code will never be executed [-Wunreachable-code]
if ( ! (yy_did_buffer_switch_on_eof) )
^~~
/Volumes/LOBuilds/lode/dev/core/workdir/LexTarget/connectivity/source/parse/sqlflex.cxx:6445:14:
 warning: code will never be executed [-Wunreachable-code]
if ( ! (yy_did_buffer_switch_on_eof) )
^~~
/Volumes/LOBuilds/lode/dev/core/workdir/LexTarget/connectivity/source/parse/sqlflex.cxx:6440:5:
 warning: unannotated fall-through between switch labels 
[-Wimplicit-fallthrough]
case EOB_ACT_END_OF_FILE:
^
/Volumes/LOBuilds/lode/dev/core/workdir/LexTarget/connectivity/source/parse/sqlflex.cxx:6440:5:
 note: insert '[[fallthrough]];' to silence this warning
case EOB_ACT_END_OF_FILE:
^
[[fallthrough]];  
/Volumes/LOBuilds/lode/dev/core/workdir/LexTarget/connectivity/source/parse/sqlflex.cxx:6440:5:
 note: insert 'break;' to avoid fall-through
case EOB_ACT_END_OF_FILE:
^
break;  3 warnings generated.
[DEP] LNK:Library/libvcllo.dylib.d
[LNK] Library/libvcllo.dylib



Re: Compiling nearly every file now compiles sqlbison.cxx and/or sqlflex.cxx

2024-05-19 Thread Caolán McNamara
On Sun, 2024-05-19 at 13:22 -0400, Patrick Luby wrote:
> A couple of weeks ago I started seeing my builds slow down and my
> build log filled with compiler warnings in sqlbison.cxx and
> sqlflex.cxx on macOS.
> 
> Is anyone else seeing this? I see these warnings even when compiling
> files in vcl. Seems to me that something in the build is not working
> right since I see one of these files is recompiled for each and every
> other C++ file that is compiled.

That seems very odd. Checking a gerrit macos build log like
https://ci.libreoffice.org/job/gerrit_mac/167726/consoleFull
I just see the expected handful of sqlbison and sqlflex warnings as
those individual files are compiled once.

I can't see any reason why compiling vcl would have any connection to
something in connectivity.

What is your configure line? wondering if there is some
--enable-mergelibs or --enable-pch thing that could be a trigger.


[Bug 160888] Cannot unprotect protected macro library

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #6 from Theo  ---
What @ady describes is exactly what mean. Try those three steps and the
applications hang, where it should just unprotect the library and come back.

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

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

2024-05-19 Thread Caolán McNamara (via logerrit)
 sw/source/ui/frmdlg/frmpage.cxx |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

New commits:
commit bf877f3e10c3a2ce7267335a0c9c7cd828c373ca
Author: Caolán McNamara 
AuthorDate: Sun May 19 15:08:14 2024 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Sun May 19 21:05:55 2024 +0200

Resolves: tdf#151382 we want to save the FN_KEEP_ASPECT_RATIO state

and not if it is implied to be toggled on by SwFormatFrameSize::SYNCED
in which case on "ok" FN_KEEP_ASPECT_RATIO is set from the ui state

so both tdf#151382 and tdf132591 work

Change-Id: I039de0e8f0f9adcc3c02f0e07c12d83cd807887b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167816
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/sw/source/ui/frmdlg/frmpage.cxx b/sw/source/ui/frmdlg/frmpage.cxx
index b3e2a873ad18..8a7ec8d4ffe0 100644
--- a/sw/source/ui/frmdlg/frmpage.cxx
+++ b/sw/source/ui/frmdlg/frmpage.cxx
@@ -2306,6 +2306,8 @@ void SwFramePage::Init(const SfxItemSet& rSet)
 
 if (SfxItemState::SET == rSet.GetItemState(FN_KEEP_ASPECT_RATIO))
 m_xFixedRatioCB->set_active(rSet.Get(FN_KEEP_ASPECT_RATIO).GetValue());
+// see tdf#132591 and tdf#151382 for some examples of FN_KEEP_ASPECT_RATIO 
cases
+m_xFixedRatioCB->save_state();
 
 // columns
 SwFormatCol aCol( rSet.Get(RES_COL) );
@@ -2364,7 +2366,6 @@ void SwFramePage::Init(const SfxItemSet& rSet)
 
 if (rSize.GetWidthPercent() == SwFormatFrameSize::SYNCED || 
rSize.GetHeightPercent() == SwFormatFrameSize::SYNCED)
 m_xFixedRatioCB->set_active(true);
-m_xFixedRatioCB->save_state();
 if (rSize.GetWidthPercent() && rSize.GetWidthPercent() != 
SwFormatFrameSize::SYNCED &&
 !m_xRelWidthCB->get_active())
 {


[Bug 141314] LibreOffice Remote for Impress not showing up in iOS AppStore

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141314

raal  changed:

   What|Removed |Added

 Resolution|INVALID |---
URL|https://bugs.documentfounda |
   |tion.org/enter_bug.cgi?prod |
   |uct=Impress%20Remote|
 Status|RESOLVED|NEW

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

core.git: Branch 'libreoffice-24-2' - include/svtools svtools/source

2024-05-19 Thread Caolán McNamara (via logerrit)
 include/svtools/editbrowsebox.hxx |2 ++
 svtools/source/brwbox/ebbcontrols.cxx |6 ++
 2 files changed, 8 insertions(+)

New commits:
commit 7472bf01dee87a45aa3345397ae6f072f5d57058
Author: Caolán McNamara 
AuthorDate: Fri May 17 21:36:40 2024 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Sun May 19 20:33:43 2024 +0200

Resolves: tdf#161133 read-only widget should have deactivated calendar

a problem since:

commit 6e7e19d9c300dbdd279789b09f94781e946fad52
Date:   Wed Jul 15 12:10:32 2020 +0100

weld DateControl

Change-Id: I367c4237903655ad02c0c4af70ae0383b8a89f25
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167811
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/include/svtools/editbrowsebox.hxx 
b/include/svtools/editbrowsebox.hxx
index c89a396a9dc7..6a581d4e7305 100644
--- a/include/svtools/editbrowsebox.hxx
+++ b/include/svtools/editbrowsebox.hxx
@@ -829,6 +829,8 @@ namespace svt
 
 void SetDate(const Date& rDate);
 
+virtual void SetEditableReadOnly(bool bReadOnly) override;
+
 virtual void dispose() override;
 private:
 std::unique_ptr m_xMenuButton;
diff --git a/svtools/source/brwbox/ebbcontrols.cxx 
b/svtools/source/brwbox/ebbcontrols.cxx
index 45b1a3766e76..761fd32b3fa7 100644
--- a/svtools/source/brwbox/ebbcontrols.cxx
+++ b/svtools/source/brwbox/ebbcontrols.cxx
@@ -586,6 +586,12 @@ namespace svt
 m_xCalendar->set_date(rDate);
 }
 
+void DateControl::SetEditableReadOnly(bool bReadOnly)
+{
+FormattedControlBase::SetEditableReadOnly(bReadOnly);
+m_xMenuButton->set_sensitive(!bReadOnly);
+}
+
 void DateControl::dispose()
 {
 m_xTodayBtn.reset();


core.git: Branch 'libreoffice-24-2' - include/vcl svx/source vcl/inc vcl/source vcl/unx

2024-05-19 Thread Caolán McNamara (via logerrit)
 include/vcl/weld.hxx   |4 
 svx/source/fmcomp/gridcell.cxx |   11 +--
 vcl/inc/salvtables.hxx |2 ++
 vcl/source/app/salvtables.cxx  |2 ++
 vcl/unx/gtk3/gtkinst.cxx   |   16 +++-
 5 files changed, 32 insertions(+), 3 deletions(-)

New commits:
commit 07e6ed881032d1df3ec96c93f5e6c502e021eeb6
Author: Caolán McNamara 
AuthorDate: Sat May 18 21:17:01 2024 +0100
Commit: Adolfo Jayme Barrientos 
CommitDate: Sun May 19 20:33:05 2024 +0200

Resolves: tdf#157453 support FM_PROP_LINECOUNT for combobox dropdow rows

Change-Id: I3d18ed505c2eea7305903f9a476c332db0148113
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167814
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos 

diff --git a/include/vcl/weld.hxx b/include/vcl/weld.hxx
index fc585bdb1071..2a4e1ef084b6 100644
--- a/include/vcl/weld.hxx
+++ b/include/vcl/weld.hxx
@@ -889,6 +889,10 @@ public:
 virtual void set_max_mru_count(int nCount) = 0;
 virtual OUString get_mru_entries() const = 0;
 virtual void set_mru_entries(const OUString& rEntries) = 0;
+
+// Backwards compatibility, should be avoided to allow
+// UI consistency.
+virtual void set_max_drop_down_rows(int nRows) = 0;
 };
 
 enum class ColumnToggleType
diff --git a/svx/source/fmcomp/gridcell.cxx b/svx/source/fmcomp/gridcell.cxx
index e8c56fb0ac38..2f17f7f3a490 100644
--- a/svx/source/fmcomp/gridcell.cxx
+++ b/svx/source/fmcomp/gridcell.cxx
@@ -2629,9 +2629,16 @@ void DbListBox::Init(BrowserDataWin& rParent, const 
Reference< XRowSet >& xCurso
 DbCellControl::Init( rParent, xCursor );
 }
 
-void DbListBox::implAdjustGenericFieldSetting( const Reference< XPropertySet 
>& /*rxModel*/ )
+void DbListBox::implAdjustGenericFieldSetting(const Reference& 
_rxModel)
 {
-// ignore FM_PROP_LINECOUNT
+DBG_ASSERT( m_pWindow, "DbListBox::implAdjustGenericFieldSetting: not to 
be called without window!" );
+DBG_ASSERT( _rxModel.is(), "DbListBox::implAdjustGenericFieldSetting: 
invalid model!" );
+if ( m_pWindow && _rxModel.is() )
+{
+sal_Int16  nLines   = getINT16( _rxModel->getPropertyValue( 
FM_PROP_LINECOUNT ) );
+weld::ComboBox& rComboBox = 
static_cast(m_pWindow.get())->get_widget();
+rComboBox.set_max_drop_down_rows(nLines);
+}
 }
 
 CellControllerRef DbListBox::CreateController() const
diff --git a/vcl/inc/salvtables.hxx b/vcl/inc/salvtables.hxx
index 4074e097a4f4..d6d3a90ce2e4 100644
--- a/vcl/inc/salvtables.hxx
+++ b/vcl/inc/salvtables.hxx
@@ -922,6 +922,8 @@ public:
 return 20 * (pDefault ? pDefault->GetDPIScaleFactor() : 1.0);
 }
 
+void set_max_drop_down_rows(int nRows) override { 
m_xComboBox->SetDropDownLineCount(nRows); }
+
 void CallHandleEventListener(VclWindowEvent& rEvent)
 {
 if (rEvent.GetId() == VclEventId::DropdownPreOpen
diff --git a/vcl/source/app/salvtables.cxx b/vcl/source/app/salvtables.cxx
index faf645fc7943..8dc0edf814fd 100644
--- a/vcl/source/app/salvtables.cxx
+++ b/vcl/source/app/salvtables.cxx
@@ -6927,6 +6927,8 @@ public:
 
 virtual void set_mru_entries(const OUString&) override { assert(false && 
"not implemented"); }
 
+virtual void set_max_drop_down_rows(int) override { assert(false && "not 
implemented"); }
+
 virtual void set_item_menu(const OUString&, weld::Menu*) override
 {
 assert(false && "not implemented");
diff --git a/vcl/unx/gtk3/gtkinst.cxx b/vcl/unx/gtk3/gtkinst.cxx
index a899fc16c606..6a06947d4cd2 100644
--- a/vcl/unx/gtk3/gtkinst.cxx
+++ b/vcl/unx/gtk3/gtkinst.cxx
@@ -21034,6 +21034,11 @@ public:
 #endif
 }
 
+virtual void set_max_drop_down_rows(int) override
+{
+SAL_WARN( "vcl.gtk", "set_max_drop_down_rows unimplemented");
+}
+
 virtual ~GtkInstanceComboBox() override
 {
 //m_xCustomMenuButtonHelper.reset();
@@ -21114,6 +21119,7 @@ private:
 gint m_nPrePopupCursorPos;
 int m_nMRUCount;
 int m_nMaxMRUCount;
+int m_nMaxDropdownRows;
 
 static gboolean idleAutoComplete(gpointer widget)
 {
@@ -21236,7 +21242,7 @@ private:
 {
 const StyleSettings& rSettings = 
Application::GetSettings().GetStyleSettings();
 
-int nMaxRows = rSettings.GetListBoxMaximumLineCount();
+int nMaxRows = m_nMaxDropdownRows == -1 ? 
rSettings.GetListBoxMaximumLineCount() : m_nMaxDropdownRows;
 bool bAddScrollWidth = false;
 int nRows = get_count_including_mru();
 if (nMaxRows < nRows)
@@ -22154,6 +22160,7 @@ public:
 , m_nPrePopupCursorPos(-1)
 , m_nMRUCount(0)
 , m_nMaxMRUCount(0)
+, m_nMaxDropdownRows(-1)
 {
 int nActive = gtk_combo_box_get_active(m_pComboBox);
 
@@ -22838,6 +22845,11 @@ public:
 return nWidth;
 }
 
+virtual void set_max_drop_down_rows(int nMaxRows) override
+{
+m_nMaxDropdownRows = nMaxRows;
+}
+
 virtual ~GtkInstanceComboBox() override
 {
 

[Bug 132780] Feature Request: Add Calc Tables with functionality similar to Excel's "Format as tables"

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132780

--- Comment #32 from Antonio Vidal  ---
Recently, Google Sheets released an auto formatting feature which would
compliment this feature request, it is a great improvement over Office 365 and
LibreOffice auto format

Announced: 14/05/24 (DD/MM/YY)

Google Sheets New Feature: New ways to quickly format and organize data with
tables: https://support.google.com/docs/thread/274482551?hl=en

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

[Bug 132780] Feature Request: Add Calc Tables with functionality similar to Excel's "Format as tables"

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132780

--- Comment #31 from Antonio Vidal  ---
Created attachment 194200
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194200=edit
Google Sheets: pre-built tables (3. Gif)

We’re also introducing pre-built tables that you can populate with common data
types for everyday tasks like project management, inventory management, event
planning and more. Now with pre-built tables, you never have to build a
spreadsheet from scratch again.

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

[Bug 161153] Inserting tashdid (a.k.a. shaddah) character (Unicode 0651) breaks or distorts Persian text

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161153

--- Comment #9 from arham.amo...@gmail.com ---
(In reply to ahangarha from comment #8)
> This is my finding.
> 
> I could reproduce the issue on the shared document. The issue is observed
> only when editing that document, meaning that if the user types the same
> text in another document (no copy/paste) there is no issue.
> 
> Someone needs to check for hidden characters in the document, otherwise in
> normal situation, there is no issue even with B Nazanin.

The issue may be related to the presence of diacritics (kasreh, fatheh, etc) in
text. In any text with B Nazanin font and possibly similar fonts, if a sentence
contains a diacritic such as kasreh, inserting a tashdid in the sentence, at
least displaces the diacritic to a wrong position.

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

[Bug 132780] Feature Request: Add Calc Tables with functionality similar to Excel's "Format as tables"

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132780

--- Comment #30 from Antonio Vidal  ---
Comment on attachment 194197
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194197
Google Sheets: Auto-applied formatting (1. Gif)

With tables, you can simplify and accelerate spreadsheet building by bringing
format and structure to unorganized ranges. By selecting your data range and
going to Format > Convert to table, Sheets now does the heavy lifting to format
and organize data with a polished design including column types, filters, color
coding, dropdown menus and more.

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

[Bug 132780] Feature Request: Add Calc Tables with functionality similar to Excel's "Format as tables"

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132780

--- Comment #29 from Antonio Vidal  ---
Created attachment 194199
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194199=edit
Google Sheets: Group By View (2. Gif)

When you are using tables, you’ll also have access to our new type of view,
group by, where you can aggregate your data into groups based on a selected
column. For instance, you can decide to group all data at the same priority
level in one place, as shown below.

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

[Bug 161176] Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

--- Comment #2 from Klaas  ---
Created attachment 194198
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194198=edit
>From LO Writer printed page with faulty borders

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

[Bug 132780] Feature Request: Add Calc Tables with functionality similar to Excel's "Format as tables"

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132780

--- Comment #28 from Antonio Vidal  ---
Created attachment 194197
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194197=edit
Google Sheets: Auto-applied formatting (1. Gif)

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

[Bug 103270] [META] Image/Picture dialog bugs and enhancements

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103270
Bug 103270 depends on bug 151382, which changed state.

Bug 151382 Summary: UI: Keep ratio setting lost after opening Image properties 
Position and Size dialog, a change, OK and reopening the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=151382

   What|Removed |Added

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

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

core.git: sw/source

2024-05-19 Thread Caolán McNamara (via logerrit)
 sw/source/ui/frmdlg/frmpage.cxx |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

New commits:
commit d0702a3f17c1fbd1b8ffb9ca0b275943e1a1f442
Author: Caolán McNamara 
AuthorDate: Sun May 19 15:08:14 2024 +0100
Commit: Caolán McNamara 
CommitDate: Sun May 19 20:08:15 2024 +0200

Resolves: tdf#151382 we want to save the FN_KEEP_ASPECT_RATIO state

and not if it is implied to be toggled on by SwFormatFrameSize::SYNCED
in which case on "ok" FN_KEEP_ASPECT_RATIO is set from the ui state

so both tdf#151382 and tdf132591 work

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

diff --git a/sw/source/ui/frmdlg/frmpage.cxx b/sw/source/ui/frmdlg/frmpage.cxx
index 6d6a1fefd49a..589af7dbb0a0 100644
--- a/sw/source/ui/frmdlg/frmpage.cxx
+++ b/sw/source/ui/frmdlg/frmpage.cxx
@@ -2321,6 +2321,8 @@ void SwFramePage::Init(const SfxItemSet& rSet)
 
 if (SfxItemState::SET == rSet.GetItemState(FN_KEEP_ASPECT_RATIO))
 m_xFixedRatioCB->set_active(rSet.Get(FN_KEEP_ASPECT_RATIO).GetValue());
+// see tdf#132591 and tdf#151382 for some examples of FN_KEEP_ASPECT_RATIO 
cases
+m_xFixedRatioCB->save_state();
 
 // columns
 SwFormatCol aCol( rSet.Get(RES_COL) );
@@ -2379,7 +2381,6 @@ void SwFramePage::Init(const SfxItemSet& rSet)
 
 if (rSize.GetWidthPercent() == SwFormatFrameSize::SYNCED || 
rSize.GetHeightPercent() == SwFormatFrameSize::SYNCED)
 m_xFixedRatioCB->set_active(true);
-m_xFixedRatioCB->save_state();
 if (rSize.GetWidthPercent() && rSize.GetWidthPercent() != 
SwFormatFrameSize::SYNCED &&
 !m_xRelWidthCB->get_active())
 {


[Bug 161174] table splitting bug

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161174

--- Comment #4 from Telesto  ---
Created attachment 194196
  --> https://bugs.documentfoundation.org/attachment.cgi?id=194196=edit
Sample

It's not totally clear which steps are needed to trigger the bug with the
original example.

However I'm able to reproduce it:
1. Open the sample file
2. Delete the yellow highlighted text
3. Save & File -> Reload

Fine with
Version: 7.1.8.0.0+ (x64) / LibreOffice Community
Build ID: a94b58277c7aeaa83ce14347cd0b8f7137969d03
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

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

[Bug 158914] Calc leaks RAM when using macOS accessibility

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158914

--- Comment #15 from Patrick Luby (volunteer)  ---
(In reply to Patrick Luby (volunteer) from comment #14)
> But what I found interesting is that while VoiceOver is enabled, clicking on
> a cell causes roughly 2K new ScAccessibleCell instances to be allocated. A
> few of those instances gets deleted very soon after it is allocated, but all
> the rest are cached somewhere until the Calc document is closed.

I've narrowed the problem down to the following patch:

https://git.libreoffice.org/core/+/8e886993f32b7db11a99bdecf06451e6de6c3842%5E!

Before that patch, the code reused the same ScAccessibleCell instance for the
2K requests that we are seeing for each selected cell.

Apparently, that caused the data in the reused ScAccessibleCell to be stale
under certain circumstances (e.g. deleting the cell's contents) so we can't now
I think we need to move higher up the stack and figure out what Calc code needs
2K ScAccessibleCell instances for each cell.

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

[Bug 161176] Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m_a_riosv  ---
Please attach a sample file, reduce the size as much as possible without
private information, and paste the information in Menu/Help/About LibreOffice,
there is a copy icon.

Verify if your printer is able to print up to the border, not all are.

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

[Bug 141314] LibreOffice Remote for Impress not showing up in iOS AppStore

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141314

--- Comment #7 from steve  ---
What's going on here? Why is this bug Resolved Invalid?

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

[Bug 161174] table splitting bug

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161174

m_a_riosv  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression

--- Comment #3 from m_a_riosv  ---
On my installed LOs:

First with the issue
Version: 7.4.7.2 (x64) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL


The last one that works
Version: 7.2.7.2 (x64) / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL

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

[Bug 161176] New: Background should be completly colored, but left and top border are still white

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161176

Bug ID: 161176
   Summary: Background should be completly colored, but left and
top border are still white
   Product: LibreOffice
   Version: 7.6.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: klaa...@aol.com

Description:
Version 7.6.7.2, Writer: Background of a page should be completely colored, so
I set format, page, background, color . Preview shows it
correctly, but when printed, top and left border doesn't show any color.

Steps to Reproduce:
1. format, page, background
2. color set to a value like d7
3. printer preview
4. print

Actual Results:
When printed to pdf, either via ABBYY Fine Reader or Microsoft PDF Printer or
to a real hardware printer, the left and the top border stayed completely
white, without any color. Rigth and bottom borders show the chosen color. All
borders for texts are set to 1.5 cm. But top and left borders are white with
1.5 cm.

Expected Results:
A page with a completly colored background, inclusive all borders.


Reproducible: Always


User Profile Reset: No

Additional Info:
Writer, page, color

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

[Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140702

V Stuart Foote  changed:

   What|Removed |Added

 CC||par...@narod.ru

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

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

[Bug 161175] there is no "link to page" option at frame/picture context menu

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161175

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
Long gone and intentionally removed at the LibreOffice 7.1 release as for bug
135836. It is not coming back as a default entry, and it is trivial to
customize and restore the "to page" anchor [1] (though not back onto the
context Anchor sub-menu).

=-=ref-=
[1] UNO uno.SetAnchorToPage

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

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

[Bug 161174] table splitting bug

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161174

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m_a_riosv  ---
Reproducible
Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
and
Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 658a212585c56540a17c4e6829716d4ef4e3
CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: default;
VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Bug 158914] Calc leaks RAM when using macOS accessibility

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158914

--- Comment #14 from Patrick Luby (volunteer)  ---
(In reply to Michael Weghorn from comment #10)
> I remember Noel fixed some Calc memory leak last year (see commit
> 8e886993f32b7db11a99bdecf06451e6de6c3842 ), but at least that fix was
> already included in daily builds last December (already tested according to
> comment 2).
> Apart from that, I don't have any ideas right now without doing further
> analysis.

So I added the following debug patch to see if there was any ScAccessibleCell
were never getting deleted. The good news is that when you close a Calc
document, the number of undeleted ScAccessibleCell instances goes back down to
zero.

But what I found interesting is that while VoiceOver is enabled, clicking on a
cell causes roughly 2K new ScAccessibleCell instances to be allocated. A few of
those instances gets deleted very soon after it is allocated, but all the rest
are cached somewhere until the Calc document is closed.

So, the next thing to investigate is which code is requesting so many new
ScAccessibleCell instances for each cell:

diff --git a/sc/source/ui/Accessibility/AccessibleCell.cxx
b/sc/source/ui/Accessibility/AccessibleCell.cxx
index b27fbb90671a..0d6beafa37c8 100644
--- a/sc/source/ui/Accessibility/AccessibleCell.cxx
+++ b/sc/source/ui/Accessibility/AccessibleCell.cxx
@@ -49,6 +49,8 @@
 using namespace ::com::sun::star;
 using namespace ::com::sun::star::accessibility;

+static std::map aAccessibleCellMap;
+
 rtl::Reference ScAccessibleCell::create(
 const uno::Reference& rxParent,
 ScTabViewShell* pViewShell,
@@ -79,10 +81,15 @@ ScAccessibleCell::ScAccessibleCell(
 {
 if (pViewShell)
 pViewShell->AddAccessibilityObject(*this);
+aAccessibleCellMap[this] = this;
 }

 ScAccessibleCell::~ScAccessibleCell()
 {
+std::map::iterator it =
aAccessibleCellMap.find(this);
+if (it != aAccessibleCellMap.end())
+aAccessibleCellMap.erase(it);
+fprintf(stderr, "ScAccessibleCell count; %lu\n", aAccessibleCellMap.size());
 if (!ScAccessibleContextBase::IsDefunc() && !rBHelper.bInDispose)
 {
 // increment refcount to prevent double call off dtor

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

[GSoC] Comments in Sidebar Deck: Weekly Update

2024-05-19 Thread Mohit Marathe
Hi everyone,

I’ll be posting weekly updates about my progress on this project in this thread.

This week, I learned how to use Glade for making UIs.
I used it to make .ui for “Comments” deck in the sidebar.

This is how looks (for now, as there are lots of things to add):

You can find the patch here: https://gerrit.libreoffice.org/c/core/+/167840

Thanks,
Mohit

core.git: sc/source

2024-05-19 Thread Eike Rathke (via logerrit)
 sc/source/ui/docshell/docfunc.cxx |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

New commits:
commit d4ae5abb4d00cc8adb3c45a9410fc71e56211c46
Author: Eike Rathke 
AuthorDate: Sun May 19 15:21:19 2024 +0200
Commit: Eike Rathke 
CommitDate: Sun May 19 19:26:05 2024 +0200

Resolves: tdf#160804 sc: ResizeMatrix: Use document grammar

API grammar (old GRAM_PODF_A1) here was always wrong and could
never had matched the formula string obtained from the document,
but in earlier days array separators weren't configurable so this
may have worked accidentally.. Likely GRAM_PODF_A1 was introduced
being confused by existance of older bApi parameter that never was
true though and got eliminated later.

Change-Id: Ie77ad4047c21d999bea1ff97c7c2b451f01121eb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167844
Reviewed-by: Eike Rathke 
Tested-by: Jenkins

diff --git a/sc/source/ui/docshell/docfunc.cxx 
b/sc/source/ui/docshell/docfunc.cxx
index 556cd6e6c940..d47f6f0bde40 100644
--- a/sc/source/ui/docshell/docfunc.cxx
+++ b/sc/source/ui/docshell/docfunc.cxx
@@ -5521,11 +5521,11 @@ void ScDocFunc::ResizeMatrix( const ScRange& rOldRange, 
const ScAddress& rNewEnd
 
 if ( DeleteContents( aMark, InsertDeleteFlags::CONTENTS, true, 
false/*bApi*/ ) )
 {
-// GRAM_API for API compatibility.
-if (!EnterMatrix( aNewRange, , nullptr, aFormula, false/*bApi*/, 
false, OUString(), formula::FormulaGrammar::GRAM_API ))
+// Formula string was obtained in document grammar.
+if (!EnterMatrix( aNewRange, , nullptr, aFormula, false/*bApi*/, 
false, OUString(), rDoc.GetGrammar() ))
 {
 // try to restore the previous state
-EnterMatrix( rOldRange, , nullptr, aFormula, false/*bApi*/, 
false, OUString(), formula::FormulaGrammar::GRAM_API );
+EnterMatrix( rOldRange, , nullptr, aFormula, false/*bApi*/, 
false, OUString(), rDoc.GetGrammar() );
 }
 }
 


[Bug 161175] New: there is no "link to page" option at frame/picture context menu

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161175

Bug ID: 161175
   Summary: there is no "link to page" option at frame/picture
context menu
   Product: LibreOffice
   Version: 7.6.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: par...@narod.ru

Description:
at 7.6.7.2 version link to page option is lost in context menues for frame or
picture. In earlier version it exist, and it was more comfortable. 
Now for linking to page i have to go to properties window first.

Actual Results:
via bypass operation (Properties...) linking to page can be done

Expected Results:
restore option link "to page" (symbol, paragraph, as symbol) in context menu


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: ru
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

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

Compiling nearly every file now compiles sqlbison.cxx and/or sqlflex.cxx

2024-05-19 Thread Patrick Luby
A couple of weeks ago I started seeing my builds slow down and my build log 
filled with compiler warnings in sqlbison.cxx and sqlflex.cxx on macOS.

Is anyone else seeing this? I see these warnings even when compiling files in 
vcl. Seems to me that something in the build is not working right since I see 
one of these files is recompiled for each and every other C++ file that is 
compiled.

I understand that all of the warnings are because of the blocks of code 
generated by yacc and/or lex. My question is why are we recompiling the same to 
files hundreds (maybe thousands?) of times during a build. Is it is possible 
that those files are getting accidentally included in a common include file?

Patrick

[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135739

--- Comment #10 from Julien Nabet  ---
(In reply to Jim Raykowski from comment #9)
> (In reply to Julien Nabet from comment #8)
> > Are you sure about uno:JumpToNextTableSel ?
> 
> I also found .uno:JumpToNextTableSel for Ctrl+Shift+PgDn to be odd because
> it is not available in the Writer shell.
> 
> Closer inspection shows it was .uno:JumpToFootnoteArea, removed by commit
> 139e0fb7132cb7b943ea50930a8a7ede72ea5e47
> 
> Placing .uno:PageDownSel and .uno:JumpToFootnoteArea buttons on a tool bar
> and executing them in the order given in the steps to repro I *do not* repro
> the assert.
>...
Thank you for the investigation! At least we're sure it's ok now.

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

[Bug 161167] LibreOffice Version: 24.2.3.2 (X86_64) - Writer - Footnotes not displayed.

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161167

m_a_riosv  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

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

[Bug 135739] Assertion on Ctrl+Shift+Page down after Shift+Page down

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135739

--- Comment #9 from Jim Raykowski  ---
(In reply to Julien Nabet from comment #8)
> Are you sure about uno:JumpToNextTableSel ?

I also found .uno:JumpToNextTableSel for Ctrl+Shift+PgDn to be odd because it
is not available in the Writer shell.

Closer inspection shows it was .uno:JumpToFootnoteArea, removed by commit
139e0fb7132cb7b943ea50930a8a7ede72ea5e47

Placing .uno:PageDownSel and .uno:JumpToFootnoteArea buttons on a tool bar and
executing them in the order given in the steps to repro I *do not* repro the
assert.

Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 60a7c560a80839248769a13d5a1dd7a353abf476
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Bug 161153] Inserting tashdid (a.k.a. shaddah) character (Unicode 0651) breaks or distorts Persian text

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=161153

--- Comment #8 from ahangarha  ---
This is my finding.

I could reproduce the issue on the shared document. The issue is observed only
when editing that document, meaning that if the user types the same text in
another document (no copy/paste) there is no issue.

Someone needs to check for hidden characters in the document, otherwise in
normal situation, there is no issue even with B Nazanin.

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

[Bug 45028] label of connector, ordinary lines and arrow gets written through line

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=45028

--- Comment #56 from Regina Henschel  ---
The import of the Visio file sets the character background to White, so for
that file the line does not go through the label.

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

[Bug 160888] Cannot unprotect protected macro library

2024-05-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160888

--- Comment #5 from ady  ---
(In reply to Theo from comment #4)
> The macro library has been protected with the password 'test'. I can not
> unprotect this macro library.

How exactly are you trying to achieve that? Do you mean that you:

1. input the old password in the Old Password field,
2. leave the 2 fields under New Password empty,
3. and then click OK?

Please confirm whether that's the procedure that you used in order to attempt
to unprotect the macro library.

IDK whether this is the adequate procedure that should be used, but if this is
the procedure you followed, (I think) I can replicate the crash on MS Windows
using attachment 194193 with LO 24.2.3.2.

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

  1   2   >