[Bug 33210] menus do not build from desktop integration.

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

--- Comment #11 from Commit Notification 
 ---
Sahil committed a patch related to this issue.
It has been pushed to "master":

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

tdf#33210 Add Listener for ColumnRowHighlighting changes

It will be available in 24.8.0.

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

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

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

[Bug 33210] menus do not build from desktop integration.

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.8.0

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

[Bug 66791] FORMATTING: Incorrect application of "Asian text font" for quotation marks when the paragraph contains a mixture of western and asian characters

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

Kevin Suo  changed:

   What|Removed |Added

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

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

[Bug 123105] FILEOPEN DOCX Arrow changes its head style in LO

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

--- Comment #11 from Tex2002ans  ---
Still reproducible in:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

- - -

I retested by using these steps:

1. Opened attachment in Comment #8.
--- In LibreOffice + Word 2016.
2. Saw similar as screenshot in Comment #9.

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

[Bug 139814] Crash pasting after undo

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

--- Comment #7 from Tex2002ans  ---
Still reproduced in:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

Here's the crash report:

https://crashreport.libreoffice.org/stats/crash_details/48330db2-d1c4-427f-a81a-a158acfeb079

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

[Bug 158599] Hangs when opening options menu

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

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Bug 158363] Add configuration key for the Right-aligned vertical ruler property

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 108800] [META] Print related issues

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

Bug 155250 Summary: Does not print more than first page
https://bugs.documentfoundation.org/show_bug.cgi?id=155250

   What|Removed |Added

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

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

[Bug 158356] FORMATTING: cell format "Status" from xlsx are not transferred correctly to Calc

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 158599] Hangs when opening options menu

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

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

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

[Bug 155250] Does not print more than first page

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 155250] Does not print more than first page

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

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

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 146806] printing, custom paper size, 2pages in 1, duplicate

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

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 146806] printing, custom paper size, 2pages in 1, duplicate

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

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

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 71037] FORMATTING: wrong page number direction in footnote's continuation notice

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

--- Comment #16 from QA Administrators  ---
Dear safarzadeh.h,

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 94076] FILEOPEN: ODT - Table styles not imported and not preserved after Roundtrip

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 90107] When using the presenter console with user size portrait slide, computer screen is showing the wrong height and not all slide is seen

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

--- Comment #12 from QA Administrators  ---
Dear Jim Roper,

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 34914] page border in Calc works incorrect

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

--- Comment #12 from QA Administrators  ---
Dear sasha.libreoffice,

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 145794] LibreOffice document has partly black content while resizing (Skia)

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 145568] DIRECT FORMATTING: Text format of DF remains after "Undo" if Text with DF was pasted at the end of a paragraph (steps in comment 7)

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

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

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 145055] UI Re-running filter by color is inconvenient because of inactive OK button

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

--- Comment #2 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 129261] EDITING: Clicking with mouse in CLOB of a form throws "Content has been changed" when closing the form.

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

--- Comment #9 from QA Administrators  ---
Dear Alan Wheeler,

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 132890] Clear direct formatting has no separate undo step

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 137298] Should only show Edit Fields dialog for date/time fields inserted from Docinformation tab and where appropriate show File - General - Properties - Description

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

--- Comment #28 from QA Administrators  ---
Dear sdc.blanco,

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 123195] Double Window Envelope Format Function Unusable

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

--- Comment #4 from QA Administrators  ---
Dear Jonathan Ryshpan,

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 118321] Text on path (=Fontwork) is inconsistent on shape 'text box'

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

--- Comment #6 from QA Administrators  ---
Dear Regina Henschel,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 117369] UI Comment box is truncated on hover when comment cell is copied

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

--- Comment #8 from QA Administrators  ---
Dear Emil Tanev,

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 117204] Slides notes not shown or if shown not changing on presentation mode (dual screen) of specific ODP

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

--- Comment #6 from QA Administrators  ---
Dear Thierry Mallard,

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 103068] New Database Wizard gets confused between ODBC and JDBC connection if you backup twice to step 1.

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 158440] Filter for background should take colors in empty cells

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

Aron Budea  changed:

   What|Removed |Added

 Whiteboard|target: 24.2|target:24.2.0 target:7.6.4

