[Libreoffice-bugs] [Bug 152033] Memory leakage when using Writer with Skia activated

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152033

Buovjaga  changed:

   What|Removed |Added

Summary|Memory leakage when using   |Memory leakage when using
   |Writer  |Writer with Skia activated
   Severity|normal  |major
 Status|NEEDINFO|NEW

--- Comment #13 from Buovjaga  ---
Thanks for testing. I'll set this to NEW while assuming nagyhadnagy's issue is
also related to Skia as it is not seen in Safe Mode.

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

[Libreoffice-bugs] [Bug 152033] Memory leakage when using Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152033

--- Comment #12 from James Sheehan  ---
1. Turning off SKIA on my Windows 11 machine does "fix" the problem.
2. I notice that on my Linux Mint machine LibreOffice does not have a checkbox
for SKIA. I could not duplicate this problem on my Linux machine.
3. Previously, I had a similar problem for which the "fix" was to uncheck the
anti-aliasing checkbox. So I have been running my Windows 11 machine with the
anti-aliasing checkbox unchecked.

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

[Libreoffice-bugs] [Bug 154533] New: Libreoffice wont start / crash if you have multiple GPUs (Intel+Nvidia) and have dGPU disabled

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154533

Bug ID: 154533
   Summary: Libreoffice wont start / crash if you have multiple
GPUs (Intel+Nvidia) and have dGPU disabled
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: make...@gmail.com

Just wanted to open an odt file today, and noticed Libreoffice doesnt open
anymore. It worked some weeks ago still. I restarted PC, doesnt fix. I updated
to LibreOffice_7.5.2_Win_x86-64, doesnt fix (could be it auto updated to 7.5.2
and that broke it). I uninstalled and reinstalled LibreOffice_7.5.2_Win_x86-64,
doesnt fix. I deleted my profile under %APPDATA%\Libreoffice, doesnt fix. I
started it in safe mode via command line " start soffice.exe --safe-mode " and
did a revert back to factory settings, doesnt fix. Safe mode starts, but the
moment it starts in normal mode again, it crashes after bootload GUI.

Found out, it seems to be related to dual GPU sytemes, I have Intel UHD 630 +
Nvidia GTX1050 on my laptop, and have disabled the Nvidia card in control
panel. This worked before with no problem.

I selected libreoffice writer under Windows 11 settings to just open with Intel
GPU, doesnt fix.

Disabling OpenCL under libreoffice settings fixes the issue.

Windows 11 22h2 22621.1485
Intel drivers 31.0.101.2115
Nvidia drivers 31.0.15.3141

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

[Libreoffice-bugs] [Bug 154508] Cannot paste twice screenshot.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154508

M. Mahadevan  changed:

   What|Removed |Added

Summary|I did not paste twice   |Cannot paste twice
   |screenshot  |screenshot.

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

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=141586

--- Comment #30 from Aron Budea  ---
(In reply to Mibu from comment #29)
> No change in the last version of Libreoffice Fresh 7.5.2.2. Is there any
> chance that this bug will be solved?
You're probably mistaking this for bug 140147.

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

[Libreoffice-bugs] [Bug 151077] Multiple extensions require repeat installation and activation, with error messages on first installation (macOS appstore version)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151077

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 146981] CRASH LibreOffice freezes when resizing on a second monitor

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146981

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 154249] page spaces no longer toggle to run on

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154249

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 154516] Multiple annoying "Nonexistent file" error windows pop up in LibreOffice when editing a XLS document with a wrong link to another document.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154516

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 154516] Multiple annoying "Nonexistent file" error windows pop up in LibreOffice when editing a XLS document with a wrong link to another document.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154516

--- 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 154468] soffice crashes under unclear conditions

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154468

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 107703] Improve insert behaviour of images

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107703

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 154468] soffice crashes under unclear conditions

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154468

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

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

[Libreoffice-bugs] [Bug 107703] Improve insert behaviour of images

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107703

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

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

[Libreoffice-bugs] [Bug 151227] LibreOffice Impress text box sizes changed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151227

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

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

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

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

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 95324] Chart sidebar doesn’t function with .docx charts

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=95324

--- Comment #12 from QA Administrators  ---
Dear Luke,

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 140927] Bookmarks vanish when file closed/reopened in Writer (around comments)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=140927

--- Comment #5 from QA Administrators  ---
Dear Dave Lovelace,

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 55954] EDITING: CJK text has wrong style applied when copied from Writer to Calc

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=55954

--- Comment #15 from QA Administrators  ---
Dear bugquestcontri,

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 141346] Horizontal alignment doesn't work on custom (massive) page dimensions

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=141346

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

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 141273] Writer: line numbering in specific ODT writes that page number in footer although footer option was not set

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=141273

--- Comment #6 from QA Administrators  ---
Dear frithjof,

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 138184] FILEOPEN XLSX Bar chart axis labels appear vertically broken

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=138184

--- Comment #5 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 136996] Gallery -> Shapes -> Equal-3d is assigned Divide-3d icon

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136996

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

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 136597] ODF Export: Bookmark order broken when bookmarks start on same position

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136597

--- Comment #3 from QA Administrators  ---
Dear Samuel Mehrbrodt (allotropia),

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 135163] Anchor to paragraph moves to different page

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=135163

--- Comment #9 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 134454] Font not rendering properly when color is changed on mark glyph.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=134454

--- Comment #8 from QA Administrators  ---
Dear a.kalugin,

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 126095] NB toolbars visible which should be hidden

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=126095

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

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 113829] FILEOPEN: DOC: Incorrect position of table - on top instead of 5 cm vertical relative to page

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=113829

--- Comment #6 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 124379] Calc does not sort category formatted columns by multiple Sort Criteria

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=124379

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

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 107364] Currently assigned slide layout not highlighted in Slide Layout group button

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107364

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 106919] CALC: moving cell A1 data changes reference of Range Names in chart which doesn't reference cell A1

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=106919

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

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 100848] i18n: Separate strings that contain terms "page" or "slide" for Draw and Impress

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=100848

--- Comment #12 from QA Administrators  ---
Dear Modestas Rimkus,

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 105186] The same slide is searched twice when searching backwards

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=105186

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 103708] in Impress slides pane selecting a slide doesn't show it on every second click, instead runs different actions on it, occasionally even deleting it

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103708

--- Comment #14 from QA Administrators  ---
Dear Simon Sievers,

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 102372] Background image of a inserted slide from file is not saved

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=102372

--- Comment #6 from QA Administrators  ---
Dear Francisco,

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 154532] New: Input help texts are no longer displayed in Calc

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154532

Bug ID: 154532
   Summary: Input help texts are no longer displayed in Calc
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: cedriclach...@free.fr

Description:
Hello,

I am a French user of LibreOffice. The following message has been translated
into English by the deepl translator. I apologize in advance if the names of
the menus do not correspond to those of the English version of LibreOffice.

