[Libreoffice-bugs] [Bug 33240] RPT: grouping/sorting silently ignored with "analyze sql: no"

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33240

--- Comment #15 from Robert Großkopf  ---
Bug is still the same in LO 7.3.6.2 on OpenSUSE 15.3 64bit rpm Linux

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

[Libreoffice-bugs] [Bug 142462] LO BASE FILESAVE- too many unwanted backup copies lead to "low disk space" alarm

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142462

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 108542] [META] Chart label bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108542
Bug 108542 depends on bug 41741, which changed state.

Bug 41741 Summary: VIEWING: Callout text size changes when modification in data 
source
https://bugs.documentfoundation.org/show_bug.cgi?id=41741

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 41741] VIEWING: Callout text size changes when modification in data source

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=41741

Rainer Bielefeld Retired  changed:

   What|Removed |Added

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

--- Comment #9 from Rainer Bielefeld Retired  
---
I saw some problems with "Manueller Eingriff ..." callout (character size too
big, different text colors using different LibO versions) with LibO 4.0.0. and
6.0.7.3

No problems at all any longer  reproducible with  Installation of Version:
7.3.3.2 (x64) Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE |  Calc: threaded | Elementary Theme | My
normal User Profile: Text size,background and character color seem ok.

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

[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145266

--- Comment #16 from Buovjaga  ---
(In reply to tex.avery2 from comment #15)
> Hello,
> 
> Same problem with the new Macbook pro 14 pouces, Monterey 12.6.
> 
> Please, try to correct this bug !

Would be easier, if someone bisected it like I said in comment 11.

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

[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145266

Buovjaga  changed:

   What|Removed |Added

   Hardware|ARM |All
Version|7.4.1.2 release |7.2.1.2 release

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

[Libreoffice-bugs] [Bug 117173] Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchL

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117173

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

https://git.libreoffice.org/core/commit/947fe0d89dee75ee43515ef7dfb43837d65a45bc

tdf#119788 tdf#117173 add accessibility NOTIFICATION role

It will be available in 7.5.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.

[Libreoffice-bugs] [Bug 119788] a11y: Distinguish between role STATIC and new role NOTIFICATION

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119788

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

https://git.libreoffice.org/core/commit/947fe0d89dee75ee43515ef7dfb43837d65a45bc

tdf#119788 tdf#117173 add accessibility NOTIFICATION role

It will be available in 7.5.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.

[Libreoffice-bugs] [Bug 119788] a11y: Distinguish between role STATIC and new role NOTIFICATION

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119788

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.5.0

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

[Libreoffice-bugs] [Bug 150658] The behavior of the Formatting toolbar has changed in 7.4.0.3 from 7.3 and prior when copying and pasting individual Writer table rows.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150658

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Libreoffice-bugs] [Bug 150912] Italic and bold graphic glitch with Noto fonts on Arch Linux KDE Plasma when scrolling or editing text

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150912

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 150906] Merged cell collision with application border in "right-to-left sheet" mode

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150906

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 150704] Inserting a new paragraph in Writer generates a lot of warnings in console with debug LO

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150704

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 150702] Inserting a chart in Writer generates a lot of warnings in console with debug LO

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150702

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150848

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

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

[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150848

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 93926] Correct word is corrected to wrong word (Differenzeierbarkit)

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=93926

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 81736] Writer cannot import variable Ref fields from .doc or .docx and instead displays text "Show variable" and "Set variable"

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81736

--- Comment #17 from QA Administrators  ---
Dear Pablo Rodríguez,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 63412] PRINTING Handout: all text in a slide becomes raster picture if raster picture is overlapping any text.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=63412

--- Comment #16 from QA Administrators  ---
Dear Rick Yorgason,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 49259] Writer is too jumpy with images and right clicks

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49259

--- Comment #9 from QA Administrators  ---
Dear Ruslan Kabatsayev,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 41741] VIEWING: Callout text size changes when modification in data source

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=41741

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 33240] RPT: grouping/sorting silently ignored with "analyze sql: no"

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33240

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 136971] Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136971

--- Comment #5 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.

[Libreoffice-bugs] [Bug 132820] UI: Height input box smaller compared to width (document specific)

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132820

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 125154] writer calculation using variable within table does not work with formated numbers

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125154

--- Comment #6 from QA Administrators  ---
Dear Daniel Frost,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 129223] EDITING: Crash if I copy big amount of data and [Windows]+[V] copy history enabled.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129223

--- Comment #6 from QA Administrators  ---
Dear jorge.alfe.512,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 111086] Assertion failure after undo (!"EmptyProperties::SetObjectItemSet() should never be called")

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=111086

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 151181] New: I can't find "Edit Style..." in the keyboard customization functions

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151181

Bug ID: 151181
   Summary: I can't find "Edit Style..." in the keyboard
customization functions
   Product: LibreOffice
   Version: unspecified
  Hardware: Other
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@linna.com

Description:
I wanted to set a custom keyboard shortcut for "Edit Style..." but couldn't
find it. This is on 7.4.2.1 but that version doesn't appear in the version
list.