--- Comment #5 from Aron Budea  ---
In 7.6:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=644ad239a22f438b300f1dd7fbf602e920075316
https://cgit.freedesktop.org/libreoffice/core/commit/?id=300a09f4ebae1c1e08645f5d0112137d25223f37t

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

[Bug 158599] Hangs when opening options menu

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

--- Comment #2 from Keith  ---
I hope this is what you are asking for.

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded(In reply to m.a.riosv from comment #1)
> Please test in safe mode, Menu/Help/Restart in Safe Mode
> 
> Please paste here the information on Menu/Help/About LibreOffice (There is
> an icon to copy)

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

[Bug 158612] New: Not able to select different border thickness

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

Bug ID: 158612
   Summary: Not able to select different border thickness
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: marcu...@gmail.com

Description:
I cannot find any function that allows one to choose a thicker border for a
cell/ row/ column left/right. top/bottom.

The only options I see relate to placement, style and colour but no thickness.
These are located as icons on the task bar at the top. I could not find these
functions amongst the dropdown list of available functions! 

Steps to Reproduce:
n/a

Actual Results:
n/a

Expected Results:
n/a


Reproducible: Always


User Profile Reset: No

Additional Info:
Thicker border generated by Excel 2013 edition does appear in Calc but a new
thick border cannot be created by your software.

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

[Bug 60494] UI: Expect minimum split pane height to depend on row 1 text line height and zoom level (now min 2 rows at 66%)

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

gekach...@yahoo.com changed:

   What|Removed |Added

 CC||gekach...@yahoo.com
 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #17 from gekach...@yahoo.com ---
In 7.6.4.1, is possible to get 1 row split using steps A or B.  It may take a
little mouse dragging to get the height just right to show only 1 row, but it
is possible.

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Bug 109182] [META] Cell freezing/fixing/locking bugs and enhancements

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

Bug 60494 Summary: UI: Expect minimum split pane height to depend on row 1 text 
line height and zoom level (now min 2 rows at 66%)
https://bugs.documentfoundation.org/show_bug.cgi?id=60494

   What|Removed |Added

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

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

[Bug 158611] Active cell identification and copy format

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

--- Comment #2 from marcu...@gmail.com  ---
I have just installed and used the 7.6.4.1 version to test the tool out in my
previous comment.

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

[Bug 158611] Active cell identification and copy format

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

--- Comment #1 from marcu...@gmail.com  ---
I used an *arrow key* to move/ slide onto the next cell. 

I just realised that the tool works if the new cell is selected by clicking
over it.

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

[Bug 158611] New: Active cell identification and copy format

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

Bug ID: 158611
   Summary: Active cell identification and copy format
   Product: LibreOffice
   Version: 7.5.9.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: marcu...@gmail.com

Description:
It would help to have a thick border around the active (selected) cell/s.

Also, I tried using the brush too (to copy format of one cell to another). It
does not work at least not as in Excel!

Steps to Reproduce:
1. click on brush tool
2. move to another cell
3. nothing happens

Actual Results:
nothing

Expected Results:
cell format should change to that of previously selected cell (when the brush
tool was clicked/ selected)


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a

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

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

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

--- Comment #66 from marcu...@gmail.com  ---
I too experience this issue with Calc so far. I started using LibreOffice only
recently and plan to gradually migrate completely to it.

The scrolling speed is frustrating at the very least and I hope that it is
addressed effectively soon.

I use Win 11 Pro on Asus Zenbook Pro 15. My current version of LO is 7.5.9.2. I
am downloading 7.6 which I understand to be a beta version of the next update.

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

[Bug 158609] FILEOPEN maximum columns exceeded warning with ods file saved with M. Office 16

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

ady  changed:

   What|Removed |Added

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

--- Comment #1 from ady  ---
MSO Excel saves by default more columns than what LO 7.3 supports by default.

LO 7.4 supports 16384 columns by default.

For version 7.3, the setting to allow such amount of columns is in the advance
options.

IMO, this is not a bug; instead it is a question for
. Please use it next time before reporting a bug.

I'll close this as NAB. If there is a reason not to close it, feel free to
reopen it; please be specific about the reasons in such case.

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

[Bug 158599] Hangs when opening options menu

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

m.a.riosv  changed:

   What|Removed |Added

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

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

Please paste here the information on Menu/Help/About LibreOffice (There is an
icon to copy)

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

