[Libreoffice-bugs] [Bug 151521] Applying paragraph styles with sub outline-level does not become folded content

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151521

--- 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/a3238a8e35c9c649069ef67ffa83e0d83f25936b

tdf#151521 Fix para applied style sub-level remains visible

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 151521] Applying paragraph styles with sub outline-level does not become folded content

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151521

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 151567] Sparkline graph copy+paste copies the graph itself not the graphing formula

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151567

--- Comment #4 from fre...@wp.pl ---
My tests show that it's not the range that is copied, but the graphics
snapshot.
Im my test case, if someone will copy/paste sparkline from D1 to D2, both will
look identical. Then if the Row1 data is changed, e.g. B1 from 3 to 1, the
sparkline in D1 will be updated to reflect the change and it's copy from D2
will not. So it seems like sparkline copy in D2 lost it's data connection at
all.

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

[Libreoffice-bugs] [Bug 151635] General Error exporting a chart into PNG, XML or JPG

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151635

Rainer Bielefeld Retired  changed:

   What|Removed |Added

   Keywords||regression
 Ever confirmed|0   |1
  Component|LibreOffice |Writer
Version|7.4.2.3 release |7.3.3.2 release
 Status|UNCONFIRMED |NEW

--- Comment #3 from Rainer Bielefeld Retired  
---
Additional Info:

a) Not a problem with DRAW, CALC
b) No obvious DUP found with query


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

[Libreoffice-bugs] [Bug 151635] General Error exporting a chart into PNG, XML or JPG

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151635

--- Comment #2 from Rainer Bielefeld Retired  
---
Created attachment 183154
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183154=edit
Sample Document

NOT yet reproducible with sample document and Server Installation of Version:
6.0.7.3 (x64) Build-ID dc89aa7a9eabfd848af146d5086077aeed2ae4a5; 
CPU-Threads: 12; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE);
Calc: CL, Special devUserProfile

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

[Libreoffice-bugs] [Bug 139185] "creatine" is detected as a Romanian word

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139185

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 113298] RTL: Automatic language detection based on keyboard layout

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113298

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #8 from Mike Kaganski  ---
See also: bug 139185 (and its See Also list) about language guessing problems
of libexttextcat; see bug 139185 comment 4.

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

[Libreoffice-bugs] [Bug 151635] General Error exporting a chart into PNG, XML or JPG

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151635

Rainer Bielefeld Retired  changed:

   What|Removed |Added

Summary|General Error exporting a   |General Error exporting a
   |chart into PNG  |chart into PNG, XML or JPG
 CC||LibreOffice@bielefeldundbus
   ||s.de

--- Comment #1 from Rainer Bielefeld Retired  
---
REPRODUCIBLE with Server Installation of Version: 7.5.0.0.alpha0+  Build ID:
2a7fcaf582df3ada57ca519b50e29011973a1b6f
CPU-Threads: 12; BS: Windows 10.0 Build 19044; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: Calc: threaded |  Elementary Theme  |  Special devUserProfile  (based on
my normal one)

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

[Libreoffice-bugs] [Bug 125965] [META] Sifr icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125965
Bug 125965 depends on bug 151647, which changed state.

Bug 151647 Summary: Sifr: Missing Table/Cell Border Icons
https://bugs.documentfoundation.org/show_bug.cgi?id=151647

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 125965] [META] Sifr icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125965
Bug 125965 depends on bug 151631, which changed state.

Bug 151631 Summary: Sifr: Missing Icons in 3D Settings Toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=151631

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 125965] [META] Sifr icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125965
Bug 125965 depends on bug 151071, which changed state.

Bug 151071 Summary: Revise Sifr to Follow Upstream (Adwaita)
https://bugs.documentfoundation.org/show_bug.cgi?id=151071

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 125965] [META] Sifr icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125965
Bug 125965 depends on bug 151502, which changed state.

Bug 151502 Summary: Sifr: No Wrap Image in Image Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=151502

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

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

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151365] Consider letting +/- change zoom level in Read-Only mode

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151365

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 151336] Wrong cursor placement when moving past LTR to RTL paragraph

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151336

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 145741] Calc Sidebar Function List Window does not permit size adjustment

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145741

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 151564] Crash for nebulous reason possibly involving scrolling when low available memory

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151564

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

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

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 151564] Crash for nebulous reason possibly involving scrolling when low available memory

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151564

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 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