Steps to Reproduce:
1. Choose Tools->Customize... and click Keyboard
2. Type "Edit Style" or "Edit" or "Style" in the Functions search field

Actual Results:
"Edit Style..." does not appear.

Expected Results:
"Edit Style..." should appear.


Reproducible: Always


User Profile Reset: No



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

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

[Libreoffice-bugs] [Bug 151180] Deleting keyboard shortcuts didn't work

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151180

--- Comment #1 from Nik Gervae  ---
Update: I tried removing the keyboard shortcuts for Left/Center/Right/Justified
and they also are still in the menus.

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

[Libreoffice-bugs] [Bug 151180] New: Deleting keyboard shortcuts didn't work

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151180

Bug ID: 151180
   Summary: Deleting keyboard shortcuts didn't work
   Product: LibreOffice
   Version: 7.4.1.2 release
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@linna.com

Description:
I am using a laptop without dedicated F-keys so I went through the
Customization/Keyboard thing and deleted all those keyboard shortcuts, but they
are still on the menus and they still work.

Steps to Reproduce:
1. Open Tools->Customization... and click Keyboard.
2. Delete any of the keyboard shortcuts with F-keys.
3. Open a menu that has one of the commands you deleted.

Actual Results:
The keyboard shortcut is still listed and still triggers the menu command.

Expected Results:
The keyboard shortcut should be gone.


Reproducible: Always


User Profile Reset: No



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

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

[Libreoffice-bugs] [Bug 151179] New: I can't find command+backslash in the Customize keyboard shortcuts list

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151179

Bug ID: 151179
   Summary: I can't find command+backslash in the Customize
keyboard shortcuts list
   Product: LibreOffice
   Version: 7.4.1.2 release
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@linna.com

Description:
I would like to use command+backslash for a keyboard shortcut but it doesn't
appear to be listed. I noticed that if I type a shortcut, it gets selected, but
nothing happens if I press command+\.

Steps to Reproduce:
1. Open Tools->Customization... and click Keyboard.
2. Press command+\.

Actual Results:
Nothing happens.

Expected Results:
I hoped to be able to select that keyboard shortcut and assign a command to it.


Reproducible: Always


User Profile Reset: No



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

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

[Libreoffice-bugs] [Bug 151178] Include support for Ge'ez zema using multi-line phonetic guides | enhancement

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151178

--- Comment #1 from dawishwis...@gmail.com ---
Created attachment 182673
  --> https://bugs.documentfoundation.org/attachment.cgi?id=182673=edit
example of what i want to be able to do

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

[Libreoffice-bugs] [Bug 151178] New: Include support for Ge'ez zema using multi-line phonetic guides | enhancement

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151178

Bug ID: 151178
   Summary: Include support for Ge'ez zema using multi-line
phonetic guides | enhancement
   Product: LibreOffice
   Version: 7.4.1.2 release
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dawishwis...@gmail.com

Description:
FORMATTING
In Ge'ez there is zema milikits these are little marks above words that
indicate how the hymns should be said. In order to replicate this, phonetic
guides are used. However, phonetic guides aren't supported in impress. Not only
that, some hymns have more than one way of saying the hymn which is why I'm
also asking the phonetic guides to be able to have more than one line.

here is an example:
https://user-images.githubusercontent.com/8098333/190934189-b9e5f794-2036-47a2-8a6a-c6fd2f09ec62.png

Steps to Reproduce:
1.type the hymn
2.try to use phonetic guide, doesnt work
2b. try to type the phonetic guides in writer
3. unable to get phonetic guides for multiple lines

Actual Results:
1.type the hymn
2.try to use phonetic guide, doesnt work
2b. try to type the phonetic guides in writer
3. unable to get phonetic guides for multiple lines

Expected Results:
expected something like this
https://user-images.githubusercontent.com/8098333/190934189-b9e5f794-2036-47a2-8a6a-c6fd2f09ec62.png


Reproducible: Always


User Profile Reset: Yes



Additional Info:
maybe make a separate feature since ge'ez isnt from asian origin, like a
separate ge'ez milikit guide.
also churches primarily use powerpoint so if you can add it into impress first
as opposed to writer

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

[Libreoffice-bugs] [Bug 87687] Merging cells does not move references in equations (Comment 6)

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87687

--- Comment #13 from Tex2002ans  ---
Still not working. Followed steps in comment #6.

Version: 7.4.1.2 (x64) / LibreOffice Community
Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 150473] Function description in "Functions" sidebar should have minimum height

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150473

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 56408] Writer always breaks lines at text direction change

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=56408