[Bug 158597] FILEOPEN DOCX Numbering in specific file is unexpectedly bold

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Reproducible
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
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 147021] Use std::size() or std::ssize() instead of SAL_N_ELEMENTS() macro

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

--- Comment #45 from Commit Notification 
 ---
Dr. David Alan Gilbert committed a patch related to this issue.
It has been pushed to "master":

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

tdf#147021 Use std::span to avoid SAL_N_ELEMENTS in CustomShape

It will be available in 24.8.0.

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

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

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

[Bug 158601] Page direction not the same as sheet direction

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

--- Comment #3 from ady  ---
(In reply to Eyal Rozenberg from comment #2)

> No

If I may, I would have a request then. Would you please post the exact steps in
order to arrive to the 2 different settings (in the UI) you are asking about?

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

[Bug 147021] Use std::size() or std::ssize() instead of SAL_N_ELEMENTS() macro

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

--- Comment #44 from Commit Notification 
 ---
Dr. David Alan Gilbert committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/4a49d7a3a98ccdca52ea0a4475d05235a111ec0a

tdf#147021 Use std::span to avoid SAL_N_ELEMENTS in CustomShape

It will be available in 24.8.0.

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

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

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

[Bug 147021] Use std::size() or std::ssize() instead of SAL_N_ELEMENTS() macro

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

--- Comment #43 from Commit Notification 
 ---
Dr. David Alan Gilbert committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/82f30ac55a90a0f0915d4016c760c5c38db087f1

tdf#147021 Use std::span to avoid SAL_N_ELEMENTS in CustomShape

It will be available in 24.8.0.

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

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

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

[Bug 158595] Performance : PDF export is taking 1min 20 sec

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

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m.a.riosv  ---
No reproducible opening with LibreOffice and exporting to pdf.
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
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 158592] Control anchored and fit to cell jumps to different cell when changing Anchor setting in Control Properties

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m.a.riosv  ---
Reproducible
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
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 145716] Saving document as Word (docx) does not preserve paragraph space above/below correctly

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 CC||kelem...@ubuntu.com

--- Comment #10 from Gabor Kelemen (allotropia)  ---
Created attachment 191328
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191328&action=edit
The docx version in Word after enabling the HTML paragraph auto spacing thingy

And a bit of experimenting resulted in this: the "Don't use HTML paragraph auto
spacing" option (whatever this means) is the key to preserving the numbered
paragraphs spacing in MSO formats.

So we need to automatically add the compat option:


Interestingly saving the example file in RTF format also keeps the layout both
in Writer and Word. Looking into the specification there is the \htmautsp
keyword to Use HTML paragraph auto spacing which is missing from the export -
perhaps a lucky coincidence.

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

[Bug 145716] Saving document as Word (docx) does not preserve paragraph space above/below correctly

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

--- Comment #9 from Gabor Kelemen (allotropia)  ---
Created attachment 191327
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191327&action=edit
Layout options of the doc version in Word

Curiously the doc version has several layout options enabled according to Word,
while the docx version has none.

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

[Bug 145716] Saving document as Word (docx) does not preserve paragraph space above/below correctly

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

--- Comment #8 from Gabor Kelemen (allotropia)  ---
Created attachment 191326
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191326&action=edit
The doc and docx versions in Word, plus the doc converted to docx

The doc version also looks good in Word (somehow my Word 2016 hides the last
paragraph, but 2010 does not - odd), and this good look stays if I convert it
to docx with Word.

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

[Bug 145716] Saving document as Word (docx) does not preserve paragraph space above/below correctly

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

--- Comment #7 from Gabor Kelemen (allotropia)  ---
Created attachment 191325
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191325&action=edit
The example file saved as doc format in Writer and the original odt

So I did a bit of research into this, and looks like the doc export actually
looks the same in Writer as the odt one.

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

[Bug 154369] FILEOPEN DOCX Numbering loses its parastyle-assigned color b/c of applied charstyle

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