--- 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 61195] FILEOPEN: Add support for importing and exporting Open XML Paper Specification files (OXPS)

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61195

--- Comment #13 from QA Administrators  ---
Dear Bastián Díaz,

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 44812] Sort ignores links from local url buttons to cells in the sorted range

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=44812

--- Comment #10 from QA Administrators  ---
Dear andréb,

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 42400] Query designer: numeric literal in condition on (VAR)CHAR column destructively transformed into string

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42400

--- Comment #6 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 40258] PRINTING With printing a selection: if the last paragraph has a bullet/numbering, all selected paragraphs get that bullet/numbering in the print

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=40258

--- Comment #22 from QA Administrators  ---
Dear Terrence Enger,

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 39921] Russian dictionary needs a proper numbers handling

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=39921

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

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 137589] Repeat: Merge Cells (Shift-Ctrl-Y) doesn't do same as Merge

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137589

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

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 137591] Don't ignore outlinelevelN RTF attribute when pasting from clipboard

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137591

--- Comment #3 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 137545] EDITING: Undo doesn't work with shape alignment

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137545

--- Comment #2 from QA Administrators  ---
Dear Xisco Faulí,

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 136232] After entering date inside drop down calendar in main form with kf5 VCL engine data has to be saved manually to enter subform

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136232

--- Comment #13 from QA Administrators  ---
Dear michael,

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 137017] FILESAVE XLSX Pie chart data labels custom positioning is not exported

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137017

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 136670] EDITING: removing rows/columns via keyboard ctrl + minus works only once

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136670

--- Comment #2 from QA Administrators  ---
Dear Oliver Brinzing,

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 135453] TABLE PROPERTIES DIALOG: Wrong Table Column size in dialog after changing table width (it changes to correct entries after pressing OK and reopening)

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135453

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

[Libreoffice-bugs] [Bug 134781] Harmonize entries structure for index of tables and figures

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134781

--- Comment #17 from QA Administrators  ---
Dear ajlittoz,

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 134614] FILESAVE: RTF: Indent in TOC is lost after RT in MSO 2010

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134614

--- Comment #4 from QA Administrators  ---
Dear Xisco Faulí,

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 133794] Memory used related to external data (CSV) not released after close of document

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133794

--- Comment #2 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 119329] Variable in equation in .docx vanishes if we open the file in Writer (Win10 only?)

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119329

--- Comment #32 from QA Administrators  ---
Dear Marco A.G.Pinto,

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 126477] FILEOPEN DOCX Embedded OLE document does not show charts

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126477

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 112773] UI: EDITING Pivot Table Layout closed upon closing warning message

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112773

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

[Libreoffice-bugs] [Bug 107750] Previews of drawing & presentation styles not rendered in Styles and Formatting deck in Impress/Draw

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107750

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

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 151567] Sparkline graph copy+paste copies the graph itself not the graphing formula

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151567

m.a.riosv  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #3 from m.a.riosv  ---
The spark line range it's copied without take care if the range reference is
relative.

Still happens with 
Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 5a1f41a0d3aab15c113651f2edc9d4137ae99063
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo

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

[Libreoffice-bugs] [Bug 151648] New: Formatted List Styles do not retain indent after copy/paste

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151648

Bug ID: 151648
   Summary: Formatted List Styles do not retain indent after
copy/paste
   Product: LibreOffice
   Version: 7.3.5.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rj.amdphr...@gmail.com

Description:
Copying/pasting and Undo/redo screw up Style information. Style information is
ignored, encoded incorrectly, and sometimes completely replaced with other
Style information.

Steps to Reproduce:
Create nested bulleted list like:
level 1
  level 2
level 3

Try to move part of that list around, to re-order the list items. Both
copy/paste and drag-and-drop cause it to format the list with the incorrect
indent. Re-applying the list Style from the Styles panel does not correct the
issue.

A bonus bug:
Copy the same list to another document, then Undo it, then Redo it with Ctrl-Y.
The Style information will now be screwed up. Every item that was a List 1, or
2 or 3, etc, will now be registered as a List style (the parent style of List
1, 2, etc), but list items that are not a top-level item will not have a
bullet, and will not be indented.

Actual Results:
Copy/paste problem: The list indentation is forgotten.