For some time now, one of my ODS files that uses input helpers has been
displaying empty frames in their place when you select a cell where the help
should be displayed.

I just tested on a new file, by selecting a cell at random, I go to the Data >
Validity menu, I activate the Input help tab (checkbox), I enter a title and a
message, and after validating, I get an empty yellow frame on this cell. The
problem does not seem to come from my original file created under a previous
version of LibreOffice.

This problem has been occurring since I upgraded LibreOffice to the then
version 7.5, before going back to the then latest version of the 7.4 branch
where the functionality did not work again.

Steps to Reproduce:
1.Select a cell in the worksheet
2.Go to menu Data > Validity
3.Activate the input help and write it (title + text or text only)

Actual Results:
Once the input help has been written and saved, by clicking on the cell an
empty yellow frame appears

Expected Results:
The input help is normally displayed with its title and below its help text


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL threaded

The problem persists in safe-mode

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

[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154461

خالد حسني  changed:

   What|Removed |Added

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

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


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

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

[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154461

--- Comment #8 from خالد حسني  ---
(In reply to Robert Großkopf from comment #7)
> Could confirm the buggy behavior for LO 7.4.6.2 on OpenSUSE 15.4 64bit rpm
> Linux.
> 
> Works well on LO 7.5.1.2.
> 
> If it is fixed for LO 7.5, why isn't it backported to LO 7.4?

The changes to fix this issue are too big to be backported.

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

[Libreoffice-bugs] [Bug 154531] EDITING: Paragraph style applied only to last paragraph in selection

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154531

--- Comment #1 from Tyler  ---
Just tested on 7.5.2.2 and the behaviour is, umm, different:

Now the style of all selected paragraphs is changed (as expected), but the
cursor jumps to the previous Heading 1...10 paragraph (if there is one in the
doc) -- whatever heading level is closest to the selected range.



Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

--- Comment #4 from Jeff Fortin Tam  ---
Created attachment 186384
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186384=edit
Screenshot of stack traces in sysprof

I don't know if that helps, but if you look at it with sysprof, it seems (from
my untrained eye) that there is a lot of expensive stuff going on with libsclo
and libsvllo...

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

Re: [libreoffice-marketing] Re: [libreoffice-design] Re: Moving to LibreOffice 8?

[Kelvene Requiroso]

I'm sorry I am not aware of the dynamics within the team. I like the 
exchange of ideas, sans insults and negative comments toward the person. 
And I agree our opinions are subjective, though we must try to be as 
objective as possible.


From a marketing perspective, other than the product's features, we also 
consider the context of the users or prospective end-users -- the 
market. Italo's suggestion of using the number 8 for the version naming, 
I think, is a good idea. Usually, the market only responds to the 
campaign once the product is on the roll, though a version rename 
without a major or significant addition or change would be a hollow one. 
So, it calls for a more balanced approach where the developers and 
marketing team collaborate. Thanks, Stephane, for the list of the major 
changes to do for the next version.


Thanks!

Kelvene

On 2023-03-30 03:55, Stéphane Guillou wrote:

/(I see that I replied to only one list, so just wanted to include 
design and marketing. Sorry for the double-up.)/


Thank you all for sharing your opinion.

Please keep in mind that "a really big jump" or "a major innovation" 
will always be very subjective and depend on personal areas of interest 
or specialties, and I suspect that we will have dozens of different 
opinions (and no agreement) if we ask what constitutes a feature that 
is significant enough to warrant a major version number.


Concretely, here is the shortlist of things that, in my _subjective_ 
opinion, are important in the upcoming version (somewhat similar to 
László's):
- availability on all major desktop platforms, including through 
official app stores

- advertise availability for ARM processors on Windows
- build baseline bump
- zoom gesture support
- cementing of updated visual identity and improved theming following 
the OS's
- improvements in accessibility of documents, including accessibility 
checked in sidebar and tagged PDF export by default

- two new languages
- multi-page floating tables
- _maybe_ Skia by default on macOS
- _maybe_ new Windows installer

Waiting for significantly "bigger" (again, very subjective) changes in 
LibreOffice is a bit unrealistic, knowing the project grows and has 
grown very organically.


In the end, I have no strong opinion about it. I just hope everyone can 
remain respectful and understand that sometimes, decisions have to be 
made, and I believe the marketing team, after some discussion with the 
rest of the TDF team, the Design team and the ESC, are a good fit to 
take such decisions, instead of heated conversations filled with 
subjective opinions on what feature is or isn't important.


The recent interaction makes me think a year/month versioning scheme is 
beneficial in that discussing version bumps will not be needed anymore. 
It's definitely not worth getting insulted, and I am sorry Italo had to 
be at the receiving end of that. And as Jorge said: let's not get 
bogged down into something that is in the end quite trivial.


I do however want to say I appreciate and take note of input from 
people like Regina (associating major releases with ODF releases, the 
default standard we are proud of), Kelvene (cultural aspect of the 
number), David (deciding early on to allow work on more disruptive 
projects) and Nigel ("The universal office suite", highlighting our 
strength in language and platform support).


Cheers!

On 29/3/23 21:36, Jaron Kuppers wrote:

I agree with Italo that changing to version 8 makes sense and that it 
is a marketing decision. Office suite updates that become new version 
numbers rarely include much in the way of ground breaking innovation 
and waiting for some integration of some new 'ground breaking' feature 
does not make sense. Nor does waiting for ODF1.4 which is not a change 
in some way unique to LibreOffice. A new version can also be framed 
around the plan for that new version. What huge changes are we going 
to make during version 8? It does not have to be limited to what 
changes warranted a number change. I think universal accessibility 
warrants a number change and makes for great marketing.


Italo, the way people talk to you is not okay... know that you have 
the respect of many/most community members who trust in your marketing 
expertise. Many are quick to speak on a topic they have no formal 
training in.


My 2 cents...

Cheers,
Jaron

On Wed, Mar 29, 2023 at 5:14 AM Pedro Rosmaninho 
 wrote:


I would just like to counter what Eyal Rosenberg says. Version number
should be a marketing decision.
But I agree with his points that marketing must consider that major
innovations or missing features should be included with a major number
change otherwise said number change will fall flat.
The number 8 is a great opportunity so it shouldn't be wasted without
having something impactful when it is launched.

Regina Henschel  escreveu no dia terça,
28/03/2023
à(s) 15:40:


Hi Italo,

the change from 6.x to 7.0 happens together with the change from

ODF 1.2

[Libreoffice-commits] core.git: helpcontent2

[Olivier Hallot (via logerrit)]

 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 32a11b50b2fc0b7a190a2197368958fa4e82b3e3
Author: Olivier Hallot 
AuthorDate: Fri Mar 31 22:03:43 2023 -0300
Commit: Gerrit Code Review 
CommitDate: Sat Apr 1 03:03:43 2023 +0200

Update git submodules

* Update helpcontent2 from branch 'master'
  to 717e7ee5206afad534d358182d88c3244ac6635e
  - Update filter conversion help page

Change-Id: Ieac78fad758e1b66932566d8928bbef53593b28a
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149898
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/helpcontent2 b/helpcontent2
index e3b6c3b4f9c2..717e7ee5206a 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit e3b6c3b4f9c2a5834251afe1ced59be64321e23e
+Subproject commit 717e7ee5206afad534d358182d88c3244ac6635e

[Libreoffice-commits] help.git: helpers/convertfilters.py source/text

[Olivier Hallot (via logerrit)]

 helpers/convertfilters.py   |   12 +-
 source/text/shared/guide/convertfilters.xhp |   32 ++--
 2 files changed, 22 insertions(+), 22 deletions(-)

New commits:
commit 717e7ee5206afad534d358182d88c3244ac6635e
Author: Olivier Hallot 
AuthorDate: Fri Mar 31 20:44:40 2023 -0300
Commit: Olivier Hallot 
CommitDate: Sat Apr 1 03:03:43 2023 +0200

Update filter conversion help page

Change-Id: Ieac78fad758e1b66932566d8928bbef53593b28a
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/149898
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/helpers/convertfilters.py b/helpers/convertfilters.py
index 5a01af19a9..863cbb23e2 100755
--- a/helpers/convertfilters.py
+++ b/helpers/convertfilters.py
@@ -60,13 +60,13 @@ output = '''
 -->
 
 
-File Conversion Filters Tables
+File Conversion Filters Tables
 /text/shared/guide/convertfilters.xhp
 
 
 
 
-
+
 filters;document conversion
 document conversion;filters
 convert-to;filters
@@ -76,7 +76,7 @@ output = '''
 
 File Conversion Filter 
Names
 
-
+
 
 Tables with filter names for command line document 
conversion.
 
@@ -84,9 +84,9 @@ output = '''
 
 Usage
 Filter names are used 
when importing and exporting files in alien formats and converting files 
formats through the command 
line.
-soffice --convert-to 
OutputFileExtension[:OutputFilterName[:OutputFilterParams[,param]]] [--outdir 
output_dir]
+soffice 
--convert-to 
OutputFileExtension[:OutputFilterName[:OutputFilterParams[,param]]] [--outdir 
output_dir]
 
-soffice 
--infilter=InputFilterName[:InputFilterParams[,param]]
+soffice 
--infilter=InputFilterName[:InputFilterParams[,param]]
 --infilter="Text (encoded):UTF8,LF,Liberation 
Mono,en-US".
 '''
 
@@ -130,7 +130,7 @@ for module in modules:
 
 output += f'\
 \n\
-\n\
+\n\
 command line document conversion; filters for 
{module[:-4].upper()}\n\
 \n\
 Filters for {module[:-4].upper()}\n\
diff --git a/source/text/shared/guide/convertfilters.xhp 
b/source/text/shared/guide/convertfilters.xhp
index 0af860ac20..72cd563cc5 100644
--- a/source/text/shared/guide/convertfilters.xhp
+++ b/source/text/shared/guide/convertfilters.xhp
@@ -10,13 +10,13 @@
 -->
 
 
-File Conversion Filters Tables
+File Conversion Filters Tables
 /text/shared/guide/convertfilters.xhp
 
 
 
 
-
+
 filters;document conversion
 document conversion;filters
 convert-to;filters
@@ -26,7 +26,7 @@
 
 File Conversion Filter 
Names
 
-
+
 
 Tables with filter names for command line document 
conversion.
 
@@ -34,9 +34,9 @@
 
 Usage
 Filter names are used 
when importing and exporting files in alien formats and converting files 
formats through the command 
line.
-soffice --convert-to 
OutputFileExtension[:OutputFilterName[:OutputFilterParams[,param]]] [--outdir 
output_dir]
+soffice 
--convert-to 
OutputFileExtension[:OutputFilterName[:OutputFilterParams[,param]]] [--outdir 
output_dir]
 
-soffice 
--infilter=InputFilterName[:InputFilterParams[,param]]
+soffice 
--infilter=InputFilterName[:InputFilterParams[,param]]
 --infilter="Text (encoded):UTF8,LF,Liberation 
Mono,en-US".
 
 
@@ -47,7 +47,7 @@
 
 
 
-
+
 command line document conversion; filters for 
WRITER
 
 Filters for WRITER
@@ -434,7 +434,7 @@
 
 
 
-Word 2010-365 Document
+Word 2010–365 Document
 
 
 Office Open XML 
Text
@@ -445,7 +445,7 @@
 
 
 
-Word 2010-365 Template
+Word 2010–365 Template
 
 
 Office Open 
XML Text Template
@@ -589,7 +589,7 @@
 
 
 
-
+
 command line document conversion; filters for 
CALC
 
 Filters for CALC
@@ -1065,7 +1065,7 @@
 
 
 
-
+
 command line document conversion; filters for 
IMPRESS
 
 Filters for IMPRESS
@@ -1343,7 +1343,7 @@
 
 
 
-
+
 command line document conversion; filters for 
DRAW
 
 Filters for DRAW
@@ -1577,7 +1577,7 @@
 
 
 
-
+
 command line document conversion; filters for 
MATH
 
 Filters for MATH
@@ -1657,7 +1657,7 @@
 
 
 
-
+
 command line document conversion; filters for 
BASE
 
 Filters for BASE
@@ -1693,7 +1693,7 @@
 
 
 
-
+
 command line document conversion; filters for 
GRAPHICFILTER
 
 Filters for GRAPHICFILTER
@@ -1762,7 +1762,7 @@
 
 
 
-
+
 command line document conversion; filters for 
PDFIMPORT
 
 Filters for PDFIMPORT
@@ -1864,7 +1864,7 @@
 
 
 
-
+
 command line document conversion; filters for 

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

Jeff Fortin Tam  changed:

   What|Removed |Added

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

--- Comment #3 from Jeff Fortin Tam  ---
It doesn't look like a strict duplicate (of bug #129228) to me either, and
"It's hard!" is not a resolution status in my view.

This being on 7.5, newer than 7.4, tells me it's also a different problem from
what was investigated and fixed in
https://llunak.blogspot.com/2022/07/making-unsorted-lookups-in-calc-fast.html

---

For comparison now, I installed Gnumeric, and it was able to open this same
file in less than 11 seconds, with zero lag (whether scrolling or changing
pages) while editing the file after opening it. *Gnumeric*, ladies and
gentlemen! On the same computer, same OS, etc. There is then no reason why
LibreOffice Calc can't achieve sub-20 seconds open times (let alone be able to
scroll fluidly once opened, but I guess that's a different matter).

I also asked two friends to time how long it takes to open that file in Excel
on Windows. Results: for one of them (with an older laptop) it took 13 seconds.
For the other, it took... 3 seconds. Ouch.

I believe my initial "performance objective" guess remains valid: LibreOffice
should aim to open this sample file "in 10-20 seconds or less."

LibreOffice taking over 3 minutes to open this file weakens the app's
credibility for enterprise scenarios, or even simply for community marketing
when you try to convince individuals to use it (and you are then embarrassed
when it falls apart on their data).

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

[Libreoffice-bugs] [Bug 154212] A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154212

--- Comment #3 from Jim Raykowski  ---
For me, holding the Ctrl key and clicking the "Move Chapter Up" button in the
Navigator tool box gives the expected result of moving the chapter back to the
position it was before the "Move Chapter Down". Holding the Ctrl key and
clicking the chapter move buttons in the tool box moves the chapter with out
moving sub-chapters. In this case the moved chapter doesn't have sub-chapters
so the expected result is seen.

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

[Libreoffice-bugs] [Bug 154531] New: EDITING: Paragraph style applied only to last paragraph in selection

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154531

Bug ID: 154531
   Summary: EDITING: Paragraph style applied only to last
paragraph in selection
   Product: LibreOffice
   Version: 7.4.6.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: t...@faehnle.net

Description:
If multiple paragraphs are selected and a different paragraph style is set,
only the last paragraph in the selection has its style changed. The paragraph
style of all other selected paragraphs remains unchanged.

Steps to Reproduce:
1. Create new document without template 
2. Hit  a few times to create some "Default Paragraph Style" paragraphs
3. Select everything (-A)
4. Choose a different paragraph style, e.g. "Title", from the "Set paragraph
style" toolbar dropdown

Actual Results:
The paragraph style of all but the last paragraph remains unchanged.
The paragraph style of the last paragraph is changed to "Title" (or whatever
you chose).

Expected Results:
The paragraph style of all paragraphs is changed to "Title" (or whatever you
chose).


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.6.2 / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-commits] core.git: Changes to 'feature/allo_contract34185'

[Thorsten Behrens (via logerrit)]

New branch 'feature/allo_contract34185' available with the following commits:
commit 54cb185f0db97d54c2440262745e84a44a58e4eb
Author: Thorsten Behrens 
Date:   Sat Apr 1 02:04:42 2023 +0200

Revert "tdf#153642 ucb: fix broken save with cached DAVOptions"

This reverts commit 03fe458efe59a810f885817abf2a574c0dda1dc2.

[Libreoffice-bugs] [Bug 139164] Always default to 'whole document' in print dialog

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=139164

--- Comment #34 from khagar...@gmail.com ---
Yes, that would be an issue for completely new files, but there are templates.

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

[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - include/LibreOfficeKit libreofficekit/source

[Paris Oplopoios (via logerrit)]

 include/LibreOfficeKit/LibreOfficeKitEnums.h |   10 +-
 libreofficekit/source/gtk/lokdocview.cxx |1 +
 2 files changed, 10 insertions(+), 1 deletion(-)

New commits:
commit 2480f572e05bc1c15696cb955187491778a6bded
Author: Paris Oplopoios 
AuthorDate: Wed Mar 29 13:47:06 2023 +0300
Commit: Paris Oplopoios 
CommitDate: Sat Apr 1 01:52:23 2023 +0200

Add LoKit callback for application color change

Change-Id: I9d0fe4ab878c9d3a4a6d842be5cd534b97bf77a8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149822
Tested-by: Jenkins CollaboraOffice 
Reviewed-by: Paris Oplopoios 

diff --git a/include/LibreOfficeKit/LibreOfficeKitEnums.h 
b/include/LibreOfficeKit/LibreOfficeKitEnums.h
index 6e02c92596f1..f57e00afa185 100644
--- a/include/LibreOfficeKit/LibreOfficeKitEnums.h
+++ b/include/LibreOfficeKit/LibreOfficeKitEnums.h
@@ -916,7 +916,13 @@ typedef enum
  * Payload is an opaque string that matches this set of states.
  * this will be emitted after creating a new view.
  */
-LOK_CALLBACK_VIEW_RENDER_STATE = 60
+LOK_CALLBACK_VIEW_RENDER_STATE = 60,
+
+/**
+ * Informs the LibreOfficeKit client that the background color surrounding
+ * the document has changed.
+*/
+   LOK_CALLBACK_APPLICATION_BACKGROUND_COLOR = 61
 }
 LibreOfficeKitCallbackType;
 
@@ -1067,6 +1073,8 @@ static inline const char* lokCallbackTypeToString(int 
nType)
 return "LOK_CALLBACK_EXPORT_FILE";
 case LOK_CALLBACK_VIEW_RENDER_STATE:
 return "LOK_CALLBACK_VIEW_RENDER_STATE";
+case LOK_CALLBACK_APPLICATION_BACKGROUND_COLOR:
+return "LOK_CALLBACK_APPLICATION_BACKGROUND_COLOR";
 }
 
 assert(!"Unknown LibreOfficeKitCallbackType type.");
diff --git a/libreofficekit/source/gtk/lokdocview.cxx 
b/libreofficekit/source/gtk/lokdocview.cxx
index 8fcbe9a404fc..76f94293956b 100644
--- a/libreofficekit/source/gtk/lokdocview.cxx
+++ b/libreofficekit/source/gtk/lokdocview.cxx
@@ -1487,6 +1487,7 @@ callback (gpointer pData)
 case LOK_CALLBACK_MEDIA_SHAPE:
 case LOK_CALLBACK_EXPORT_FILE:
 case LOK_CALLBACK_VIEW_RENDER_STATE:
+case LOK_CALLBACK_APPLICATION_BACKGROUND_COLOR:
 {
 // TODO: Implement me
 break;

[Libreoffice-bugs] [Bug 154516] Multiple annoying "Nonexistent file" error windows pop up in LibreOffice when editing a XLS document with a wrong link to another document.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154516

--- Comment #3 from Anton K.  ---
(In reply to m.a.riosv from comment #1)
> Please attach a sample file.

Sample file is attached

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

[Libreoffice-bugs] [Bug 154516] Multiple annoying "Nonexistent file" error windows pop up in LibreOffice when editing a XLS document with a wrong link to another document.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154516

--- Comment #2 from Anton K.  ---
Created attachment 186383
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186383=edit
example file

file for example

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

[Libreoffice-bugs] [Bug 154530] FILEOPEN PPTX: text in chart shows white instead of black

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154530

--- Comment #2 from Gerald Pfeifer  ---
Created attachment 186382
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186382=edit
Screenshot - PowerPoint

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

[Libreoffice-bugs] [Bug 154530] FILEOPEN PPTX: text in chart shows white instead of black

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154530

--- Comment #1 from Gerald Pfeifer  ---
Created attachment 186381
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186381=edit
Screenshot - LibreOffice

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

[Libreoffice-bugs] [Bug 154530] New: FILEOPEN PPTX: text in chart shows white instead of black

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154530

Bug ID: 154530
   Summary: FILEOPEN PPTX: text in chart shows white instead of
black
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ger...@pfeifer.com

Created attachment 186380
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186380=edit
Sample slide (PPTX)

Viewing the slide in Impress the labels and title of the chart render
in white instead of black (as in PowerPoint).

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1b463f697405e64a03378fb38a32172c4d3c25e6
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US

...and back to LibreOffice 6.4 at least.

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

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

--- Comment #2 from ady  ---
(In reply to m.a.riosv from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 129228 ***

This new bug 154525 is being reported against LO 7.5. Bug 129228 has been set
to FIXED for several years now.

Shouldn't this report be confirmed in some way or another before setting it as
duplicate of an old already-FIXED report?

Isn't it possible that the description of the behavior is similar, but the
problem is different (or came back again)?

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

Re: Bringing theme colors to ODF

[Regina Henschel]

Hi Tomaž, hi Armin,

because you Armin are working on multi-color gradients and you Tomaž are 
working on theme colors, I try to combine both for ODF, see attachment.


One main idea is, to introduce an "enhanced-color", which could be 
either a RGBHex color or a Scheme color.



I had a color type RGBZeroToOne but have removed it, because it has no 
benefit for other ODF consumers compared to RGBHex (a ODF TC member has 
concerns) and because it cannot be used for scrgbClr from OOXML since 
latter has a different gamma.


The other idea is, to allow a sequence of color-transformations where 
such "enhanced-color" exists in the same element. That is currently in 
the new elements , , 
 and .


I have used "" instead of 
"loext:fill-color-theme-reference" because with the concept of an 
"enhanced-color" the color could be defined as #rrggbb as well and still 
be combined with color transformations.


Tomaž Vajngerl schrieb am 25.03.2023 um 11:10:

Hi Regina,

On Thu, Mar 23, 2023 at 6:57 AM Regina Henschel > wrote:


Hi Tomaž, hi all,

I have started with creating a proposal to extend ODF with theme
colors.
The first draft is attached.

Tomaž, could you please look whether it fits to what you have intended.


Yes, looks fine on a quick glance but maybe renaming some things would 
make sense. Mainly the "color-table" would probably be better as 
"color-scheme" or something like that, as this is more in-line with 
OOXML terminology and we don't need to deviate from that just for the 
sake of it.


I have now used  for all 12 colors and 
 for a single one.


OTOH it probably makes sense to rename dk1, lt1, dk2, lt2, hlink, 
folHlink to the full names dark1, light1, ... , hyperlink, 
followed-hyperlink - which is inline with ODF style to not to abbreviate 
things. I planned to do that change but other things have priority 
currently.


I have used the full names now.

Also this covers only theme colors. Fonts and format still need to be 
defined and this is where it will get more complicated :)


The  element has currently only the child element 
 but the structure would allow to extend it later 
with a "scheme-font" and a "scheme-format" element.



You find on the first page of the attachment examples how I think a 
final (not loext) markup could look.


I have not yet feedback from the ODF TC about my idea to make the 
color-transformations "implementation-defined". That would mean, that 
for each color-transformation we need to describe the algorithm on the 
Wiki page. But it has the advantage, that implementing more 
color-transformations would need no change in ODF.


In case the ODF TC do not agree with "implementation-defined", which 
color-transformations do we need currently for ODF? More than lumMod, 
lumOff and alpha?


Kind regards,
Regina


ODF draft multi-color gradient plus theme v2.odt
Description: application/vnd.oasis.opendocument.text

[Libreoffice-bugs] [Bug 147938] Crash in: msvcp140.dll

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147938

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Attachment #178841|0   |1
is obsolete||

--- Comment #14 from Stéphane Guillou (stragu) 
 ---
Created attachment 186379
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186379=edit
minimal sample file for bisected bug

I made the original attachment smaller to test more easily.

Steps used to bisect:
1. Open file
2. Select whole table
3. Table > Convert > Table to Text > OK
4. Select all with Ctrl + A
5. Table > Convert > Text to Table > OK

Result: crash

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

[Libreoffice-bugs] [Bug 147938] Crash in: msvcp140.dll

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=147938

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Severity|normal  |critical
   Keywords|bibisectRequest |bibisected, bisected
 Blocks||103100
 CC||michael.st...@allotropia.de
   ||,
   ||stephane.guillou@libreoffic
   ||e.org
Crash report or|["msvcp140.dll"]|["msvcp140.dll","std::_Xlen
crash signature||gth_error(char const
   ||*)","libc.so.6"]
  Regression By||Michael Stahl
Version|6.4.7.2 release |6.2.0.3 release

--- Comment #13 from Stéphane Guillou (stragu) 
 ---
Quite a few things in here. I tested two crashes: comment 7 is resolved, and I
bibisected comment 4.

- comment 7 crash:

Reproduced in 7.3.7.2, with crash signature libc.so.6 :
https://crashreport.libreoffice.org/stats/crash_details/0008f17b-e2ee-4165-99ee-f29fcaa23920

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

However, not reproduced in 7.4.6, nor 7.5.2, nor a recent master build, so
comment 7 is resolved as "works for me".

-- comment 4 crash:

Reproduced in recent master:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1b463f697405e64a03378fb38a32172c4d3c25e6
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Also in 7.5.5.2, with crash signature libc.so.6 as well:
https://crashreport.libreoffice.org/stats/crash_details/ad4e8bce-e354-4365-b47f-99e3aa38d98b

Bibisected with linux-64-6.2 bibisect repo to first bad commit
ae82aa93d4536e9529688f412def4a23908f1d40 which points to core commit
94c1af65367dcbc7272455cf6d4940252a289b62 which is a cherrypick of:

commit  32902f66e7749b2d06d13f50416be5323a0c0ea9
author  Michael Stahl Fri Nov 30 17:54:41 2018 +0100
committer   Michael Stahl Tue Dec 18 17:55:30
2018 +0100
tree901ab6577d25102c0a855d2a63964dfef67b34c4
parent  b310378e874bc8fa7005352fcd85fa64eb075f54
sw_redlinehide: make layout based Show/Hide mode the default
remove ExperimentalMode checks
https://gerrit.libreoffice.org/c/core/+/64351

Michael, can you please have a look?


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103100

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||147938


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 154529] Proper text alignment is not possible in a flow chart table as the curser is not starting from the same point for each coloum.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154529

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m.a.riosv  ---


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

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

[Libreoffice-bugs] [Bug 154465] Proper text alignment is not possible in a flow chart table as the cursor is not starting from the same point for each column.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154465

--- Comment #1 from m.a.riosv  ---
*** Bug 154529 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 129228] FILEOPEN XLSX: file won't open then very slow (2 speedups in this bug)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=129228

m.a.riosv  changed:

   What|Removed |Added

 CC||nekoh...@gmail.com

--- Comment #22 from m.a.riosv  ---
*** Bug 154525 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 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---


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

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

[Libreoffice-bugs] [Bug 154516] Multiple annoying "Nonexistent file" error windows pop up in LibreOffice when editing a XLS document with a wrong link to another document.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154516

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please attach a sample file.

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

[Libreoffice-bugs] [Bug 154522] Drag the outer circle in the circle diagram at Libre office impress-text is going outside of the circle

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154522

--- Comment #1 from Anjali t a  ---
Yes i found this exactly same bug on my libre office impress. Once after i have
dragged a venn-colorful diagram on to the file and typed few texts in it,the
texts are going outside of the outer circle and the text are not moving it
still appears in the same place.
So this bug needs to be rectified in the Libre office impress.

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

[Libreoffice-bugs] [Bug 154529] Proper text alignment is not possible in a flow chart table as the curser is not starting from the same point for each coloum.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154529

--- Comment #1 from Sangeetha  ---
I tried this Bug.It looks same for me.The first coloumn flowchart curser is
starting from the left side corner but I Tried second and third the curser is
starting from the middle.
Text Alignment is not properly working in all the coloumns.

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

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

[Mike Kaganski (via logerrit)]

 writerperfect/source/writer/WordPerfectImportFilter.cxx |   17 +---
 1 file changed, 6 insertions(+), 11 deletions(-)

New commits:
commit d408e940630d131ab886a1d4619671fa0299c03e
Author: Mike Kaganski 
AuthorDate: Fri Mar 31 22:05:24 2023 +0200
Commit: Mike Kaganski 
CommitDate: Fri Mar 31 23:06:59 2023 +0200

Simplify a bit

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

diff --git a/writerperfect/source/writer/WordPerfectImportFilter.cxx 
b/writerperfect/source/writer/WordPerfectImportFilter.cxx
index 46e3241ee5eb..518c5556bb13 100644
--- a/writerperfect/source/writer/WordPerfectImportFilter.cxx
+++ b/writerperfect/source/writer/WordPerfectImportFilter.cxx
@@ -167,18 +167,15 @@ WordPerfectImportFilter::setTargetDocument(const 
Reference& 
Descriptor)
 {
-libwpd::WPDConfidence confidence = libwpd::WPD_CONFIDENCE_NONE;
-OUString sTypeName;
 sal_Int32 nLength = Descriptor.getLength();
 sal_Int32 location = nLength;
-const css::beans::PropertyValue* pValue = Descriptor.getConstArray();
 Reference xInputStream;
 for (sal_Int32 i = 0; i < nLength; i++)
 {
-if (pValue[i].Name == "TypeName")
+if (Descriptor[i].Name == "TypeName")
 location = i;
-else if (pValue[i].Name == "InputStream")
-pValue[i].Value >>= xInputStream;
+else if (Descriptor[i].Name == "InputStream")
+Descriptor[i].Value >>= xInputStream;
 }
 
 if (!xInputStream.is())
@@ -186,13 +183,10 @@ 
WordPerfectImportFilter::detect(css::uno::Sequence& D
 
 WPXSvInputStream input(xInputStream);
 
-confidence = libwpd::WPDocument::isFileFormatSupported();
-
+OUString sTypeName;
+libwpd::WPDConfidence confidence = 
libwpd::WPDocument::isFileFormatSupported();
 if (confidence == libwpd::WPD_CONFIDENCE_EXCELLENT
 || confidence == libwpd::WPD_CONFIDENCE_SUPPORTED_ENCRYPTION)
-sTypeName = "writer_WordPerfect_Document";
-
-if (!sTypeName.isEmpty())
 {
 if (location == nLength)
 {
@@ -200,6 +194,7 @@ 
WordPerfectImportFilter::detect(css::uno::Sequence& D
 Descriptor.getArray()[location].Name = "TypeName";
 }
 
+sTypeName = "writer_WordPerfect_Document";
 Descriptor.getArray()[location].Value <<= sTypeName;
 }
 

[Libreoffice-bugs] [Bug 152257] Crash: Selecting an option in dropdown content control leads to unexpected exit with code 139

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=152257

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Version|7.5.0.0 alpha0+ |7.4.3.2 release
 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
   Keywords||bibisected, bisected
 Status|UNCONFIRMED |NEW
Crash report or||["SwDropDownContentControlB
crash signature||utton::LaunchPopup()"]
   Severity|normal  |critical

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Could get the same segfault on SwDropDownContentControlButton::LaunchPopup() in
non-debug 7.5.2.2 without waiting at all, by pressing twice alt+down in the
first dropdown content control.

Crash report:
https://crashreport.libreoffice.org/stats/crash_details/e3df02e2-60b3-483d-84f5-e3448ee021ed

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

With gtk VCL, using Alt + Down the first time allows entering the dropdown.
Further Down presses to navigate the options don't crash it, but another Alt +
Down does.

With kf5 or gen VCLs, no crash.

Bibisected with linux-64-7.4 repo to first bad commit
5fd5f3e7b44717eab066389806f70ff7a008d7a6 which points to core commit:

commit  e2095410b00b8a374ba35ea5fab584a79a46cfe2
author  Miklos Vajna Mon Oct 10 10:07:10 2022 +0200
committer   Xisco Fauli Tue Oct 11
16:33:43 2022 +0200
tdf#151261 DOCX import: fix dropdown SDT when the item display text is missing
[...]
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/141151

Not calling it a regression as this is the commit that made an actual dropdown
available for gtk.
Miklos, can you please have a look?

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

[Libreoffice-bugs] [Bug 154529] New: Proper text alignment is not possible in a flow chart table as the curser is not starting from the same point for each coloum.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154529

Bug ID: 154529
   Summary: Proper text alignment is not possible in a flow chart
table as the curser is not starting from the same
point for each coloum.
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: anjalita...@gmail.com

Description:
once after we have dragged a header and pool flowchart into the libre office
impress,and types a text in each coloum of the table,we r not able to get a
proper alignment of text as the curser is not getting started in the same
position.

Steps to Reproduce:
1.Go to libre office impress and open the file
2.Select a flow chart header and pool from the gallery
3.Drag the flow chart into libre office impress and type a text in each coloum
4.While typing a text in each coloum the curser is starting from different
position and the text alignment is not proper.

Actual Results:
In the first coloum of the flowchart,the curser is starting from the left side
corner,whereas in the second and third coloum the curser is getting started
from the centre of the coloum,hence there is no proper alignment of text.

Expected Results:
The curser should start at the same point in each coloum of the flow chart
table and the text alignment should be proper.


Reproducible: Always


User Profile Reset: No

Additional Info:
The curser should start at the same poin in each coloum of the table .

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 37128] Writer saves text alignment of RTL paragraph not according to the ODF specification

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=37128

Eyal Rozenberg  changed:

   What|Removed |Added

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

--- Comment #19 from Eyal Rozenberg  ---
(In reply to Eyal Rozenberg from comment #17)
> Isn't the bug here really just the fact that LO fails to distinguish between
> Start/End and Left/Right?

So, yes, but no. There is now a separate bug about properly supporting Start
and End in addition to Left and Right: bug 131192.

But this really needs to be fixed! Our output files for RTL languagues are
broken now already for 14 years :-O

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

[Libreoffice-bugs] [Bug 56412] RTL UI: Resize-movement of embedded objects is opposite to the change direction

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=56412

--- Comment #17 from Eyal Rozenberg  ---
Also happens when you single-click the object, not edit it, but resize by
dragging the right edge.

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

[Libreoffice-bugs] [Bug 56412] RTL UI: Resize-movement of embedded objects is opposite to the change direction

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=56412

Eyal Rozenberg  changed:

   What|Removed |Added

Summary|RTL UI: Movement of |RTL UI: Resize-movement of
   |embedded objects is |embedded objects is
   |opposite to the change  |opposite to the change
   |direction   |direction

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

[Libreoffice-bugs] [Bug 107810] [META] OLE/Embedded object bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=107810

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||56412


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=56412
[Bug 56412] RTL UI: Movement of embedded objects is opposite to the change
direction
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 56412] RTL UI: Movement of embedded objects is opposite to the change direction

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=56412

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||107810
Version|3.3.0 release   |Inherited From OOo


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 56412] RTL UI: Movement of embedded objects is opposite to the change direction

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=56412

Eyal Rozenberg  changed:

   What|Removed |Added

   See Also|https://issues.apache.org/o |https://bz.apache.org/ooo/s
   |oo/show_bug.cgi?id=104515   |how_bug.cgi?id=104515

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

[Libreoffice-bugs] [Bug 154528] FILEOPEN PPTX: some bullet points show smaller than in PowerPoint

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154528

Gerald Pfeifer  changed:

   What|Removed |Added

Summary|FILEOPEN PPTX: bullet   |FILEOPEN PPTX: some bullet
   |points  |points show smaller than in
   ||PowerPoint

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

[Libreoffice-bugs] [Bug 154527] When I try to write in notepad it goes beyond the given minimum size

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154527

--- Comment #1 from Sangeetha  ---
I tried this Bug .It looks same for me.when i try to write in the notepad it
goes beyond the notepad size

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

[Libreoffice-bugs] [Bug 154528] FILEOPEN PPTX: bullet points

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154528

--- Comment #1 from Gerald Pfeifer  ---
Created attachment 186378
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186378=edit
Visual comparison Office 365 (left) vs LibreOffice (right)

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

[Libreoffice-bugs] [Bug 154528] New: FILEOPEN PPTX: bullet points

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154528

Bug ID: 154528
   Summary: FILEOPEN PPTX: bullet points
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ger...@pfeifer.com

Created attachment 186377
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186377=edit
Sample slide (PPTX)

Slides 1 and 15 of attachment #127409 from bug #102261 render
differently in LibreOffice than PowerPoint: some bullet points 
are shown in different sizes (= smaller).

The sample document attached here is a reduced reproducer.


Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4ca4282517d02592966576fc642048b3d5ae5532
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US

...and all the way back to 6.4 at least.

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

[Libreoffice-bugs] [Bug 154490] Libreoffice spreadsheets keeps unfreezing rows and columns yet the menu says they are still frozen.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154490

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153946] FreezePanes unlocks by self.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153946

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |4490|
 CC||stephane.guillou@libreoffic
   ||e.org
 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Hi there
- Which option exactly do you use in the View menu?
- Can you please paste here the information copied from Help > About
LibreOffice?

Thank you!

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

[Libreoffice-bugs] [Bug 154527] New: When I try to write in notepad it goes beyond the given minimum size

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154527

Bug ID: 154527
   Summary: When I try to write in notepad it goes beyond the
given minimum size
   Product: LibreOffice
   Version: 7.5.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sisbva...@gmail.com

Description:
When I try to write in notepad it goes beyond the given minimum size.
steps to reproduce:
1. First you need to go to libreofficedraw
2.Then press the gallery on the right side,then choose shapes.
3.Select the 3rd bluenote and enter text in it
Note that it extends belows the given segment











































Actual Results:
When i entering text the lower part continues to stretch

Expected Results:
When i entering text the text should be displayed in the inner part without the
bottom part disappearing


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

Jeff Fortin Tam  changed:

   What|Removed |Added

   Keywords||filter:ooxml, filter:xlsx,
   ||perf

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

[Libreoffice-bugs] [Bug 154526] New: [EDITING] Character styles should be available in toolbars, similar to paragraph styles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154526

Bug ID: 154526
   Summary: [EDITING] Character styles should be available in
toolbars, similar to paragraph styles
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nora@nora.codes

Description:
I work with a publisher that extensively uses Microsoft Word. I am able to
perfectly replicate their workflow in LibreOffice Writer with the single
exception of the use of character styles, which are pretty annoying to use
because I have to have the character styles open in the right-hand pane.

Character styles should be available in a dropdown (drop-down) menu which can
be added to the toolbar, similarly to paragraph styles.

Steps to Reproduce:
1. Open Tools -> Customize.
2. Select Toolbars tab.
3. Search for "character styles".


Actual Results:
There is no available toolbar component for character styles.

Expected Results:
There should be a toolbar component similar to the paragraph styles dropdown
component for character styles.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.2
Calc: threaded

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

[Libreoffice-bugs] [Bug 154525] New: [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154525

Bug ID: 154525
   Summary: [sample] Calc is extremely slow (3+ minutes) to open
Lenovo's Accessories "Options Compatibility Matrix"
spreadsheet
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nekoh...@gmail.com

Description:
Trying to open the attached spreadsheet causes Calc to eat 100% of one of my
CPU cores (it would be faster if it was multi-threaded) for 3 minutes and 20
seconds, on a ThinkPad X220T with Intel® Core™ i5-2520M × 4 CPU + Mesa Intel®
HD Graphics 3000 (SNB GT2) running on Fedora 37's GNOME Xorg (X11) session.

Steps to Reproduce:
1. Grab this spreadsheet from
https://download.lenovo.com/pccbbs/options_iso/ocm_mar_2023.xlsx (found through
clicking the Thinkpad link on http://www.lenovo.com/accessoriesguide )
2. Open that file.
3. Put a kettle on your CPU to prepare some tea while you wait 

Actual Results:
3 mins and 20 seconds to open the spreadsheet and for the UI to become reactive
again. During that time, one of my 4 CPU cores is 100% used, and temperatures
climb to 75°C (it would probably be higher and closer to 90-100°C if I didn't
have really good thermal paste).

Even closing the app/document (read-only, with no unsaved changes) takes a
solid 5-10 seconds, instead of being instantaneous.

Expected Results:
Open in 10-20 seconds or less.

Ideally use all my CPU cores to process the spreadsheet.


Reproducible: Always


User Profile Reset: No

Additional Info:
 It would probably be very beneficial for TDF to download, archive and
integrate that spreadsheet as part of LibreOffice's standard
performance/regression document testsuite... it certainly is a great bench
test.

---

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3
Flatpak
Calc: threaded

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

[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=129661

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||154524


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154524
[Bug 154524] Spelling error squiggly line misplaced for rotated RTL text
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154524] Spelling error squiggly line misplaced for rotated RTL text

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154524

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||129661, 96000


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=96000
[Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129661
[Bug 129661] [META] Right-To-Left (RTL) user interface issues
-- 
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

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=96000

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||154524


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154524
[Bug 154524] Spelling error squiggly line misplaced for rotated RTL text
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154524] Spelling error squiggly line misplaced for rotated RTL text

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154524

Eyal Rozenberg  changed:

   What|Removed |Added

 Attachment #186376|Document with rotated text  |Document with rotated text
description|with which the bug  |with which the bug
   |manifests   |manifests (186376)

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

[Libreoffice-bugs] [Bug 154524] Spelling error squiggly line misplaced for rotated RTL text

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154524

Eyal Rozenberg  changed:

   What|Removed |Added

 Attachment #186375|Screenshot of Writer window |Screenshot of bug manifests
description|with bug manifesting|with attachment 186376

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

[Libreoffice-bugs] [Bug 154524] Spelling error squiggly line misplaced for rotated RTL text

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154524

--- Comment #1 from Eyal Rozenberg  ---
Created attachment 186376
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186376=edit
Document with rotated text with which the bug manifests

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

[Libreoffice-bugs] [Bug 154524] New: Spelling error squiggly line misplaced for rotated RTL text

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154524

Bug ID: 154524
   Summary: Spelling error squiggly line misplaced for rotated RTL
text
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Created attachment 186375
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186375=edit
Screenshot of Writer window with bug manifesting

If you have the spelling check enabled, and enter some incorrectly spelled RTL
text which is also rotated at 90 degrees, some of the squiggly line indicating
the error will be placed far "before" the text - upwards of it. See attached
screenshot.

You may need to scroll a little upwards and downwards to see the squiggly line
at all, since initially when I open the file with the example I don't see it.

Experienced with:

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US

and:

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-IL (en_IL); UI: en-US


and also with a recent 7.6 nightly.

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

[Libreoffice-bugs] [Bug 154212] A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154212

--- Comment #2 from Jim Raykowski  ---
The bug has to do with where frame nodes are stored in the document model
(before regular document content). Patches for Bug 143569 made headings that
are in frames show in document order.

This bug can also be reproduced with a second level Heading appended to the end
of the document and then doing "Move Chapter Up".

Navigator outline move commands are handled here:

sw/source/uibase/utlui/content.cxx
void SwContentTree::ExecCommand(std::string_view rCmd, bool
bOutlineWithChildren)

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

Re: Extended color

[Regina Henschel]

Hi Armin,

Armin Le Grand schrieb am 31.03.2023 um 13:29:

Hi,

On 3/24/23 11:01, Regina Henschel wrote:
The ColorTransformType determines how the number in Value has to be 
interpreted.
Examples: Type="LumMod" Value="6000" means to modify the luminance of 
the color with 60% as specified in OOXML.


struct ColorStop
    double   StopOffset
    css::awt::ExtColor   StopColor


We should split it here from my POV.

(a) There is the model data in the XFillGradientItem and 
XFillFloatTransparenceItem expressed as XGradient


(b) There is FillGradientAttribute used in primitives


I'm only thinking about API and ODF. My proposals do not touch 
primitives and FillGradientAttribute.




Both use currently basegfx::ColorStops and thus ColorStop which just 
uses a basegfx::BColor as color definition. I agree that we should use 
css::awt::ExtColor in the model data (a), but not in (b).


Then we agree.

Nevertheless, we need to track the relationship to themes and color 
transformations. Those are needed in export to OOXML and ODF.




The issue is that primitives are designed to be self-contained, thus 
should contain a 'complete' data set to describe their content, also to 
be able to implement as simple as possible, and *local*, decomposition. 
If they would contain the ColorType 'Theme' always some kind of 'solver' 
would be necessary to be in reach to get the end result of the color to 
be used in the visualization.


Thus the primitives in (b) should already contain the result of that 
processing that converts from a theme color to the render color. This 
fits well together, so in the primitive creating step where (a) is 
processed the probability to have such a 'solver' is high (should be 
e.g. in the same ItemSet?). Just 'solve' it there and use the result in 
a single representation form in the to-be-created primitive.


It would be good, if Tomaž Vajngerl could give an overview over his 
plans, especially how _he_ things to integrate theme colors and 
multi-color gradients.


Kind regards,
Regina

[Libreoffice-bugs] [Bug 154523] Promote & Demote button icons do not respect RTL

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154523

Eyal Rozenberg  changed:

   What|Removed |Added

   See Also||https://bz.apache.org/ooo/s
   ||how_bug.cgi?id=88925

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

[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=129661

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||154523


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154523
[Bug 154523] Promote & Demote button icons do not respect RTL
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103239] [META] Toolbars bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103239

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||154523


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154523
[Bug 154523] Promote & Demote button icons do not respect RTL
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154523] Promote & Demote button icons do not respect RTL

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154523

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||129661, 48799, 103239


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=48799
[Bug 48799] [META] Impress Bullets and Numbering bugs (formatting and UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=103239
[Bug 103239] [META] Toolbars bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129661
[Bug 129661] [META] Right-To-Left (RTL) user interface issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 48799] [META] Impress Bullets and Numbering bugs (formatting and UI)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=48799

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||154523


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154523
[Bug 154523] Promote & Demote button icons do not respect RTL
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154229] Text files without extension treated as WordPerfect files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154229

--- Comment #10 from Mike Kaganski  ---
The false detection happens in WP42Heuristics::isWP42FileFormat

https://sourceforge.net/p/libwpd/code/ci/master/tree/src/lib/WP42Heuristics.cpp#l61

and it seems to do the reasonable job - just the data happens to be
suspiciously similar to the proper format. It is a UTF-8-encoded plain text
file, which has ASCII characters (0x20 to 0x7F), and exactly one pair of the
non-ASCII characters (the same “), which are encoded in UTF-8 as 0xE2 0x80.
This pair forms one "variable-length functional group" (starting from 0xE2, and
ending at the same 0xE2), and immediately after, one "single-character
functional group", consisting of 0x80. Such a unlikely coincidence: the
properties of 0xE2 in WordPerfect require the pair; and the properties of 0x80
make it a valid alone. If it were almost anything different; it the quotes were
different, like “...”; or if there was at least one other non-ASCII; or...

I don't know if the detection can be improved. But the constellation is funny
;)

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

[Libreoffice-bugs] [Bug 154523] Promote & Demote button icons do not respect RTL

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154523

--- Comment #1 from Eyal Rozenberg  ---
Created attachment 186374
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186374=edit
Impress window with promote/demote on main toolbar and RTL bulleted paragraph

Note the bright blue rightwards arrow button on the top toolbar. The paragraph
cannot go any further to the right, only due left. So, only the demote button
is enabled :-(

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