--- Comment #7 from Gabor Kelemen (allotropia)  ---
(In reply to Justin L from comment #3)
> Here is something a bit bizarre. in LO, select the entire paragraph and
> change the font colour to red. Now the numbering will show up as green.

This is now bug 158610, thanks for noticing!

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

[Bug 154369] FILEOPEN DOCX Numbering loses its parastyle-assigned color b/c of applied charstyle

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Depends on|158610  |
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||8610


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158610
[Bug 158610] FILEOPEN DOCX Changing font color in numbered list changes font
color of numbering
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158610] FILEOPEN DOCX Changing font color in numbered list changes font color of numbering

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Blocks|154369  |108770
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||4369


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108770
[Bug 108770] [META] DOCX (OOXML) bullet and numbering list-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=154369
[Bug 154369] FILEOPEN DOCX Numbering loses its parastyle-assigned color b/c of
applied charstyle
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108770] [META] DOCX (OOXML) bullet and numbering list-related issues

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Depends on||158610


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158610
[Bug 158610] FILEOPEN DOCX Changing font color in numbered list changes font
color of numbering
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 154369] FILEOPEN DOCX Numbering loses its parastyle-assigned color b/c of applied charstyle

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Depends on||158610


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158610
[Bug 158610] FILEOPEN DOCX Changing font color in numbered list changes font
color of numbering
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158610] New: FILEOPEN DOCX Changing font color in numbered list changes font color of numbering

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

Bug ID: 158610
   Summary: FILEOPEN DOCX Changing font color in numbered list
changes font color of numbering
   Product: LibreOffice
   Version: 7.0.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: bibisected, bisected, regression
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: kelem...@ubuntu.com
CC: nem...@numbertext.org
Blocks: 154369

Created attachment 191324
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191324&action=edit
The example file after setting one numbered paragraph to red font

When a numbered paragraph of attachment 186193 from bug 154369 is changed
color, the numbering gets the parent paragraphs green formatting and font size.

1. Open attachment 186193 
2. Select one of the 1-4 numbered paragraphs in full
3. On the toolbar set a different font color
-> The numbering becomes green and slightly larger font size, just like the A /
B numbered paragraphs above.

Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 5ff64bfcf9bb8c27670c4cb44a778105008407ed
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
Calc: threaded

Bibisected in linux-6.4 to:
https://git.libreoffice.org/core/+/11768f901b4c9e34e598187a31adf5028377c65c

author  László NémethThu Apr 16 11:47:57 2020 +0200
committer   Michael Stahl Mon Apr 27 11:30:42
2020 +0200

tdf#127606 DOCX lists: fix unchangeable formatting

Adding CC to: László Németh


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154369
[Bug 154369] FILEOPEN DOCX Numbering loses its parastyle-assigned color b/c of
applied charstyle
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158604] UI: Warning when applying Autoformat > Styles for a large (empty) range

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

--- Comment #3 from Eyal Rozenberg  ---
> If you apply autoformat -> styles LibreOffice will Freeze/hang for long time

This is the problem. Why can't we interrupt such operations while they're
ongoing?

There are are operations which could potentially take a long time; like -
parsing a huge input CSV for example.

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

[Bug 135350] Weird direction & alignment issues in new documents when switching to RTL

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

--- Comment #6 from Eyal Rozenberg  ---
(In reply to Stéphane Guillou (stragu) from comment #5)

That was quite right.

I want to try and escalate this bug. While it is not terrible in itself (it
goes away when you play with the alignment and direction a little) - it is
highly disorienting behavior for newbie users, who need to understand what
button states mean, what the difference is between direction and alignment etc.
It  also has very high visibility. It gives RTL users a really bad impression
of LibreOffice

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

[Bug 103342] [META] Font substitution bugs and enhancements

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

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||158589


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158589
[Bug 158589] Add option to save Font Replacement Table
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103342] [META] Font substitution bugs and enhancements

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

Bug 158589 Summary: Add option to save Font Replacement Table
https://bugs.documentfoundation.org/show_bug.cgi?id=158589

   What|Removed |Added

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

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

[Bug 158589] Add option to save Font Replacement Table

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

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
Already available as an extension, YMMV:

https://extensions.libreoffice.org/en/extensions/show/42001

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


Referenced Bugs:

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

[Bug 157415] Import & Export mechanism for the font substitution table

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||j22...@gmail.com

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

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

[Bug 158606] Libreoffice crashes when i open any document

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

Julien Nabet  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||serval2...@yahoo.fr
 Status|UNCONFIRMED |NEEDINFO