Undo/Redo problem: The list bullets are forgotten for non-top-level list items.
Indentation is also forgotten.

Expected Results:
I should be able to copy a portion of any list and past it somewhere else and
have it formatted the exact same way, and displayed properly.


Reproducible: Didn't try


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no < this is wrong. Your feedback button populated the wrong
info.

Version: 7.3.5.2 (x64) / LibreOffice Community
Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01
CPU threads: 16; OS: Windows 10.0 Build 22622; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 113123] [META] PDF import filter in Writer

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113123
Bug 113123 depends on bug 151546, which changed state.

Bug 151546 Summary: PDF poppler based filter import to Writer canvas reverses 
RTL script
https://bugs.documentfoundation.org/show_bug.cgi?id=151546

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104597
Bug 104597 depends on bug 151546, which changed state.

Bug 151546 Summary: PDF poppler based filter import to Writer canvas reverses 
RTL script
https://bugs.documentfoundation.org/show_bug.cgi?id=151546

   What|Removed |Added

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

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

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

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43808
Bug 43808 depends on bug 151546, which changed state.

Bug 151546 Summary: PDF poppler based filter import to Writer canvas reverses 
RTL script
https://bugs.documentfoundation.org/show_bug.cgi?id=151546

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151630] LibreOffice crashes when saving this file as .docx

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151630

Aron Budea  changed:

   What|Removed |Added

   Keywords||bibisected, bisected,
   ||regression
 CC||aron.bu...@gmail.com
Version|7.4.2.3 release |7.2.0.4 release

--- Comment #6 from Aron Budea  ---
(In reply to Julien Nabet from comment #4)
> It's related to: 35732c84b05e4f6e50349796636beb01f2a09907
> tdf#121509 DOCX export: fix corrupt shape anchoring in textbox

Yes, it's a regression from that fix.

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

[Libreoffice-bugs] [Bug 151647] Sifr: Missing Table Border Icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151647

Rizal Muttaqin  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |riz...@libreoffice.org
   |desktop.org |

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

[Libreoffice-bugs] [Bug 151647] Sifr: Missing Table Border Icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151647

Rizal Muttaqin  changed:

   What|Removed |Added

 Blocks||125965


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 125965] [META] Sifr icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125965

Rizal Muttaqin  changed:

   What|Removed |Added

 Depends on||151647


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151647
[Bug 151647] Sifr: Missing Table Border Icons
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151647] New: Sifr: Missing Table Border Icons

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151647

Bug ID: 151647
   Summary: Sifr: Missing Table Border Icons
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: riz...@libreoffice.org

Created attachment 183153
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183153=edit
Image capture showing no borders

Steps to reproduce:
1. Change icon theme to Sifr
2. Insert a table in Writer
3. Select the table, right click > Table Properties...
4. Select Borders tab

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 73911ed8d35294a9e15771d8aaa1e9121ef10309
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: id-ID (id_ID.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 148438] Get rid of unnecessary document recovery

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148438

--- Comment #3 from Rajasekaran Karunanithi  ---
I opened a  document in LO 7.4.1.2(x64)  and did some changes kept it open.
Later on killed the LO process and opened again LO, the auto recovery works on.

Can't reproduce in LO 7.4.1.2 (x64) Windows 10
build:3c58a8f3a960df8bc8fd77b461821e42c061c5f0

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

[Libreoffice-bugs] [Bug 131295] Firebird Embedded: Error while saving the table design

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=131295

--- Comment #11 from Damian Hofmann  ---
Retested with LO 7.3.5.2 and still reproducible as described in comment #8

Version: 7.3.5.2 (x64) / LibreOffice Community
Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-CH (de_CH); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151646] [SCREENSHOT] Several screenshots are not displaying good in information on the dialog

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151646

--- Comment #3 from Olivier Hallot  ---
Created attachment 183152
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183152=edit
Bad OptAppearancepage.png

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

[Libreoffice-bugs] [Bug 151646] [SCREENSHOT] Several screenshots are not displaying good in information on the dialog

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151646

--- Comment #2 from Olivier Hallot  ---
Created attachment 183151
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183151=edit
Bad OptPathPage.png deom "make screenshots"

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

[Libreoffice-bugs] [Bug 130744] [META] Screenshot Issues Meta Bug

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=130744