--- Comment #25 from Eyal Rozenberg  ---
(In reply to خالد حسني from comment #17)
> This is a bug, change in direction does not create line breaking opportunity.

The first part of this statement does not follow from the second. That is, the
second part is true, but there already is a breaking opportunity before and
after the parentheses regardless of the change in direction.

> There is even an easy way to check this

... and checking shows the line breaking opportunity.

To me it seems this is a bug because the parenthesized word would still fit on
the first line of the two in the sample document. So, it's about why LO thinks
it _must_ break as opposed to it mistakenly thinking it _can_ break.

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

[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145266

tex.ave...@aliceadsl.fr changed:

   What|Removed |Added

Version|7.2.1.2 release |7.4.1.2 release
   Hardware|x86-64 (AMD64)  |ARM

--- Comment #15 from tex.ave...@aliceadsl.fr ---
Hello,

Same problem with the new Macbook pro 14 pouces, Monterey 12.6.

Please, try to correct this bug !

Regards

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

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

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

--- Comment #41 from خالد حسني  ---
(In reply to Munzir Taha from comment #40)
> @خالد حسني
> As usual, your fixes are outstanding. I will test as soon as there is a
> build available.
> 
> Yes, I am aware that less broken results show when formatting marks are
> hidden as in the original bug I filed. So, now remains the broken characters
> like LAM ALEF combinations and ligatures.
> 
> I am not sure whether breaking shaping should be the same bug as breaking
> kerning.zYes, broken Arabic ligature shaping is similar to kerning because
> the text is still correct though not suitable for professional work.
> However, breaking shaping is more serious and the text is incorrect and can
> be handled in a different way.


Kerning (glyph positioning in general) and shaping (glyph substitution in
general) are done in the same step, there is no way to fix one but not the
other, regardless which is more severe. The underlying issue is the same; when
LibreOffice sees a formatting change it splits the text and processes each
portion separately.

> In Scribus e.g. the kerning doesn't break due to color changes. For Arabic,
> Scribus still doesn't know how to handle the coloring for single characters
> of combinations correctly so it changes the color of the whole ligature,
> which is not perfect but at least the shaping is intact.

This is orthogonal to the issue here. There is no single answer for how to
partially color a ligature, since it is a single glyph. Some applications will
apply the color of the first component to the ligature (Chrome and I think MS
Office do this), others will use a mask and color the part of the glyph up to
where the cursor is inserted (Firefox is actually the only application I know
that does this, and it is not without issues, see
https://faultlore.com/blah/text-hates-you/#style-can-change-mid-ligature).

This issue is about the shaping part, once this is done (if it ever gets done,
it is not a simple task), we can then decide how to partially color ligature
glyphs).

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

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

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

--- Comment #40 from Munzir Taha  ---
@خالد حسني
As usual, your fixes are outstanding. I will test as soon as there is a build
available.

Yes, I am aware that less broken results show when formatting marks are hidden
as in the original bug I filed. So, now remains the broken characters like LAM
ALEF combinations and ligatures.

I am not sure whether breaking shaping should be the same bug as breaking
kerning. Yes, broken Arabic ligature shaping is similar to kerning because the
text is still correct though not suitable for professional work. However,
breaking shaping is more serious and the text is incorrect and can be handled
in a different way.

In Scribus e.g. the kerning doesn't break due to color changes. For Arabic,
Scribus still doesn't know how to handle the coloring for single characters of
combinations correctly so it changes the color of the whole ligature, which is
not perfect but at least the shaping is intact.

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

[Libreoffice-bugs] [Bug 151177] New: Added page background images disappear from library

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151177

Bug ID: 151177
   Summary: Added page background images disappear from library
   Product: LibreOffice
   Version: 7.4.1.2 release
  Hardware: Other
OS: macOS (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@linna.com

Description:
I added some images to use as page backgrounds, expecting them to remain
availalble to choose in the catalogue of images. But they disappear randomly.

Steps to Reproduce:
1.Add an image to a Page Style/Area.
2.Apply it, or not, doesn't seem to matter.
3.Close the Page Style dialog.
4.Reopen the Page Style dialog.


Actual Results:
The added images aren't there, most of the time.

Expected Results:
The added images should be there.


Reproducible: Sometimes


User Profile Reset: No



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

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

[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150848

--- Comment #8 from tor...@yahoo.com ---
Created attachment 182670
  --> https://bugs.documentfoundation.org/attachment.cgi?id=182670=edit
file with various tabs and indents.

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

[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150848

--- Comment #7 from tor...@yahoo.com ---
(In reply to Heiko Tietze from comment #6)
> the sample document has quite many modifications to the default.
● Does Writer get confused by many modifications? How many?
> 
> I don't see an issue.

● You might see it with the new document, tabs6.odt:
*Elements AA, BB, BC, HH and DD conform to specs and user expectations;
*CC looks like BB and DD but was obtained by hitting the TabKey twice
—unexpected. If TabKey had ignored the indent, a single TabKey hit would have
entered a Tab filled by underline beginning at the left margin (according to
hangingIndent definition), like AA or BC.

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

[Libreoffice-bugs] [Bug 151154] Change category "draw" in Template Manager and make it translatable

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151154

--- Comment #4 from Rafael Lima  ---
Created attachment 182669
  --> https://bugs.documentfoundation.org/attachment.cgi?id=182669=edit
Template Manager categories after patch

(In reply to Laurent BP from comment #3)
> I tried to deep in this bug but I was not able to find a solution.
> 
> Categories name are defined in TEMPLATE_LONG_NAMES_ARY[]:
> https://opengrok.libreoffice.org/xref/core/sfx2/inc/doctempl.
> hrc?r=144057a5#27
> I added a line
> +NC_("TEMPLATE_LONG_NAMES_ARY", "Draw"),
> 
> as well as in TEMPLATE_SHORT_NAMES_ARY[]:
> https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/doctemplates.
> cxx?r=91ba9654#483
> I added a line at the same position
> +"draw",

This is exactly what I did. However, for it to take effect you need to be on a
clear user profile. You need to either be on safe mode or apply the "Reset
settings and user interface modifications" option to see the new category name.

Here's a screenshot I took after applying the patch and resetting the user
profile.

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

[Libreoffice-bugs] [Bug 151174] sidebar transparency slider isn't hidden when it does not apply

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151174

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 CC||79045_79...@mail.ru
 Status|UNCONFIRMED |NEW
   Keywords||bibisectRequest
 Ever confirmed|0   |1

--- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> ---
Confirm the problem in

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 943177e0f8074753db25d9a56d15f8010a755ffc
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

I couldn't to bisect it myself because the Area section layout was changed
inside 7.4 development path and there is no the transparency slider in oldest
step in bisect repo for Linear variant at least (I just try to triage the
report with Linear variant).

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

[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102283
Bug 102283 depends on bug 42859, which changed state.

Bug 42859 Summary: Add settings button for Slide pane to make it easy to 
configure
https://bugs.documentfoundation.org/show_bug.cgi?id=42859

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

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

[Libreoffice-bugs] [Bug 107817] [META] Impress UI/UX bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107817
Bug 107817 depends on bug 42859, which changed state.

Bug 42859 Summary: Add settings button for Slide pane to make it easy to 
configure
https://bugs.documentfoundation.org/show_bug.cgi?id=42859

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

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

[Libreoffice-bugs] [Bug 42859] Add settings button for Slide pane to make it easy to configure

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42859

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #13 from V Stuart Foote  ---
The ++F10 global LibreOffice dock window frame action works well
on this and other panels without a specific View -> Dock frame menu. 

WFM and IMHO => WF

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

[Libreoffice-bugs] [Bug 151154] Change category "draw" in Template Manager and make it translatable

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151154

Laurent BP  changed:

   What|Removed |Added

 CC||jumbo4...@yahoo.fr

--- Comment #3 from Laurent BP  ---
I tried to deep in this bug but I was not able to find a solution.

Categories name are defined in TEMPLATE_LONG_NAMES_ARY[]:
https://opengrok.libreoffice.org/xref/core/sfx2/inc/doctempl.hrc?r=144057a5#27
I added a line
+NC_("TEMPLATE_LONG_NAMES_ARY", "Draw"),

as well as in TEMPLATE_SHORT_NAMES_ARY[]:
https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/doctemplates.cxx?r=91ba9654#483
I added a line at the same position
+"draw",

In addition, templates directories are declared in directory_ooo.scp
https://opengrok.libreoffice.org/xref/core/scp2/source/ooo/directory_ooo.scp?r=14c7bc1c#602
I added this declaration:
+Directory gid_Dir_Template_Common_Draw
+ParentID = gid_Dir_Template_Common;
+DosName = "draw";
+End
+

But all that has no effect :-( I'm still missing something

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

[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering "Slides pane" onto current slide with edit focus

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151170

V Stuart Foote  changed:

   What|Removed |Added

Summary|Need mechanism for  |Need mechanism for
   |re-centering slide pane |re-centering "Slides pane"
   |(slide sorter) on current   |onto current slide with
   |slide   |edit focus

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

[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102283

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||151170


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151170
[Bug 151170] Need mechanism for re-centering slide pane (slide sorter) on
current slide
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering slide pane (slide sorter) on current slide

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151170

V Stuart Foote  changed:

   What|Removed |Added

 Blocks||102283
 OS|Linux (All) |All
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||olivier.hallot@libreoffice.
   ||org, sdc.bla...@youmail.dk,
   ||vstuart.fo...@utsa.edu

--- Comment #2 from V Stuart Foote  ---
(In reply to Eyal Rozenberg from comment #1)

+1, the slide/page "Slides/Pages pane" needs a control to scroll the pane to
expose the active slide/page with edit focus.  

Currently, except for the dragging the thumb of the scrollbar, it is much too
easy to unintentionally change focus to a different slide/page present in the
pane.

Providing an UNO action to scroll the pane to expose the Slide/Page with edit
focus--for use on keyboard, menu and context menu actions would be very
helpful.

=-=-=

As an aside for documentation:

> I never get the name of this part of the window right... do we call it the
> slide sorter? The slide pane? The slide side-bar?

It is the sd "LEFT PANE", with UNO cmds available to toggle it inactive.

In Impress it is uno.leftPaneImpress and menu labeled 'Slide Pane'

In Draw it is uno.leftPaneDraw and menu labeled 'Page Pane'

But in the Impress UI it is labeled 'Slides', and in Draw UI it is labeled
'Pages' 

Functionally the sd Left Pane, aka "Slides pane" or "Pages pane" in the module
guides documentation, can be used to manage slides/pages, e.g. add, duplicate,
hide, delete, move for the listed slide/page objects.

The Left Pane is incorrectly referred to as the 'Slide Sorter'. That labeling
is for a specific editing "view mode" of the Impress workspace--not available
in Draw. 

And the LO help even has the toggle article named "slidesorter.html" adding to
the confusion, and that all could probably be clarified.  @Olvier, Seth?


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103381
Bug 103381 depends on bug 146844, which changed state.

Bug 146844 Summary: PIVOTTABLE  Repeated pivot item labels are text, even if 
original is number
https://bugs.documentfoundation.org/show_bug.cgi?id=146844

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |WORKSFORME

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

[Libreoffice-bugs] [Bug 146844] PIVOTTABLE Repeated pivot item labels are text, even if original is number

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146844

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> ---
Nice, thanks. So closed as WFM (because we don't know what was the patch)

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

[Libreoffice-bugs] [Bug 146844] PIVOTTABLE Repeated pivot item labels are text, even if original is number

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146844

--- Comment #3 from Nis Jørgensen  ---
Confirming that this is fixed in 7.4.1.2.

I am not certain of procedures around here, but I believe the status of this
bug could be changed to RESOLVED.

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

[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150715

Noel Grandin  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150715

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

https://git.libreoffice.org/core/commit/916d30ba7e8a5293f57ec04258f6c3839736295e

tdf#150715 Animations in LO Impress do not work properly

It will be available in 7.5.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.

[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150715

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.5.0

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

[Libreoffice-bugs] [Bug 141279] REGRESSION: Overwriting a file open in LibreOffice succeeds in recent builds, should fail

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141279

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151176

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #2 from Mike Kaganski  ---
Indeed, it's strange that Windows (or any software) can't use special file open
mode created specifically for backup purposes: note e.g.
FILE_FLAG_BACKUP_SEMANTICS in CreateFile documentation [1].

However, it would be still be interesting to learn exact reproduction steps,
and the logs; only one thing should be taken into account first. Recently,
LibreOffice file locking had been changed (see tdf#141279), so it could change
in the last program versions.

[1]
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilew

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

[Libreoffice-bugs] [Bug 150616] FILESAVE PDF Table row disappears from complex table after CLI PDF export

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150616

Kevin Suo  changed:

   What|Removed |Added

Version|7.4.0.3 release |7.3.2.2 release
 CC||suokunl...@126.com

--- Comment #7 from Kevin Suo  ---
This also happens in 7.3 branch. The commit which caused this regression was
also cherry-picked to 7.3 (version 7.3.2.0.0+)
https://gerrit.libreoffice.org/c/core/+/129845

Revise version field to 7.3.2.2 accordingly.

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

[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151176

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151176

Eike Rathke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTOURBUG

--- Comment #1 from Eike Rathke  ---
Blame Windows for not being able to backup files that are opened exclusive by
an application.

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

[Libreoffice-bugs] [Bug 150658] The behavior of the Formatting toolbar has changed in 7.4.0.3 from 7.3 and prior when copying and pasting individual Writer table rows.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150658

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dgp-m...@gmx.de
 Resolution|--- |NOTABUG

--- Comment #1 from Dieter  ---
I confirm the described behaviour with

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

but for me it sounds like a bug, that has been fixed. It's the normal behaviour
of every text, that you copy and paste (doesn't matter, if source text is from
another document, part of a table or not). If you want to retain actual (bold)
formatting you have to insert text as unformatted text.

=> RESOLVED NOTABUG

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

[Libreoffice-bugs] [Bug 115645] Should be able to permanently delete comments with track changes enabled.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115645

--- Comment #12 from gutkowski  ---
I don't understand how someone could accept merely comment delete.
What precisely would you do if you wanted to recover 25 TC erased comments? I
disagree with the statement "WontFix" (which stands for "Should Never Be Fixed,
even if a developer"). 
https://cookie-clicker2.co

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

[Libreoffice-bugs] [Bug 61242] Customise comments background color in Writer

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61242

--- Comment #29 from gutkowski  ---
The nice comments to ranges option, which uses a backdrop color similar to the
comment box, has made it even more urgent.
https://geometrydash-free.com

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

[Libreoffice-bugs] [Bug 107899] [META] PPTX paragraph-related issues

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107899

Aron Budea  changed:

   What|Removed |Added

 Depends on||151134


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151134
[Bug 151134] FILESAVE PPTX: indentation of second (and other) textbox(es)
shifts to the left
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151134] FILESAVE PPTX: indentation of second (and other) textbox(es) shifts to the left

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151134

Aron Budea  changed:

   What|Removed |Added

  Regression By||Attila Bakos (NISZ)
 Blocks||107899
   Keywords||bibisected, bisected,
   ||regression
 CC||aron.bu...@gmail.com,
   ||nem...@numbertext.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||1903,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||7152

--- Comment #4 from Aron Budea  ---
This is actually a regression in 7.2, bibisected to the following commit,
bibisected using repo bibisect-linux-64-7.2. Adding CC: to Attila Bakos (NISZ)
and László Németh.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=b6b02e0b4c9d739836e1f61a886ea45b01e6696e
author  Attila Bakos (NISZ)
2021-04-20 13:02:44 +0200
committer   László Németh2021-04-29 10:48:27
+0200

tdf#111903 tdf#137152 PPTX export: fix placeholders


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107899
[Bug 107899] [META] PPTX paragraph-related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 56408] Writer always breaks lines at text direction change

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=56408

خالد حسني  changed:

   What|Removed |Added

 CC||j3frea+documentfoundation@g
   ||mail.com

--- Comment #24 from خالد حسني  ---
*** Bug 146710 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 112812] [META] Hebrew language-specific RTL issues

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112812
Bug 112812 depends on bug 146710, which changed state.

Bug 146710 Summary: Incorrect wrapping of neutral characters in CTL
https://bugs.documentfoundation.org/show_bug.cgi?id=146710

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 146710] Incorrect wrapping of neutral characters in CTL

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146710

خالد حسني  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE
 CC||kha...@aliftype.com

--- Comment #2 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 151165] [EDITING] [DOCUMENTATION] ISODD and ISEVEN behavior

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151165

Eike Rathke  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |er...@redhat.com
   |desktop.org |
 Status|NEW |ASSIGNED
Version|7.3.6.2 release |Inherited From OOo

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

[Libreoffice-bugs] [Bug 151176] New: windows 10 backup failure whenever I have a LibreOffice file open

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151176

Bug ID: 151176
   Summary: windows 10 backup failure whenever I have a
LibreOffice file open
   Product: LibreOffice
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: collinca...@gmail.com

Description:
Over the past few months I've had several (many) automatic Backup failures.
Only recently, on a whim, did I try closing LO files before going to bed for
the auto Backup. Since then, without fail, it has been successful. Except that,
yesterday, on a whim, I manually started Backup with an open LO file running.
Fail.
If you're interested I will replicate a failure and give you Error notices.
whatever. Basically, I remember "Failure to produce shadow copy" "timeout"
"refer to VSS & SPP event logs"

Steps to Reproduce:
1. see above
2.
3.

Actual Results:
see above

Expected Results:
see above


Reproducible: Always


User Profile Reset: No



Additional Info:
Although I've rated it as "minor" it's only minor once I realised the
connection between LO and Backup.

Getting to that realisation was pure chance!

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

[Libreoffice-bugs] [Bug 150409] Style inspector: CJK & CTL properties should never be hidden

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150409

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

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

tdf#150409 CJK properties shouldn't be hidden in Style Inspector

It will be available in 7.5.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.

[Libreoffice-bugs] [Bug 150409] Style inspector: CJK & CTL properties should never be hidden

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150409

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.5.0

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

[Libreoffice-bugs] [Bug 126574] description of macro security level settings is misleading or wrong

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126574

--- Comment #3 from Toni Dietze 
 ---
The issue is still present on current master:

https://git.libreoffice.org/core/+/567b4281b96f56ce48d3feb57522255b06816f9b/xmlsecurity/uiconfig/ui/securitylevelpage.ui

I also checked that it is still present in the packaged version on Arch Linux:

Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
7.3.6-2
Calc: threaded

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

[Libreoffice-bugs] [Bug 98682] Wrong text direction after copy/paste from web browser to LibreOffice

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98682

خالد حسني  changed:

   What|Removed |Added

 CC||kha...@aliftype.com

--- Comment #30 from خالد حسني  ---
I think this a feature, not a bug. When opening a blank document in an RTL
locale, the default page style will have direction set to Right To Left, and
paragraph direction is not explicitly set. This, I think, under the assumption
that if you are using an RTL locale you are most likely to be creating RTL
documents. The reverse is true as well, if the locale is LTR the page direction
will be LTR.

The best fix is for the user to set the page direction explicitly, or when
mixing RTL and LTR text, set the direction of the paragraphs.

We can try to detect paragraph direction based in the pasted content, but this
seems to be a fragile thing to do (what if one is pasting into an existing
paragraph).

Alternatively we might want an “auto” paragraph direction setting that uses the
direction from the paragraph content, but that is a much bigger change.

My suggestion is to close as NOTABUG.

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

[Libreoffice-bugs] [Bug 151156] File not found

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151156

Rafael Lima  changed:

   What|Removed |Added

 CC||rafael.palma.l...@gmail.com

--- Comment #2 from Rafael Lima  ---
I was having a similar problem using the help when I built it locally. When you
press F1 LibreOffice creates a temporary file in /tmp which cannot be accessed
by Firefox snap (see [1]).

I fixed it by changing the temporary folder used by LO (Tools - Options -
Paths).

[1] https://bugs.launchpad.net/snapd/+bug/1972762

Try creating a temporary folder in your user directory (f.i.
/home/your_user/tmp) and set it as the temporary folder used by LO. Maybe this
will fix the issue.

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

[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112810
Bug 112810 depends on bug 150726, which changed state.

Bug 150726 Summary: Wrong rendering of characters for colored Arabic text when 
enabling "Toggle formatting marks"
https://bugs.documentfoundation.org/show_bug.cgi?id=150726

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71732
Bug 71732 depends on bug 150726, which changed state.

Bug 150726 Summary: Wrong rendering of characters for colored Arabic text when 
enabling "Toggle formatting marks"
https://bugs.documentfoundation.org/show_bug.cgi?id=150726

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151173] Shadow appears before object entrance animation is scheduled

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151173

Eyal Rozenberg  changed:

   What|Removed |Added

   Keywords||needsDevEval

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

[Libreoffice-bugs] [Bug 107580] [META] Area content panel of the Properties deck/tab of the sidebar

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107580

stragu  changed:

   What|Removed |Added

 Depends on||151174


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151174
[Bug 151174] sidebar transparency slider isn't hidden when it does not apply
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151174] sidebar transparency slider isn't hidden when it does not apply

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151174

stragu  changed:

   What|Removed |Added

 Blocks||107580
   Keywords||regression


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107580
[Bug 107580] [META] Area content panel of the Properties deck/tab of the
sidebar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151175] New: Images of a presentation are distorted when the aspect ratio is changed

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151175

Bug ID: 151175
   Summary: Images of a presentation are distorted when the aspect
ratio is changed
   Product: LibreOffice
   Version: 7.3.6.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m.gabrielboe...@googlemail.com

Description:
If you change the aspect ratio of an existing Impress presentation (for example
4:3 to 16:9) images and also forms/symbols etc. end distorted. It seems their
size is not adjusted, depending on the selected aspect ratio.

"Workaround": selecting "set to original size" restores the correct aspect
ratio of the picture, but sets it also to the original size, so that it have to
be resized by hand. This is not working for rotated pictures.

Steps to Reproduce:
1. Create a presentation with an aspect ratio of your choice and fill in some
pictures.
2. Change the aspect ratio of the slides.


Actual Results:
The images/forms/objects etc. are distorted and have a wrong aspect ratio.

Expected Results:
The images/forms/objects should have a correct aspect ratio and should not be
distorted.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
none

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

[Libreoffice-bugs] [Bug 151165] [EDITING] [DOCUMENTATION] ISODD and ISEVEN behavior

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151165

Eike Rathke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Severity|normal  |minor
 Ever confirmed|0   |1

--- Comment #1 from Eike Rathke  ---
The help documentation
https://help.libreoffice.org/7.4/en-US/text/scalc/01/04060104.html?DbPAR=CALC#bm_id3156034
says "If Value is not an integer any digits after the decimal point are
ignored. The sign of Value is also ignored."
and that is what happens.

Function Wizard wording is wrong.

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

[Libreoffice-bugs] [Bug 151174] New: sidebar transparency slider isn't hidden when it does not apply

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151174

Bug ID: 151174
   Summary: sidebar transparency slider isn't hidden when it does
not apply
   Product: LibreOffice
   Version: 7.4.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stephane.guil...@member.fsf.org

Description:
This regression shows the transparency slider for a shape even when the
transparency setting does not make use of that control.

Steps to Reproduce:
1. Open Writer (or another component that can draw shapes)
2. Insert > Shape > Basic shapes > Rectangle, draw a rectangle
3. Sidebar > Properties > Area > Transparency dropdown, select something other
than "None" or "Solid"
4. Select the same setting once more

Actual Results:
The first time the transparency setting is selected, the slider is still
visible. Selecting the same setting once more makes the slider disappear.

Expected Results:
The slider should be hidden directly when the setting is selected, like in
previous versions.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Slider is hidden properly in:

Version: 7.3.6.2 / LibreOffice Community
Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

but is not hidden on transparency setting selection in:

Version: 7.4.1.2 / LibreOffice Community
Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 139962] Creating a new .odt file from Win Explorer does not use default template

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139962

Laurent BP  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |jumbo4...@yahoo.fr
   |desktop.org |
 Status|NEW |ASSIGNED
 CC||jumbo4...@yahoo.fr

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

[Libreoffice-bugs] [Bug 151166] [FILEOPEN] NUMBERS codec missing functions

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151166

Eike Rathke  changed:

   What|Removed |Added

Product|LibreOffice |Document Liberation Project
 Ever confirmed|0   |1
   Keywords||difficultyInteresting,
   ||easyHack, skillCpp,
   ||skillDebug
Version|7.3.6.2 release |unspecified
 Status|UNCONFIRMED |NEW
  Component|Calc|libetonyek
   Severity|normal  |enhancement

--- Comment #3 from Eike Rathke  ---
Appears to be this map
https://opengrok.libreoffice.org/xref/libetonyek/src/lib/IWAParser.cpp?r=9c3a8cb8=116710=3603#3537

Tagging this as EasyHack, with some knowledge and/or debugging with a completed
Numbers document the mapping could be enhanced.

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

[Libreoffice-bugs] [Bug 151016] Start Center: Thumbnail filter: hamburger menu icon lacks contrast and does not adapt dark mode

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151016

Caolán McNamara  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||riz...@libreoffice.org

--- Comment #13 from Caolán McNamara  ---
This icon is icon-themes/sukapura/sfx2/res/menu.png

caolanm->rizmut: Maybe the bars are a little faint?

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

[Libreoffice-bugs] [Bug 151164] [Bug 151139] Frequency function calculation error - Incorrect date format recognition - EDITING

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151164

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 151139] Frequency function calculation error - Incorrect date format recognition - EDITING

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151139

--- Comment #3 from Eike Rathke  ---
*** Bug 151164 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 151164] [Bug 151139] Frequency function calculation error - Incorrect date format recognition - EDITING

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151164

Eike Rathke  changed:

   What|Removed |Added

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

--- Comment #3 from Eike Rathke  ---
And please do not create yet another bug if the other was told to be not a bug.
You might discuss the resolution there, but creating duplicates is unnecessary.

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

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

[Libreoffice-bugs] [Bug 151148] Finding KATAKANA which has voice consonant mark returns incorrect results.

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151148

--- Comment #7 from Kiyotaka Nishibori  ---
To Noel:
Thank you for your providing a patch. It works well for me.
I'm sorry, but I submitted your patch to libreoffice-7-4 branch  as backporting
without your permission. 
The branch is developing  for its minor release now. That regression is serious
for Japanese users and most of them want the immediate fix.

 If you don't mind, See https://gerrit.libreoffice.org/c/core/+/140566

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

[Libreoffice-bugs] [Bug 151171] Basic editor: Bad number from hexa value

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151171

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 151171] Basic editor: Bad number from hexa value

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151171

Eike Rathke  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=62
   ||326,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||0476
 Resolution|--- |NOTABUG
 OS|Windows (All)   |All
   Keywords|regression  |
 Status|UNCONFIRMED |RESOLVED
   Hardware|x86-64 (AMD64)  |All
Version|7.4.1.2 release |6.4 all versions

--- Comment #1 from Eike Rathke  ---
Not a bug.

In  msgbox   the  is a 16-bit (short) integer constant where the
leading high bit is a sign bit and indicates a twos complement negative number.
This was fixed in 6.4.0 for bug 62326.

Force a 32-bit (long) constant with  &

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

[Libreoffice-bugs] [Bug 106727] EDITING: Select All is quite slow on a page containing a large table (72 rows and 20 columns)

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106727

--- Comment #9 from Roman Kuznetsov <79045_79...@mail.ru> ---
No repro  for me in

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 943177e0f8074753db25d9a56d15f8010a755ffc
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

Telesto, could you please retest it on your PC?

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

[Libreoffice-bugs] [Bug 136998] string interval incorrect after saving in new version

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136998

--- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> ---
Still repro in

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 943177e0f8074753db25d9a56d15f8010a755ffc
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108364

Dieter  changed:

   What|Removed |Added

 Depends on||126083


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=126083
[Bug 126083] Borders of merged table cells disappear if you enable page header
(also in PDF export) (steps in comment 7)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 126083] Borders of merged table cells disappear if you enable page header (also in PDF export) (steps in comment 7)

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126083

Dieter  changed:

   What|Removed |Added

 Blocks||108364

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

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

Actual result:
Border is visiblae but cell is shrinked (has height of two rows instead of six
rows).

Additional obeservation:
if you split cell into six cells same bug occurs with the merged cell before.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108364
[Bug 108364] [META] Table/Row/Column/Cell management function bugs and
enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 150752] LO Write 7.3.3.1 outline numbering in master document gives offset in chapter numbering in level 1

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150752

Dieter  changed:

   What|Removed |Added

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

--- Comment #6 from Dieter  ---
Jan, thank you for sample document. Now I can reproduce it with

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: bfb0dbee201a69c26293947c78356f320ff62a0b
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

but not with

Version: 7.2.7.2 (x64) / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL

Steps to reproduce
1. Open master document from attachment 182538

Actual result:
Document starts with "Introduction and Description" as Part II on page 5

Expected result:
"Introduction and Description" should be Part I


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107805
[Bug 107805] [META] Writer master document issues
https://bugs.documentfoundation.org/show_bug.cgi?id=115121
[Bug 115121] [META] Chapter numbering dialog bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 115121] [META] Chapter numbering dialog bugs and enhancements

2022-09-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115121

Dieter  changed:

   What|Removed |Added

 Depends on||150752


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=150752
[Bug 150752] LO Write 7.3.3.1 outline numbering in master document gives offset
in chapter numbering in level 1
-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   >