--- Comment #2 from Julien Nabet  ---
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?

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

[Bug 158607] Libreoffice crashes when i open any document

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---


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

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

[Bug 158606] Libreoffice crashes when i open any document

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

--- Comment #1 from Julien Nabet  ---
*** Bug 158607 has been marked as a duplicate of this bug. ***

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

[Bug 158604] UI: Warning when applying Autoformat > Styles for a large (empty) range

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

--- Comment #2 from Telesto  ---
(In reply to Eyal Rozenberg from comment #1)
> So, why am I CCed? :-)

Well mostly because of your idea's/opinions/suggestions on plenty of topics and
the ability of expressing those clearly. Or put it differently I appreciate
your view.. But well it's totally voluntary.. If so say, I'm uninterested, also
fine.

But well I should probably added the question: options? instead of blank cc

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

[Bug 121584] Ctrl+LShift, Ctrl+RShift not setting direction in comments

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

--- Comment #7 from Eyal Rozenberg  ---
(In reply to BogdanB from comment #6)
> Working for me with
> Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community

What build is that? The nightly builds are 24.2.something :-(

> Eyal, please could you retest?
> 
> I am inside the comment and press Ctrl+leftShift, Or Ctrl+rightShift, and
> the comment is changing the place it is positioned.

I now encounter the bug intermittently; and it may have something to do with
bug 135350.

Instructions:

1. Have RTL-CTL support enabled (maybe also CJK? Probably doesn't matter)
2. Create a new writer document (default page style should be RTL and so should
the first pargraph)
3. Type in שלום
4. Select the word you've typed (not the whole paragraph)
5. Insert a comment (for me, the comment paragraph direction is RTL, which I
would say is a bug, but never mind)
6. Press Ctrl+LShift and Ctrl+RShift a couple of times

Expected Result:
Comment direction changes back and forth

Actual Result:
Nothing Happens

But - if I now, say, lose application focus, gain it again, click the שלום,
then click the body of the comment again, and repeat step 6 - I now _do_ get a
direction change.




Build info:

Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 516f800f84b533db0082b1f39c19d1af40ab29c8
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: he-IL (en_IL); UI: en-US

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

[Bug 158609] FILEOPEN maximum columns exceeded warning with ods file saved with M. Office 16

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

Jérôme  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[Bug 158609] New: FILEOPEN maximum columns exceeded warning with ods file saved with M. Office 16

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

Bug ID: 158609
   Summary: FILEOPEN maximum columns exceeded warning with ods
file saved with M. Office 16
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jerome.bo...@laposte.net

Created attachment 191323
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191323&action=edit
maximum columns exceeded warning

First I saved an ods file with this version :
---
Version: 7.3.7.2.M5 (x64) / LibreOffice Community
Build ID: cf0a4747cef76399d7acd30c4dcda7a78e7973c2
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: threaded
---

Next I sent it to someone who added some content with M. Excel 16.0. Below is
the extract of meta.xml inside the ods file he sent back to me :
---

MicrosoftOffice/16.0 MicrosoftExcel/CalculationVersion-27029

---

I had a warning when opening his ods file, in French : "Impossible de charger
la totalité des données : dépassement du nombre maximal de colonnes par
feuille".

When I click "ok", I can edit the ods file and it seems correct.

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

[Bug 83350] RTL: Status bar fields aligned to the left

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

--- Comment #10 from BogdanB  ---
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Bug 83350] RTL: Status bar fields aligned to the left

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #9 from BogdanB  ---
Created attachment 191322
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191322&action=edit
screenshot

Everything seems worse in the status bar in RTL.

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

[Bug 124987] Text Box anchored to page in a Right-to-left document doesn't appear

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #5 from BogdanB  ---
Also in
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ar-JO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Bug 62932] EDITING: No option to change LTR writing direction to RTL for comment edit box in Impress

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #10 from BogdanB  ---
The same in
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: he-IL (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Bug 95539] Option + arrow does not work properly when RTL is enabled

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #15 from BogdanB  ---
The same in
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI

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

--- Comment #29 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/847d925a437f5a3c089978c7d0b8f175a1a19176

tdf#155876 UI cmds Calc-Format menu (25)

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

[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:24.2.0   |target:24.2.0 target:24.8.0

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

[Bug 121584] Ctrl+LShift, Ctrl+RShift not setting direction in comments

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #6 from BogdanB  ---
Working for me with
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

Eyal, please could you retest?

I am inside the comment and press Ctrl+leftShift, Or Ctrl+rightShift, and the
comment is changing the place it is positioned.

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

[Bug 145918] double quotes not "glued" to word across line boundaries in R-T-L

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g

--- Comment #2 from BogdanB  ---
Also in
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fb3970a1a599eae2447f6746597843434ee758b
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Bug 105948] [META] Undo/Redo bugs and enhancements

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

Tex2002ans  changed:

   What|Removed |Added

 Depends on||89816


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=89816
[Bug 89816] Image anchored to paragraph doesn't move back after entering and
deleting a new paragraph above
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 89816] Image anchored to paragraph doesn't move back after entering and deleting a new paragraph above

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