Olivier Hallot  changed:

   What|Removed |Added

 Depends on||151646


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151646
[Bug 151646] [SCREENSHOT] Several screenshots are not displaying good in
information on the dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151646] [SCREENSHOT] Several screenshots are not displaying good in information on the dialog

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151646

Olivier Hallot  changed:

   What|Removed |Added

 Blocks||130744


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 151646] [SCREENSHOT] Several screenshots are not displaying good in information on the dialog

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151646

--- Comment #1 from Olivier Hallot  ---
Created attachment 183150
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183150=edit
Good Apperance dialog screenshot

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

[Libreoffice-bugs] [Bug 151646] New: [SCREENSHOT] Several screenshots are not displaying good in information on the dialog

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151646

Bug ID: 151646
   Summary: [SCREENSHOT] Several screenshots are not displaying
good in information on the dialog
   Product: LibreOffice
   Version: 7.5.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: olivier.hal...@libreoffice.org

Created attachment 183149
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183149=edit
Screenshot of the good OptPathsPage.png

Command "make screenshots" produces many useless screenshots that do not
correspond to the real dialog shot.

Steps to reproduce

1) build LibreOffice ("make")
2) issue "make screenshot"
3) inspect resulting screenshots in workdir\screenshots\*

See for example

C:\cygwin\home\olivi\lode\dev\core\workdir\screenshots\cui\ui\optpathspage\OptPathsPage.png


C:\cygwin\home\olivi\lode\dev\core\workdir\screenshots\cui\ui\optappearancepage\OptAppearancePage.png

And many others. The attached images shows the expected results, shoot from the
live dialog.

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

[Libreoffice-bugs] [Bug 151638] Colour scale conditional format not persistent after move

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151638

--- Comment #3 from bugzi...@kgb.ovh ---
@Rafael Lima, sorry but your action is different than the steps I mentioned.
You moved your data out of the range.

With this bug I assume that the conditional format move is generally
functional. The problem is that it doesn’t behave the same way if the
conditional format is *colour scale* rather than formula.

So, @m.a.riosv, your subject is on other considerations; but this bug is only
about the colour scale not being treated like the the rest of the conditional
formatting.

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

[Libreoffice-bugs] [Bug 151638] Colour scale conditional format not persistent after move

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151638

bugzi...@kgb.ovh changed:

   What|Removed |Added

Summary|Conditional format not  |Colour scale conditional
   |persistent after move   |format not persistent after
   ||move

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

[Libreoffice-bugs] [Bug 106547] [META] OOXML SmartArt bug tracker

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106547
Bug 106547 depends on bug 151518, which changed state.

Bug 151518 Summary: FILEOPEN DOCX Text is wrongly placed in some SmartArt types
https://bugs.documentfoundation.org/show_bug.cgi?id=151518

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151215] Let me choose different fonts for different languages in the same group

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151215

--- Comment #17 from Eyal Rozenberg  ---
Speaking of language setting used keyboard layout... I was reminded of bug
113298.

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

[Libreoffice-bugs] [Bug 151215] Let me choose different fonts for different languages in the same group

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151215

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 113298] RTL: Automatic language detection based on keyboard layout

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113298

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

--- Comment #8 from arthur wilson  ---
Hi Roman. I tested our platform against 7.4.2.3 and everything is looking good.

we can close this ticket thanks!

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

[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96000
Bug 96000 depends on bug 141938, which changed state.

Bug 141938 Summary: Automatic spellcheck not triggered when navigating away 
with mouse click or arrow keys. Mistakes evaluated only after typing somewhere.
https://bugs.documentfoundation.org/show_bug.cgi?id=141938

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 136294] Red wrong spelled lining needs a trigger to get activated (spell checker)

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136294

László Németh  changed:

   What|Removed |Added

 CC||jimbo355...@gmail.com

--- Comment #18 from László Németh  ---
*** Bug 141938 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 141938] Automatic spellcheck not triggered when navigating away with mouse click or arrow keys. Mistakes evaluated only after typing somewhere.

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141938

László Németh  changed:

   What|Removed |Added

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

--- Comment #11 from László Németh  ---


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

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

[Libreoffice-bugs] [Bug 148257] Need ability to explicitly set the language/language-group of a piece of text

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148257

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 132000] Digit characters saved with different associated language/font when exporting DOCX

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132000

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151215] Let me choose different fonts for different languages in the same group

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151215