Tex2002ans  changed:

   What|Removed |Added

 Blocks||105948

--- Comment #12 from Tex2002ans  ---
I can still reproduce in:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

- - -

Same exact thing happens if you:

1. Press ENTER before "Consetetur sadipscing elitr," paragraph right above the
image.
2. Press Edit > Undo (Ctrl+Z).

The image will not return to the original position.

(Based on that, I'm adding the "Undo-Redo" metabug to this too.)


Referenced Bugs:

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

[Bug 158604] UI: Warning when applying Autoformat > Styles for a large (empty) range

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

--- Comment #1 from Eyal Rozenberg  ---
So, why am I CCed? :-)

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

[Bug 158608] The right context menu doesn't start with spelling suggestions in Calc (it does in Writer)

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

--- Comment #1 from Telesto  ---
Created attachment 191321
  --> https://bugs.documentfoundation.org/attachment.cgi?id=191321&action=edit
Screenshot

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

[Bug 158608] New: The right context menu doesn't start with spelling suggestions in Calc (it does in Writer)

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

Bug ID: 158608
   Summary: The right context menu doesn't start with spelling
suggestions in Calc (it does in Writer)
   Product: LibreOffice
   Version: 24.2.0.0 alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
The right context menu doesn't start with spelling suggestions in Calc (it does
in Writer)

Steps to Reproduce:
1. Open Calc (with English dictionary)
2. Write 'Oeps' (spell checking enabled)
3. Right Click 'Oeps'

Actual Results:
The context menu starts with Ignore all

Expected Results:
Starting with suggestions


Reproducible: Always


User Profile Reset: No

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

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

[Bug 158596] Context menu "Size" with unexpected entries in Kf5 and gen

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

--- Comment #1 from Telesto  ---
Asking myself: Is this related to LibreOffice Dark Appearence? (Tools ->
Options > View > Appearance). Font being black on black or is it truly an empty
line

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

[Bug 158607] New: Libreoffice crashes when i open any document

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

Bug ID: 158607
   Summary: Libreoffice crashes when i open any document
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nejdetv...@gmail.com

Description:
i can open libreoffice program but when i want to open up a documentor create
new document or any other tool it crashes 

Actual Results:
i dont know yet

Expected Results:
that i can use it


Reproducible: Always


User Profile Reset: No

Additional Info:
TO WORK

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

[Bug 158606] New: Libreoffice crashes when i open any document

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

Bug ID: 158606
   Summary: Libreoffice crashes when i open any document
   Product: LibreOffice
   Version: 7.6.4.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nejdetv...@gmail.com

Description:
i can open libreoffice program but when i want to open up a documentor create
new document or any other tool it crashes 

Actual Results:
i dont know yet

Expected Results:
that i can use it


Reproducible: Always


User Profile Reset: No

Additional Info:
TO WORK

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

[Bug 158605] New: 1,2 GB memory usage for a spreadsheet with simply a lot of cells with multi-line contents

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

Bug ID: 158605
   Summary: 1,2 GB memory usage for a spreadsheet with simply a
lot of cells with multi-line contents
   Product: LibreOffice
   Version: 24.2.0.0 alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
1,2 GB memory usage for a spreadsheet with simply a lot of cells with
multi-line contents

Steps to Reproduce:
1. Open attachment 151324 (bug 125236)
2. Look at the RAM usage


Actual Results:
1,2 GB with master (x64)
840 with Versie: 6.4.0.2 (x86)
500 Mb with 4.4.7.2 (x86)

Expected Results:
600-700 MB or so for x64


Reproducible: Always


User Profile Reset: No

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

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

[Bug 158544] Pasting unformatted text doesn't work if choosed using keyboard

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

Prokhor  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 158604] UI: Warning when applying Autoformat > Styles for a large (empty) range

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

Telesto  changed:

   What|Removed |Added

Summary|UI: Warning when applying   |UI: Warning when applying
   |Autoformat > Styles to  |Autoformat > Styles for a
   |extreme range   |large (empty) range

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

[Bug 158604] New: UI: Warning when applying Autoformat > Styles to extreme range

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

Bug ID: 158604
   Summary: UI: Warning when applying Autoformat > Styles to
extreme range
   Product: LibreOffice
   Version: 24.2.0.0 alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
UI: Warning when applying Autoformat > Styles to extreme range 

Steps to Reproduce:
1. Open Calc
2. Left click on column A and drag until S
3. Format -> Autoformat Styles -> Choose some box list type

Actual Results:
Observations: 
* It's easy to select an idiotic range (by incident)
* If you apply autoformat -> styles LibreOffice will Freeze/hang for long time

Expected Results:
* Do a suggestion for proper range?
* Or a warning about extend of the selection?
* something else.. 




Reproducible: Always


User Profile Reset: No

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

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

[Bug 158473] Unify lockdown behavior of Options dialog page Calc - Grid

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

Balázs Varga (allotropia)  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com
   |desktop.org |
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

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

[Bug 158472] Unify lockdown behavior of Options dialog page Calc - Print

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

Balázs Varga (allotropia)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED
   Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com
   |desktop.org |

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

[Bug 158601] Page direction not the same as sheet direction

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

Eyal Rozenberg  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

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

[Bug 107332] [META] Calc cell and page styles bugs and enhancements

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||158601


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158601
[Bug 158601] Page direction not the same as sheet direction
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||158601


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158601
[Bug 158601] Page direction not the same as sheet direction
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158601] Page direction not the same as sheet direction

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||43808, 107332


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=43808
[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues
(RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=107332
[Bug 107332] [META] Calc cell and page styles bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158601] Page direction not the same as sheet direction

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

--- Comment #2 from Eyal Rozenberg  ---
(In reply to ady from comment #1)
> If you are referring to the RTL/LTR setting for the worksheet tab (a UI
> setting) vs. the Page Style for the worksheet, I think that recent bug
> reports have proven that users do not agree that they are the same.

No, I'm not talking about where the worksheet tab is placed. I'm talking about
whether the worksheet _itself_ has cells progress from left to right or vice
versa.

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

[Bug 158601] Page direction not the same as sheet direction

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

--- Comment #1 from ady  ---
(In reply to Eyal Rozenberg from comment #0)
> Changing the direction of a worksheet, e.g. from LTR to RTL or the other way
> around, does not change the Page Style's text direction setting, and
> vice-versa.
> 
> AFAICT - this is a bug, and the two settings should be one and the same. Am
> I wrong? If not, please explain why you believe know they should differ.

If you are referring to the RTL/LTR setting for the worksheet tab (a UI
setting) vs. the Page Style for the worksheet, I think that recent bug reports
have proven that users do not agree that they are the same.

Some users might want both to be synced, but others do not. IMO, UI elements
should not be automatically synced or unified with other settings, but rather
we should have options/alternatives for the behavior/location of RTL UI
elements (which may or may not include some kind of syncing). We have these
diverse/conflicting opinions and desires expressed in bugs 157784, 158552,
100584, 157961 and others.

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

[Bug 158603] New: Implement a slide zoom feature (like MS Office has)

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

Bug ID: 158603
   Summary: Implement a slide zoom feature (like MS Office has)
   Product: LibreOffice
   Version: 7.6.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: schlittphil...@mail.de

Description:
MS Office has a function called slide zoom
(https://support.microsoft.com/en-us/office/use-zoom-for-powerpoint-to-bring-your-presentation-to-life-9d6c58cd-2125-4d29-86b1-0097c7dc47d7?ui=de-de&rs=de-de&ad=de)
where you can place slide on another one.
Could you please implement this too, since it's a very nice feature.

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

  1   2   3   >