--- Comment #16 from Eyal Rozenberg  ---
(In reply to Mike Kaganski from comment #14)
> (In reply to Eyal Rozenberg from comment #12)
> > * Choosing what happens to neutral characters (i.e. which language's font
> > they adhere to)
> 
> Disagree with some specific part of this wording. Specifically: I totally
> agree that it would be useful to define a font used for "neutral" characters
> ... but I believe that it should not be "bind them to font of language X",
> but rather an own entry.

I don't have a strong opinion on this, I (think I) am ok with your approach.

> Additionally, in this case it looks like we have an
> xor case: *either* we map all neutral characters to some font, *or* honor
> the language of the text run to decide the font.Without the latter, we
> would not be able to resolve bug 148257; but if we allow the latter, a
> normal workflow on Windows (naturally marking every piece of text with
> current system input language) would already apply a language, so neutral
> characters would have to obey ...

That's a good point; but - let's suppose that we keep track of the language the
user is typing text in, and save that information in the document. That now
creates 3 basic options for treating neutrals:

1. Honor what the document says explicitly about the language of the neutrals
(using spans, or whatever's in the ODF spec).
2. Apply whatever standard heuristic we have for recognizing language runs in
text without language indicated specifically, and assign neutrals according to
the language they are determined to be in.
3. Render neutrals as some global override language.

and perhaps a combination of these three, e.g. use (1.) when possible and (3.)
as a fallback.

Also (2.) may not actually be that useful in some cases, e.g. "שלום,hello" - is
the comma English, or Hebrew? Or even: "Hello,bonjour" - comma in English or
French? And finally, "grand,brand" - is this English all the way, or maybe
French and English, or even French and Dutch, in which "brand" means fire? ...
and then there's no way to make a decent call on which language to choose for
the comma.


> > * Understanding which additional languages would be covered "for free" by a
> > font (e.g. if I want to occasionally use a French word with accents in my
> > English text - can I?)
> 
> I don't see how would that be reasonable part of e.g. Writer - we are not a
> dedicated tool for font management. If at all, I believe that Special
> Character dialog (which needs much of love anyway) could be used for
> something like that. However, if you have an appealing UI mockup that makes
> it natural in a place like the discussed configuration - why not.

I was trying to describe a maximal set of potential functionality. We could
decide this is too much.

> > * Controlling overlaps between fonts beyond the perfectly neutral characters
> > - what gets preferred?
> 
> This needs some elaboration.

Suppose you want font F1 for language L1 and font F2 for language L2 - but that
L1 and L2 have some non-neutral glyphs _in common_ and other glyphs which
aren't common. Like Arabic and Farsi I guess. Now, which font should we use for
a single glyph in the intersection of L1 and L2? ... if it's something we're
typing, I guess you could say "use the locale's language" - but what if you've
entered it as a special character? Or if you've pasted plain text? Or if you've
used a Unicode hex value to enter a character that's not in the language's set
of glyphs?

I realize I'm getting into corner cases here, but again, I've tried to capture
the maximal set of potential functionality, and we could decide to ignore this,
or force a default, or have another mechanism for handling it (like UI and an
UNO command for setting the language explicitly, a-la-bug 148257). If we had
that, the font selection dialog could do a little less and corrections could
use the language forcing mechanism. Or not.

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

[Libreoffice-bugs] [Bug 143774] Retain Macro Expanded Folders

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143774

flywire  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 145978] Macro Selector should remember last run module/macro

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145978

flywire  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151567] Sparkline graph copy+paste copies the graph itself not the graphing formula

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151567

--- Comment #2 from fre...@wp.pl ---
Created attachment 183148
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183148=edit
Calc sparkline Copy/Paste issue

Example file to illustrate the issue.
To reproduce the problem, Copy the sparkline in D1 cell, and paste it to D2.
Expected: sparkline will update to 2nd row of data (4,3,2)
Actual: sparkline is copied graphically (representing the original image from
the copied sparkline).

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

[Libreoffice-bugs] [Bug 151564] Crash for nebulous reason possibly involving scrolling when low available memory

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151564

--- Comment #3 from Steve Lawson  ---
I turned off OpenGL and stability has returned!  Also, I don't notice any
performance degradation.

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #9 from Gellért Gyuris  ---
Created attachment 183147
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183147=edit
Test output 3 (merged as individual documents) - output is wrong

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #8 from Gellért Gyuris  ---
Created attachment 183146
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183146=edit
Test output 2 (merged as individual documents) - output is wrong

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

Gellért Gyuris  changed:

   What|Removed |Added

 Attachment #183143|0   |1
is obsolete||

--- Comment #7 from Gellért Gyuris  ---
Created attachment 183145
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183145=edit
Test output 1 (merged as individual documents) - output is wrong

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

Gellért Gyuris  changed:

   What|Removed |Added

 Attachment #183141|0   |1
is obsolete||

--- Comment #6 from Gellért Gyuris  ---
Created attachment 183144
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183144=edit
Test output in one (merged as a single document) - output is OK

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

Gellért Gyuris  changed:

   What|Removed |Added

 Attachment #183142|0   |1
is obsolete||

--- Comment #5 from Gellért Gyuris  ---
Created attachment 183143
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183143=edit
Test output 1 (merged as individual documents) - output is wrong

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #4 from Gellért Gyuris  ---
Created attachment 183142
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183142=edit
Test ouput 1 (merged as individual documents) - ouput is wrong

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

[Libreoffice-bugs] [Bug 134071] LETTER WIZARD: Template created with wizard misses user information

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134071

--- Comment #15 from hinr...@prodelphi.de ---
My problem report is resolved because it is marked as a duplicate.
Okay.
But the problem is not resolved!
When will bug 66454 be resolved?

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #3 from Gellért Gyuris  ---
Created attachment 183141
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183141=edit
Test ouput in one (merged as a single document) - ouput is OK

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #2 from Gellért Gyuris  ---
Created attachment 183140
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183140=edit
Test database file

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

[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

--- Comment #1 from Gellért Gyuris  ---
Created attachment 183139
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183139=edit
Test file

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

[Libreoffice-bugs] [Bug 151645] New: Hidden sections are present in the output document when they merged with option as individual documents

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151645

Bug ID: 151645
   Summary: Hidden sections are present in the output document
when they merged with option as individual documents
   Product: LibreOffice
   Version: 7.3.6.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gellert.gyu...@gmail.com

Description:
If a document with hidden sections are merged as a single document the hidden
sections are stripped form the document. This is the expected result. But if
the document is merged as individual documents the hidden sections are present
in the document. This is a bug.


Steps to Reproduce:
1. Create a document with this content (automatically numbered list)
  1. first element
  2. second element
  3. third element
2. Insert 3 sections
  -- 1st section
  1. first element
  -- 2nd section
  2. second element
  -- 3rd section
  3. third element
3. Create a mail merge database with some fields: Id, name and some boolean
fields. For example:
  IDNameItem1   Item2   Istem3
  1 Johntruefalse   false
  2 Peter   false   truetrue
  3 Paulfalse   false   true
4. Add "hidden" condition to the all sections: Format > Sections > Hidden: 
  !HiddenDatabase.Sheet.Item1
  !HiddenDatabase.Sheet.Item2
  !HiddenDatabase.Sheet.Item3
5. Choose File > Print and respond with Yes in the message box. Create a merged
file as a single document.
6. Choose File > Print and respond with Yes in the message box. Create merged
files as individual documents.

Actual Results:
The file created with as a single document options: OK
The files created with option as individual documents: is fails. For example.
The output is:

Peter
2. second element
3. third element

Expected Results:
The expected result is:

Peter
1. second element
2. third element


Reproducible: Always


User Profile Reset: No



Additional Info:
Why is the ouput for single document good?
- Open the document.
- See Format > Sections: There are no hidden sections. Only the visible
sections are in the document structure. The sections are named in this way:
MailMergeSection[datetime][original section name]

Why are ouputs for individual documents wrong?
- Open a document.
- See Format > Sections: All sections are present in the document structure and
there are hidden sections!

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

--- Comment #7 from arthur wilson  ---
Sure, I'll update with my findings. Thanks

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

[Libreoffice-bugs] [Bug 151047] Stuck in "clone formatting" mode

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151047

Eyal Rozenberg  changed:

   What|Removed |Added

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

--- Comment #2 from Eyal Rozenberg  ---
Can't reproduce this right now, so closing as WFM.

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

[Libreoffice-bugs] [Bug 114912] [META] Clone formatting (aka Format Paintbrush) bugs and enhancements

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114912
Bug 114912 depends on bug 151047, which changed state.

Bug 151047 Summary: Stuck in "clone formatting" mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151047

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 138367] Direct PDF export crashes LO Writer when the program window isn't in fullscreen

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138367

--- Comment #8 from i...@jenweb.dev ---
Mac OSx 12.4 with LibraOffice 7.3.2.2

Export as PDF crashes every time - I can select the folder to save in, but when
I hit save, goes into the document recovery interface. I tried turning off all
the toolbars etc, and still same problem.

However, for me the Export Direct to PDF does not crash. 

Not sure if this is the same bug, but it's related.

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

[Libreoffice-bugs] [Bug 142608] Background color of Notebookbar tabbed tabs does not match the background of the bar itself (kf5)

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142608

Rafael Lima  changed:

   What|Removed |Added

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

--- Comment #9 from Rafael Lima  ---
Created attachment 183138
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183138=edit
Screenshot of the patched UI

Actually it's not the Tab that has the wrong color, but the tab pane was using
the wrong color (for some reason I could not figure out).

Both the Tab and the Tab contents need to use DialogColor. See the attached
image of the UI with the patch.

Here's the patch:
https://gerrit.libreoffice.org/c/core/+/141411

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

[Libreoffice-bugs] [Bug 151644] Full system stop for a minute and then libre office exel crash with the need to recover files as they become corrupt

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151644

Julien Nabet  changed:

   What|Removed |Added

Version|3.3.0 release   |7.4.1.2 release
   Hardware|Other   |x86-64 (AMD64)
 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 151644] Full system stop for a minute and then libre office exel crash with the need to recover files as they become corrupt

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151644

igor2001wilczyn...@gmail.com changed:

   What|Removed |Added

   Hardware|PowerPC |Other

--- Comment #3 from igor2001wilczyn...@gmail.com ---
Hi, using Windows 11 latest release as of 19/10/22 64bit. libre office 7.4.1.2.

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

[Libreoffice-bugs] [Bug 151276] Word complete doesn't work

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151276

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #10 from Dieter  ---
So last try:

gmhvd43, please take my steps from comment 3 and describe your results
=> NEEDINFO

If this doesn't make sence for you, I would close this bug and open a new one
for adding the relevant information about word completion and dictionary.

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

[Libreoffice-bugs] [Bug 151150] very long time to execute a macro when libreoffice calc file is started after start of the system (7mn) since V7

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151150

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

   What|Removed |Added

 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEEDINFO
 CC||79045_79...@mail.ru
 Ever confirmed|0   |1

--- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> ---
Please attach here file with your macroses

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

[Libreoffice-bugs] [Bug 149741] Confusing icon for adding column in libreoffice writer

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149741

--- Comment #28 from Dieter  ---
(In reply to Amin from comment #27)
> Unfortunately the page is not accessible. It shows "Server not found"

For me the link works.

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

[Libreoffice-bugs] [Bug 151644] Full system stop for a minute and then libre office exel crash with the need to recover files as they become corrupt

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151644

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #2 from Julien Nabet  ---
What LO version do you use, I suppose it's not 3.3.0.
Also, do you use x86 or x86-64 (since I suppose it's not PowerPC)

Last stable LO version is 7.3.6 and there's brand new 7.4.2

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

[Libreoffice-bugs] [Bug 151206] Auto filtering search entry / text input widget should use a timer-based search activation algorithm to improve performance

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151206

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

   What|Removed |Added

   Keywords||needsDevEval
 CC||79045_79...@mail.ru,
   ||caol...@redhat.com,
   ||noelgran...@gmail.com
 Whiteboard| QA:needsComment|

--- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> ---
I confirm the problem with Autofilter in

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

And we need some dev's opinion here

Caolan, Noel what do you think about this suggestion?

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

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

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151406] CALC: Changing cell background via macro is very slow

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151406

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

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151216] LibreOffice set cell formatting up to 40x slower in v7.3 and v7.4

2022-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151216

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

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #6 from Roman Kuznetsov <79045_79...@mail.ru> ---
Arthur could you please retest it yourself in latest 7.4.2 version?

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

  1   2   3   4   >