[Libreoffice-bugs] [Bug 155750] Error activating object General OLE error

[bugzilla-daemon]

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

--- Comment #3 from Kadet  ---
It is a pity that so far none of the developers have paid attention to this
error.
My five-year work is based on using the capabilities of OLE attachments and
five programs and databases have been written.
It will be a pity if this error persists in the future and the possibility of
using OLE attachments in Base forms will be impossible.

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

[Libreoffice-bugs] [Bug 107906] The arrows don't respect their path when resized

[bugzilla-daemon]

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

Diana Vides  changed:

   What|Removed |Added

 CC||dianavide...@gmail.com

--- Comment #8 from Diana Vides  ---
Unfortunately, It is still happening in Version: 7.5.3.2 (X86_64) / LibreOffice
Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (en_US); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 155798] Changes to scale don't update rulers immediately

[bugzilla-daemon]

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

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 155563] Practically no visual effect for selected, and non selected, {Don't save, cancel, save} Save document? window buttons

[bugzilla-daemon]

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

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 155798] Changes to scale don't update rulers immediately

[bugzilla-daemon]

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

--- 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 118945] PRINTING When print some signed document the paper version does not show any info about the signatures

[bugzilla-daemon]

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

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

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

[Libreoffice-bugs] [Bug 118945] PRINTING When print some signed document the paper version does not show any info about the signatures

[bugzilla-daemon]

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

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 141274] Error Saving Document When Picture Pasted from Spectacle

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Sarah Szabo,

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 147321] Applied text shadow disappears upon save and reload

[bugzilla-daemon]

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

--- Comment #2 from QA Administrators  ---
Dear milton.mendonca71,

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 152510] crash when I resize one libre office window and I have other window open

[bugzilla-daemon]

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

--- Comment #3 from QA Administrators  ---
Dear Paolo Fiorito,

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 144108] Calc application color changes inconsistent.

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Ruven Gottlieb,

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 91769] Move up and down buttons work for paragraphs without list too, but only available on toolbar Bullets and Numbering

[bugzilla-daemon]

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

--- Comment #11 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 71920] FORMATTING: Text is not shown behind frame set to 'Wrap Through' and with fill set to None (see comment 10 for implementation rqmt)

[bugzilla-daemon]

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

--- Comment #17 from QA Administrators  ---
Dear Harald Koester,

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 91204] Some Items of Properties Dialogue are not Current if Option “Edit document properties before saving” is Chosen

[bugzilla-daemon]

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

--- Comment #18 from QA Administrators  ---
Dear Harald Koester,

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 90656] Metadata in Word 6 imported with wrong encoding

[bugzilla-daemon]

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

--- Comment #12 from QA Administrators  ---
Dear Karl Ove Hufthammer,

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 128273] FORMATTING Calc changes a number format

[bugzilla-daemon]

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

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

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 124673] why toggle function DrawText, HyperlinkDialog and Horizontal Line

[bugzilla-daemon]

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

--- Comment #17 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 116804] [Impress, Slideshow, FILEOPEN]: Command Line Switch To Open In Windowed Mode Slideshow

[bugzilla-daemon]

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

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

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 116720] LibreOffice Calc does not read its own HTML attributes (save as)

[bugzilla-daemon]

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

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

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 103967] DOC import: Empty table cell has wrong font size

[bugzilla-daemon]

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

--- Comment #14 from QA Administrators  ---
Dear Justin L,

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 128966] Writer table: Center Vertically shows some rows as Align Top (click-in restores until next fileopen) (see comment 10)

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 120275] [META] Writer table alignment bugs and enhancements

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||155773


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155773
[Bug 155773] Table contents are not rendered centered on odt fileopen until
refresh
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155773] Table contents are not rendered centered on odt fileopen until refresh

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Severity|normal  |minor
 Blocks||120275
Version|7.5.4.2 release |Inherited From OOo
Summary|6, 9, # are not centered on |Table contents are not
   |odt file|rendered centered on odt
   ||fileopen until refresh
 CC||stephane.guillou@libreoffic
   ||e.org
   Priority|medium  |low
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||8966

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Confirmed also in OOo 3.3, so marking as inherited.

Clicking in the third column restores the alignment, which is similar to bug
128966. Alternatively, changing the zoom level restores it too.
Save and then reload: the vertical shift reappears.


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 125544] Table cell alignment is recalculated on opening documents

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Version|unspecified |5.1.0.3 release
   Keywords||bibisectRequest, regression

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
This is a regression starting in 5.1.0.1 (tested with linux-64-releases
bibisect repo)

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

[Libreoffice-bugs] [Bug 63136] table cell is set to align=bottom, but cell contents are at top

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Version|4.0.2.2 release |Inherited From OOo
 OS|Linux (All) |All
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
I can reproduce the original issue only by changing the alignment to top, then
trying to align back to the bottom of the cell: the content stays at the top.

Inherited from LO, and also in a recent master build:

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

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

[Libreoffice-bugs] [Bug 155804] Row-wise and/or column-wise merge in 2D area

[bugzilla-daemon]

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

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

But I don't want to copy-paste one row into the rest, each row has its own
contents.

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

[Libreoffice-bugs] [Bug 155825] Crash MCGR export special file odp -> pptx

[bugzilla-daemon]

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

--- Comment #2 from Regina Henschel  ---
Created attachment 187901
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187901=edit
axial color mixed with linear transparency

Axial plus linear is indeed a problem. The attached file has a shape with both
gradients with stops at offset 0 and 1 (so do not trigger the crash) and a
screenshot of the shape. Save the file to pptx and open the pptx-file. You see
the error immediately.

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

[Libreoffice-bugs] [Bug 155825] Crash MCGR export special file odp -> pptx

[bugzilla-daemon]

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

--- Comment #1 from Regina Henschel  ---
Created attachment 187900
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187900=edit
reduced example

The error is in synchronizeColorStops in gradienttools.cxx in lines 440 to 454.

In both cases not only aNewAlpha (or aNewColor respectively), has to get the
stop but aNewColor (or aNewAlpha respectively) too. The both aNew... need to
grow simultaneously.

The situation in the example is, that the offsets for the colors are 0 and 0.9,
and for the transparency 0 and 1. The generated aNewColor and aNewAlpha both
need the stops 0, 0.9 and 1.

[Looking at the code, I'm not sure whether the combination of axial and linear
is handled correctly. (In the following the Number is the offset and the
characters are the values.)
Imagine a axial color gradient with 0 A, 1 B together with a linear
transparency gradient 0 X, 1 Y. Then the resulting stops should be 0 BX, 0.5 A
middle_of_XY, 1 BY. But because you apply axial after synchronizing you get 0
BY, 0.5 AX, 1 BY.
But I'm not sure and its after midnight so would need to look at it tomorrow
again.]

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

[Libreoffice-bugs] [Bug 154044] Undoing the first applied cell formatting only works for column A

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153913] FILESAVE / FORMATTING: Failure to save / progressive loss of cell background colour of otherwise empty cells

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153644] Calc: Undo doesn't remove cell's borders

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
Version|7.4.5.1 release |7.4.0.0 beta1+
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||4044,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3913

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

[Libreoffice-bugs] [Bug 153913] FILESAVE / FORMATTING: Failure to save / progressive loss of cell background colour of otherwise empty cells

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

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

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|154066  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154066
[Bug 154066] Unable to undo attributes part of cell's area
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153644] Calc: Undo doesn't remove cell's borders

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||nfsmob...@mail.ru

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
*** Bug 154066 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 154066] Unable to undo attributes part of cell's area

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected
Version|7.4.3.2 release |7.4.0.0 beta1+
 Blocks|105948  |
 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED
 CC||stephane.guillou@libreoffic
   ||e.org
   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |3913|

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
With core commit 9e2d48b9e04f7ea895fb095699c32ed8a44eb129, the issue started
with the inability to apply formatting to the whole of a cell range that does
not contain data in its edges.
Behaviour as described in comment 2 was bibisected with linux-64-7.4 repo to
commit ecdde2cb463610623dc25454f67ba99bb8c86fca which points to core commit:

commit  970ff17f47731be788ec34c0c8ddf3fb2c24ceac
author  Luboš Luňák  Mon May 30 16:33:15 2022 +0200
committer   Luboš Luňák  Mon May 30 21:20:54
2022 +0200
fix setting cell borders for unallocated cells
First of all, it should not be clamped to allocated columns. Second,
06d3294502413a231e5c5265609862c7f67a2f2b incorrectly handled
unallocated columns by setting the attribute for all rows, instead
of handling the inner ones differently.
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/135131

So, first commit broke things, second commit was a partial fix.

Still same root cause as bug 154044, but marking as duplicate of bug 153644
instead as the bibisect and description match.

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


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||154072


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154072
[Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar
overflows
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||100156


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows

[bugzilla-daemon]

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

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
Created attachment 187899
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187899=edit
wayland debug log

In a wayland debug log collected with:

WAYLAND_DEBUG=1 libreofficedev7.6 >& lo-wayland-log.txt

I can see:

[3812106.409] wl_display@1.error(xdg_wm_base@24, 3, "Invalid popup parent
window")

This validation seems to have been added to mutter with:

https://mail.gnome.org/archives/commits-list/2020-August/msg10980.html

The commit message says it is a client error:

"Calling `get_popup` on an unmapped window is a client bug, thus post a
protocol error when this happens."

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

[Libreoffice-bugs] [Bug 140147] Position of cursor not saved correctly (see comment 46 for bibisect)

[bugzilla-daemon]

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

--- Comment #65 from V Stuart Foote  ---
*** Bug 155824 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 155824] documents never open up where I left off.

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #2 from V Stuart Foote  ---
Beleive bug 140147 is the closer dupe

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

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

[Libreoffice-bugs] [Bug 154072] crash / no effect when clicking some dropdown buttons when toolbar overflows

[bugzilla-daemon]

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

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
Created attachment 187898
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187898=edit
gdb backtrace with LO 7.6 alpha1+ debug, "no stack"

I could crash a debug build using the steps in comment 3, but couldn't collect
a trace.

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

In the console I see:

Gdk-Message: 23:37:44.155: Error 71 (Protocol error) dispatching to Wayland
display.

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

m.a.riosv  changed:

   What|Removed |Added

 CC||spjggvlksniwaor...@bbitq.co
   ||m

--- Comment #32 from m.a.riosv  ---
*** Bug 155824 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 155824] documents never open up where I left off.

[bugzilla-daemon]

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

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 141586 ***

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

[Libreoffice-bugs] [Bug 154168] FILESAVE: Export selection to .PNG without transparency fails

[bugzilla-daemon]

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

--- Comment #12 from Commit Notification 
 ---
Paris Oplopoios committed a patch related to this issue.
It has been pushed to "libreoffice-7-6":

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

tdf#154168 Export no transparency PNGs correctly

It will be available in 7.6.0.0.beta2.

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

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

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

[Libreoffice-bugs] [Bug 154168] FILESAVE: Export selection to .PNG without transparency fails

[bugzilla-daemon]

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:24.2.0   |target:24.2.0
   ||target:7.6.0.0.beta2

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

[Libreoffice-bugs] [Bug 155326] Calc with gtk3 VCL is unusable with large spreadsheets: huge lag, high CPU usage, etc.

[bugzilla-daemon]

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

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155455] Scroll continues when keyboard key is pressed for long and then released

[bugzilla-daemon]

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

Telesto  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 143540] EDITING: Keypad decimal character not changed to comma

[bugzilla-daemon]

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

--- Comment #23 from Stéphane Guillou (stragu) 
 ---
Thank you both.

(In reply to Mattia from comment #20)

> (In reply to Stéphane Guillou (stragu) from comment #19)
>   Key val, name:  65454 KP_Decimal

I've tested the same script and get the same key val when using "English
(Australia)" for Ubuntu's Regional Formats. However, if I change the Regional
Format to "français (France)", the same key sends the key val "65452
KP_Separator".


More questions:
- can you please check that you get the right character in other GTK apps, to
make sure that it is indeed a LibreOffice issue?
- if it is only in LibreOffice, is it only for Calc or also in e.g. Writer?

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

[Libreoffice-bugs] [Bug 155455] Scroll continues when keyboard key is pressed for long and then released

[bugzilla-daemon]

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

Telesto  changed:

   What|Removed |Added

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

--- Comment #5 from Telesto  ---
Setting to NEW, based on comment 3

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

[Libreoffice-bugs] [Bug 155825] New: Crash MCGR export special file odp -> pptx

[bugzilla-daemon]

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

Bug ID: 155825
   Summary: Crash MCGR export special file odp -> pptx
   Product: LibreOffice
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Created attachment 187897
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187897=edit
Callstack by Visual Studio

I could reproduce the crash mentioned in
https://gerrit.libreoffice.org/c/core/+/152673 for normal, not headless export.
The callstack from Visual Studio is attached.

The crash happen in oox/source/export/drawingml.cxx in
if (aColorStops.size() != aAlphaStops.size() || nullptr == pGradient)
{
// this is an error - synchronizeColorStops above *has* to create that
// state, see description there (!)
// also an error - see comment in header - is to give neither
pColorGradient
// nor pTransparenceGradient
assert(false && "oox::WriteGradientFill: non-synchronized gradients
(!)");
return;
}

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

[Libreoffice-bugs] [Bug 155824] New: documents never open up where I left off.

[bugzilla-daemon]

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

Bug ID: 155824
   Summary: documents never open up where I left off.
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: spjggvlksniwaor...@bbitq.com

Description:
this has been persistent across all versions of LibreOffice on all platforms.


Steps to Reproduce:
1. opening any document
2. page doesn't open in the same space I left it, usually like 4-8 pages it
resumes to randomly.
3. type cursor is also in a different location, usually a few sentences off.

Actual Results:
Documents do not resume where they are left off in writer. I urge you to
confirm this on your own documents.

Expected Results:
Documents never open where they are left off. I expect them to open correctly.
This is a bug, it should be urgently looked into and fixed.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Documents never open where they are left off, stop deleting this report and
acknowledge it.

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

[Libreoffice-bugs] [Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||155815


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155815
[Bug 155815] footnotes reordered with docx
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155815] footnotes reordered with docx

[bugzilla-daemon]

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||109195
 CC||nem...@numbertext.org

--- Comment #6 from Stéphane Guillou (stragu) 
 ---
(In reply to martyhiatt from comment #5)
> i just tried opening a docx file with badly my ordered footnotes in
> microsoft word online. the footnotes there appear in the correct order. is
> it then only a matter of rendering, and my files should likely be fine?

Hopefully that's the case, but hard to say without a test file.
Could you please prepare a sample document that displays the issue when
compared  between MS Office and LO 7.5.4.2, and attach that file to this
report?
It sounds like it could be a follow up to issues mentioned above.

Copying László Németh in, who has worked on that part of the software recently.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=109195
[Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155823] A specific list item does not continue numbering after save-and-reload since 7.4

[bugzilla-daemon]

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

Mike Kaganski  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

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

[Libreoffice-bugs] [Bug 155823] New: A specific list item does not continue numbering after save-and-reload since 7.4

[bugzilla-daemon]

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

Bug ID: 155823
   Summary: A specific list item does not continue numbering after
save-and-reload since 7.4
   Product: LibreOffice
   Version: 7.4.0.0 alpha0+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: bibisectNotNeeded, filter:odt, regression
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com

Created attachment 187896
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187896=edit
A single list having items with different list styles

Open the attached sample. With styles panel open on List Styles, check that the
first, second, and fourth list items have style "ListStyleOne", and the third
item has "ListStyleAnother". Note also, that the numbering of all four is
contiguous (1., 2., 3., 4.).

Save (as ODT or FODT) and reload. Since commit
8f48f91009caa86d896f247059874242ed18bf39 (version 7.4), the numbering is broken
in the last item, which is now numbered "1." instead of expected "4.".

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

[Libreoffice-bugs] [Bug 155822] Method findAll() of com.sun.star.util.XSearchable may return NULL though specified to return XIndexAccess container.

[bugzilla-daemon]

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

Mike Kaganski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Keywords||difficultyBeginner,
   ||easyHack, skillCpp
 Ever confirmed|0   |1

--- Comment #1 from Mike Kaganski  ---
https://opengrok.libreoffice.org/xref/core/sc/source/ui/unoobj/cellsuno.cxx?r=3e7ff2a9=189177=3757#3757

introduced in the initial import.

It looks reasonable to throw an error when the initial check (pDocShell &&
xDesc.is()) fails, and if it passes, it seems possible to create an empty
ScRangeList right away, and create the returned ScCellRangesObj with it
unconditionally before return.

The easyhack needs a unit test.

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

[Libreoffice-bugs] [Bug 155822] New: Method findAll() of com.sun.star.util.XSearchable may return NULL though specified to return XIndexAccess container.

[bugzilla-daemon]

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

Bug ID: 155822
   Summary: Method findAll() of com.sun.star.util.XSearchable may
return NULL though specified to return XIndexAccess
container.
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@psilosoph.de

Created attachment 187895
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187895=edit
The announced demo

XIndexAccess containers can well be empty. The .Count property then is 0.

The result of a .findAll() with XSearchable is one of the cases where a result
of type XIndexAccess is specified, but NO such result is returned if nothing
was found. Instead of setting .Count to 0, in this case the NULL object is
returned. 

It may factually be impossible to fix the bug because old running code would be
broken this way. However, the API documentation should give a related hint, and
list the cases where a NULL ob ject will be returned, while a XIndexAccess
object should be expected.

Thare is a demonstrating example attched.

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

[Libreoffice-bugs] [Bug 114531] Support JPEG-XR image format

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #7 from Julien Nabet  ---
(In reply to Tomaz Vajngerl from comment #3)
> Well we need Jpeg-XR for full support of images in OOXML documents.. even if
> it is just a "meh" format it is something MSO uses in some cases. So I
> wouldn't close this one...

Reading external/libjpeg-turbo/README, we use libjpeg-turbo-2.1.5.1.tar.gz for
jpeg import support (but it seems also for export too considering we use
functions like "jpeg_create_compress").

I don't know if libjpeg-turbo supports jpeg-xr if not, it means we must find a
lib (compatible with LO license) which supports the format, in C or C++, well
maintained, etc.

Considering the size of OOXML specs (see
https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML#Criticism),
I'm not sure it's a pb to not implement a standard which isn't even implemented
natively by Gimp and Photoshop (see
https://en.wikipedia.org/wiki/JPEG_XR#Software_support).

Then we can wonder if we're talking about read support only or read and write
support but quite quickly, if there's read-only support, people will complain
they can't modify the images of a doc.
Of course, we may convert the image in another format but 1) it adds even more
complexity 2) it'll bother some users
Finally I completely agree with
https://bugs.documentfoundation.org/show_bug.cgi?id=114533#c5 :
"Also removing support for a image format is much harder so adapting a new
image format should take a lot of consideration as it can have long lasting
effects"

Perhaps it could be interesting to ask ESC opinion?

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

[Libreoffice-bugs] [Bug 154756] Vertical text direction results in rotation, not vertical text direction

[bugzilla-daemon]

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

Eyal Rozenberg  changed:

   What|Removed |Added

   Keywords||needsUXEval

--- Comment #14 from Eyal Rozenberg  ---
(In reply to Heiko Tietze from comment #13)
> Don't know how UX can contribute to this discussion

You can help decide what combination of widgets should control direction and
orientation in the Page Style dialog. You could perhaps also help reviewing my
claim that what we have right now is confusing for some users.

> Btw, if there is such a serious issue I'd expect a duplicate ticket.

The likely reason this is not a "serious" issue is that it only affects non-CJK
glyphs, and few Westerners care about this direction to begin with. In fact,

> For example bug 114002.

... that _is_ a way this issue is "serious". You see, because we treat this
writing direction as a rotation - and probably some of the implementing code
also does that - we assume glyphs are supposed to be rotated. Which they are
not. Different languages have different conventions regarding the potential
orientations of their glyphs (what's possible and what's common/default). If we
had respected that, and not assumed we should "rotated everything sans certain
exceptions", bug 114002 would not have occurred.

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

[Libreoffice-bugs] [Bug 155818] Enhancement: Please consider supporting the JPEG-XR (.jxr) format

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

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

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


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

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

[Libreoffice-bugs] [Bug 114531] Support JPEG-XR image format

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||xordevore...@gmail.com

--- Comment #6 from Julien Nabet  ---
*** Bug 155818 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 155781] documents never open up where I left off.

[bugzilla-daemon]

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

--- Comment #2 from Julien Nabet  ---
*** Bug 155821 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 155821] documents never open up where I left off.

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---
No need to make dups, it won't be fixed faster.

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

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

[Libreoffice-bugs] [Bug 154255] Support embedded PDF viewing and zooming as vectorial instead of rasterized image

[bugzilla-daemon]

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

--- Comment #6 from V Stuart Foote  ---
(In reply to Ole Tange from comment #5)

> 
> But I would really love if I could re-arrange pages like I can with
> PDFarranger.

LibreOffice is *NOT* a PDF editor. And is only a viewer in the sense that we
parse content from the PDF--the pdfium based rasters (no Skia vector canvas
yet), or for the clunky conversion of content to ODF draw objects.

The original PDF is retained, but the rendering to LO document canvas is not
bulk PDF internals. Currently the pdfium based parser works one page at a time,
so you have to split the pages out external to LibreOffice, e.g. PDFtk and add
them in the sequence you need. Scriptable but bug 114234 is open to improve
multi-page PDF.

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

[Libreoffice-bugs] [Bug 155821] New: documents never open up where I left off.

[bugzilla-daemon]

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

Bug ID: 155821
   Summary: documents never open up where I left off.
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: spjggvlksniwaor...@bbitq.com

Description:
this has been persistent across all versions of LibreOffice on all platforms.

Steps to Reproduce:
1. opening any document
2. page doesn't open in the same space I left it, usually like 4-8 pages it
resumes to randomly.
3. type cursor is also in a different location, usually a few sentences off.

Actual Results:
Documents do not resume where they are left off in writer. I urge you to
confirm this on your own documents.

Expected Results:
Documents never open where they are left off.
This is a bug, it should be urgently looked into and fixed.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Documents never open where they are left off

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

[Libreoffice-bugs] [Bug 155455] Scroll continues when keyboard key is pressed for long and then released

[bugzilla-daemon]

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

Adam664  changed:

   What|Removed |Added

 CC||p...@pfortin.com

--- Comment #4 from Adam664  ---
*** Bug 155766 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 155766] Please sync arrow keys to selected cell

[bugzilla-daemon]

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

Adam664  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||adamsesku...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Adam664  ---
155455 has more has a better description and steps to replicate, so gonna mark
this as a duplicate

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

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

[Libreoffice-bugs] [Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to H for Unicode15

[bugzilla-daemon]

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

--- Comment #2 from V Stuart Foote  ---
(In reply to V Stuart Foote from comment #1)
> =-ref-=
> [1] https://extensions.libreoffice.org/en/extensions/show/1077

This from the extension's page (via Google Translate)

Description
The IPAmj font is one of the fonts developed and distributed by the IPA
Independent Administrative Institution Information-technology Promotion Agency.
This is a huge font set containing approximately 60,000 characters, including
variant characters, used for personal names in municipalities throughout Japan.

This extension can search IPAmj fonts by various items including variant
characters (IVS) and paste them into documents via the clipboard.

・The IPAmj Mincho font must be installed on the system.
- The document must be formatted with the IPAmj Mincho font.

The MJ character information list included in this extension is distributed by
the following organizations, and CC-BY-SA is applied.
IPA Information-technology Promotion Agency
　https://mojikiban.ipa.go.jp/1311.html
Character Information Technology Promotion Council
　https://moji.or.jp/mojikiban/mjlist/

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

[Libreoffice-bugs] [Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to H for Unicode15

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||kha...@libreoffice.org,
   ||vsfo...@libreoffice.org

--- Comment #1 from V Stuart Foote  ---
@Khaled, *, 

Not sure what is meant by support here. 

Assume that if LO receives the Unicode, and select a font with coverage, that
it renders to LO document canvas--and can save and print same.

So is this an IME question or inability to render? Does our Special Character
Dialog render chart of these codepoints?

Or is this more simply against the "IPAmj Font Charactor Finder" extension [1]? 

=-ref-=
[1] https://extensions.libreoffice.org/en/extensions/show/1077

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

[Libreoffice-bugs] [Bug 154255] Support embedded PDF viewing and zooming as vectorial instead of rasterized image

[bugzilla-daemon]

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

--- Comment #5 from Ole Tange  ---
(In reply to Heiko Tietze from comment #3)

> And I struggle a bit with the use case. Your Writer document is WYSIWYG, you
> shouldn't expect different zoom level for details.

Every lawyer has a use case, and probably many more people.

We need to import hundreds of pages of PDF files into a single file.

All that will be added is a page number for the total document, and some cross
reference links into each page, so you can easily go from an index to a given
page in the PDF.

The document becomes unwieldly large if each PDF-file is converted to PNG in a
resolution that is readable (i.e. > 200 DPI). Try that with 500 pages, which is
my latest task.

I would love if LibreOffice could be an alternative to PDFarranger
https://github.com/pdfarranger/pdfarranger
So I could merge PDF-files without loss of quality and add small details like a
total page number.

It is perfectly fine if I cannot "enter into" a PDF page, so from a user
perspective the pages could be treated similar to a write protected SVG image.

But I would really love if I could re-arrange pages like I can with
PDFarranger.

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

[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143781
Bug 143781 depends on bug 154757, which changed state.

Bug 154757 Summary: CPP unit tests: provide message converters to allow use of 
O(U)Strings as _MESSAGE argument
https://bugs.documentfoundation.org/show_bug.cgi?id=154757

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 154757] CPP unit tests: provide message converters to allow use of O(U)Strings as _MESSAGE argument

[bugzilla-daemon]

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

Mike Kaganski  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142692] Python script connecting to LO instance fails

[bugzilla-daemon]

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

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
(same result for gen VCL by the way)

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

[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues

[bugzilla-daemon]

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

DaeHyun Sung  changed:

   What|Removed |Added

 Blocks||155820


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155820
[Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs
Extension Block C to H for Unicode15
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155820] isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to H for Unicode15

[bugzilla-daemon]

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

DaeHyun Sung  changed:

   What|Removed |Added

 CC||shinji.en...@gmail.com,
   ||sungd...@gmail.com
 Depends on||83066


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83066
[Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language
issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155820] New: isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to H for Unicode15

[bugzilla-daemon]

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

Bug ID: 155820
   Summary: isCJKIVSCharacter needs to support CJK Unified
Ideographs Extension Block C to H for Unicode15
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sungd...@gmail.com

Description:
isCJKIVSCharacter needs to support CJK Unified Ideographs Extension Block C to
H for Unicode15

I'm curious about CJK Characters. (I'm Korean. But, I study & can speak both
Japanese and Mandarin Chinese a little bit.)

After I contribute to support Unicode 15's CJK Unified Ideographs Extension H
for GNOME characters, I checked CJK Unified Ideographs Extension Lists on
LibreOffice.
(GNOME characters commit link:
https://gitlab.gnome.org/GNOME/gnome-characters/-/commit/daef901e34d731d6d8fe8a1f966ea9f1f04e3a2f
)

However, It doesn't support CJK Unified Ideographs Extension Block C to H. Only
supports CJK Unified Ideographs and its Extension Block A, B.

In Unicode 15, the CJK Unified Ideographs Extension Block range is here
CJK Unified Ideographs: 4E00–9FFF
CJK Unified Ideographs Extension A: 3400–4DBF
CJK Unified Ideographs Extension B: 2–2A6DF
CJK Unified Ideographs Extension C: 2A700–2B73F
CJK Unified Ideographs Extension D: 2B740–2B81F
CJK Unified Ideographs Extension E: 2B820–2CEAF
CJK Unified Ideographs Extension F: 2CEB0–2EBEF
CJK Unified Ideographs Extension G: 3–3134F
CJK Unified Ideographs Extension H: 31350–323AF
Ref: https://www.unicode.org/versions/Unicode15.0.0/ch18.pdf 

I installed the IPAmj Font Character Finder on LibreOffice
Link https://extensions.libreoffice.org/en/extensions/show/1077

Japanese MJ character Information table Ver.066.01.
https://moji.or.jp/mojikiban/mjlist/

https://moji.or.jp/mojikiban/font/

IPAmj Font Character Finder can look for characters in the CJK Unified
Ideographs Extension B or higher range.
such as "럘Ă"(U+2B7D8) It's located in CJK Unified Ideographs Extension D.
https://www.unicode.org/cgi-bin/GetUnihanData.pl?codepoint=%F0%AB%9F%98

So, For LibreOffice's CJK Users, We need to support CJK Unified Ideographs
Extension Block C to H for Unicode15


Steps to Reproduce:
1. Install the IPAmj Font Character Finder extensions on LibreOffice
Link https://extensions.libreoffice.org/en/extensions/show/1077
2. input the 'MJ060164' for MJcode or '2B7D8'UCS code 
3. If the selected CJK font supports CJK Unified Ideographs Extension Block C
to H, It can show. 

Actual Results:
If the selected CJK font supports CJK Unified Ideographs Extension Block C to
H, It can show. 

Expected Results:
If the selected CJK font supports CJK Unified Ideographs Extension Block C to
H, It can show.


Reproducible: Always


User Profile Reset: No

Additional Info:

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

[Libreoffice-bugs] [Bug 154757] CPP unit tests: provide message converters to allow use of O(U)Strings as _MESSAGE argument

[bugzilla-daemon]

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

--- Comment #1 from Stephan Bergmann  ---
As I mentioned in the comment at

"tdf#154757 Provide O(U)String converters for _MESSAGE arguments":  "I think
the main issue here is that as soon as you need a CPPUNIT_ASSERT_MESSAGE with a
programmatically assembled message, your test is doing something wrong anyway. 
:)  Test code should be as straightforward to understand and to debug for
humans as possible.  Tempting as it may be, it ideally should not contain
[e.g.] any loops over data to test, it should rather spell out those individual
tests explicitly.  Probably each of us occasionally is a sinner in this respect
when writing tests, but my argument against such improvements for the
CPPUNIT_ASSERT_MESSAGE's message argument is always the same:  If you need it,
it would be better to restructure the test code (or, failing that, to bite the
bullet and have some explicit call to OUString::getStr or similar, in the 'bad'
test code)."

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

[Libreoffice-bugs] [Bug 150828] Make LibreOffice Writer digital signature functionality available in LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add signature without alterin

[bugzilla-daemon]

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

--- Comment #16 from Lars Uffmann  ---
PS: refer here
https://techhelp.mcla.edu/index.php/File:Readerdcwin3.png

(from article at
https://techhelp.mcla.edu/index.php?title=Creating_Self_Signed_Signatures_in_Adobe_Acrobat_Reader_DC=toggle_view_desktop
)

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

[Libreoffice-bugs] [Bug 150828] Make LibreOffice Writer digital signature functionality available in LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add signature without alterin

[bugzilla-daemon]

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

--- Comment #15 from Lars Uffmann  ---
(In reply to Alex Thurgood from comment #14)
> (In reply to Lars Uffmann from comment #13)
> 
>  
> > 2) "Insert"->"Signature Line" -> choose the desired area on a desired page
> > -> in the pop-up, select the signing certificate, "Select" -> "Finish
> > Signing"
> > Result 2: A stamp is added to the selected area, stating
> >   "Digitally signed by:
> >(certificate signer name)
> >Date: dd/mm/"
> >   with a PDF icon as the background image.
> > 
> 
> 
> This is similar to the way it works in Adobe Reader (on macOS at least, I
> can't speak for Windows) for trusted key signatures, i.e. the user is
> invited to draw an area on the page into which the digital signature is
> inserted with a timestamp after entering the passphrase key or PIN code.


Similar, but missing one crucial bit: in Adobe Reader (both on MacOS and
Windows), you can create a signature template, for which you can choose e.g. a
custom signature image.

Adobe Reader permits to toggle signature fields to be displayed in the
document:

[x] Common Name
[x] Distinguished Name
[x] Reason (for signing)
[x] Location
[x] Date
and an option to show a graphic (like LO Writer does)

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

[Libreoffice-bugs] [Bug 150828] Make LibreOffice Writer digital signature functionality available in LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add signature without alterin

[bugzilla-daemon]

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

--- Comment #14 from Alex Thurgood  ---
(In reply to Lars Uffmann from comment #13)


> 2) "Insert"->"Signature Line" -> choose the desired area on a desired page
> -> in the pop-up, select the signing certificate, "Select" -> "Finish
> Signing"
> Result 2: A stamp is added to the selected area, stating
>   "Digitally signed by:
>(certificate signer name)
>Date: dd/mm/"
>   with a PDF icon as the background image.
> 


This is similar to the way it works in Adobe Reader (on macOS at least, I can't
speak for Windows) for trusted key signatures, i.e. the user is invited to draw
an area on the page into which the digital signature is inserted with a
timestamp after entering the passphrase key or PIN code.

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

[Libreoffice-bugs] [Bug 147514] How many copies you want of something should not be hidden in the print dialog

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org

--- Comment #1 from V Stuart Foote  ---
Find no issue with layout of the print dialog 'Range and Copies' and 'Page
Layout' supplemented with their 'More' exposure triangles.

What is visible suffices and are core to configuring the print job. While the
'Number of copies' field would not fit cleanly on the default panel, and is not
relevant to core task of configuring what to print.  It can't all fit so the
'More' extenders are necessary anyway and the copies count is fine there.

IMHO => WF

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

[Libreoffice-bugs] [Bug 133507] contextual spacing wrong between normal text and section

[bugzilla-daemon]

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

--- Comment #5 from Justin L  ---
contextual spacing was added to LO in LO 3.6. (3.5.7 showed a 1cm gap in
between all of these paragraphs.)

(In reply to Regina Henschel from comment #0)
> So I expect, that there is a 1cm spacing between the forth and fifth
> paragraph, because the forth paragraph is inside the section and the fifth
> paragraph is outside the section
Yes, I would have expected spacing there also. As seen in the example, it DOES
work between "real" sections, but not when transitioning for an explicit
section to the main text body.

Unfortunately, for DOCX, MSO 2010 actually applies both the bottom AND top
spacing (so 2cm) instead of just a combined 1cm. (Also, in DOCX, everything is
a "real" section, except perhaps for the first section).

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

[Libreoffice-bugs] [Bug 155187] Newly inserted / deleted tables are not coloured when tracking changes.

[bugzilla-daemon]

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

--- Comment #2 from Commit Notification 
 ---
László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/3c1fee94e007a4c985572ec708bb60afa60f565d

tdf#155187 sw track changes: color tables in single changes

It will be available in 24.2.0.

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

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

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

[Libreoffice-bugs] [Bug 155187] Newly inserted / deleted tables are not coloured when tracking changes.

[bugzilla-daemon]

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

[Libreoffice-bugs] [Bug 143002] [META] Tracked Changes of tables

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=143002
Bug 143002 depends on bug 155187, which changed state.

Bug 155187 Summary: Newly inserted / deleted tables are not coloured when 
tracking changes.
https://bugs.documentfoundation.org/show_bug.cgi?id=155187

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155187] Newly inserted / deleted tables are not coloured when tracking changes.

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

   Assignee|nem...@numbertext.org   |libreoffice-b...@lists.free
   ||desktop.org
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

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

[Libreoffice-bugs] [Bug 146211] export to PDF/A-2b removes (qualified) signature

[bugzilla-daemon]

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

--- Comment #3 from Alex Thurgood  ---
I can confirm something similar, on macOS when exporting to PDF/A-3a.

I have an EIDAS hardware certificate (USB key) issued by CertEurope that uses
Trusted Key Manager for making the key available to the OS.

I have set up a security device per the supplier's recommendations in Firefox
so that the key is readable in a Firefox profile session after entry of a PIN
associated with the certificate on the physical USB key.

I can use this key to digitally & validly sign PDF files separately in Adobe
Reader.

I can also use the key within Firefox (via the security device configuration
tool under Security & Certificates)  to login to a court CMS for which the
certificate and key are required for the filing of signed and authenticated
transactions with the court CMS.


However, in LibreOffice, after the usual idiocy (bug 147291 or bug 153626) of
not being able to find a Certificate Manager, I can finally get LO to display
an entry dialog for the PIN, when I click directly on the "Sign" button (which
otherwise shows no available certificates).

I can then sign an ODT, but LibreOffice reports that it could not verify the
signature.

One has to ask how it can activate the digital signature and not be able to
validate it ?
What use is a X509 signature that isn't validated by the software application
that adds it to the document ?

CertEurope uses SHA-256 with RSA Encryption.

If I export the signed ODT to PDF(A/3b), opening the PDF in Adobe Reader
doesn't show the document as being signed, it seems that the signature is
silently removed, or not compliant with the PDF-A spec.

If I create an ODT without a signature, export to PDF using the signature tab
(which finds my X509 cert), the signature is considered valid in the PDF when
opened in Adobe Reader.

Am I missing something, or does signing X590 within the ODT not do anything
actually useful, and is it scrubbed when exporting the signed ODT to PDF/A2/3 ?

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

[Libreoffice-bugs] [Bug 150828] Make LibreOffice Writer digital signature functionality available in LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add signature without alterin

[bugzilla-daemon]

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

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||elto...@aucegypt.edu,
   ||t...@libreoffice.org
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 155819] SVG: marker not displayed

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED
   Keywords||bibisected, bisected,
   ||regression

--- Comment #1 from Xisco Faulí  ---
Regression introduced by 242b7d0162d55be0945ca849c3de841fbf6cb475

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

[Libreoffice-bugs] [Bug 155814] SVG: use + clip-path doesn't work

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

   Keywords||filter:svg

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

[Libreoffice-bugs] [Bug 155819] SVG: marker not displayed

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

   Keywords||filter:svg
 CC||xiscofa...@libreoffice.org

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

[Libreoffice-bugs] [Bug 155819] New: SVG: marker not displayed

[bugzilla-daemon]

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

Bug ID: 155819
   Summary: SVG: marker not displayed
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: filters and storage
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: xiscofa...@libreoffice.org

Created attachment 187894
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187894=edit
sample file

Steps to reproduce:
1. Open attached document
2. Compare it with another svg visor

-> The markers are not displayed

Reproduced in

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 244f9cf66bc36f229ccb5712bc8d80166b92266d
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 147291] macOS: Digital Signatures > Start Certificate Manager (OpenPGP) results in error instead of opening GPG Keychain

[bugzilla-daemon]

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

--- Comment #14 from Alex Thurgood  ---
(In reply to Heiko Tietze from comment #13)
> Some info on bug 142279. In a nutshell: some certificate manager are
> hard-coded and clicking the button is supposed to run these tools. Which
> depends on the OS but macOS has not been considered yet.
> 

Which is a very sad state of affairs given that we've been touting digital
signatures in our marketing hype since...


> Apple's keychain tool probably does not work with GPG / WoT but similarly to
> Windows with issued certificates. In that's true the keychain tool is
> worthless (see also bug 133941 for the situation on Windows).

FWIW, my CertEurope USB eIDAS key relies on a third party app called TKM
(Trusted Key Manager) to register the hardware key with the OS. The key isn't
automatically registered with Apple Keychain. I would have to export the CER
from the TKM app and then import it into the Keychain.app.

This type of USB hardware key  is used by the bar association of France for
filing court documents. 

It is also one of the allowed hardware signing/authentication/non-repudiation
keys used for filing documents with the Unified Patent Court.

LibreOffice won't find the cert outside of the Mozilla Firefox profile. For
example, if I put a copy of the cert in a folder in my home directory and point
LibreOffice manually to that folder, it can't find the key.

This means that the CER has to be referenced within the Firefox session by
creating a software security device containing the path to the DYLIB and then
loading that software security device into the Firefox session.

This IMHO is the biggest problem with cert management within LO at the moment,
to the extent that it relies on Mozilla profiles (Firefox or Thunderbird) to be
called when needed.

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

[Libreoffice-bugs] [Bug 150828] Make LibreOffice Writer digital signature functionality available in LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add signature without alterin

[bugzilla-daemon]

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

Lars Uffmann  changed:

   What|Removed |Added

Summary|Place digital signatures in |Make LibreOffice Writer
   |an existing PDF document|digital signature
   |with a visible stamp (e.g.  |functionality available in
   |signature scan) |LibreOffice Draw
   ||"File"->"Digital
   ||Signatures"->"Sign Existing
   ||PDF" (= add signature
   ||without altering the
   ||document)

--- Comment #13 from Lars Uffmann  ---
Edit 2023-06-13: changed title as suggested by Heiko in
https://bugs.documentfoundation.org/show_bug.cgi?id=150828#c7

New title: Make LibreOffice Writer digital signature functionality available in
LibreOffice Draw "File"->"Digital Signatures"->"Sign Existing PDF" (= add
signature without altering the document)

Old title: "Place digital signatures in an existing PDF document with a visible
stamp (e.g. signature scan)"

Added attachments to referenced Writer functionality:
1 - place signature field into document
2 - sign newly placed signature field
3 - choose name & signature pic & signing certificate
4 - resulting signed document


Currently, in LO Draw, the signing functionality is implemented as follows:
"File"->"Digital Signatures"->"Sign Existing PDF"

Then, multiple options are:
1) in the top blue bar "This PDF is open in read-only mode to allow signing the
existing file: choose "Sign Document", in the pop-up choose choose "Sign
Document" again, and choose a certificate.
Result 1: Signature is added to the document, but no visible indicator is
placed on any page

2) "Insert"->"Signature Line" -> choose the desired area on a desired page ->
in the pop-up, select the signing certificate, "Select" -> "Finish Signing"
Result 2: A stamp is added to the selected area, stating
  "Digitally signed by:
   (certificate signer name)
   Date: dd/mm/"
  with a PDF icon as the background image.

3) "File"->"Signature Line" -> same as 2)

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

[Libreoffice-bugs] [Bug 155814] SVG: use + clip-path doesn't work

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

 Attachment #187885|0   |1
is obsolete||

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

[Libreoffice-bugs] [Bug 155814] SVG: use + clip-path doesn't work

[bugzilla-daemon]

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

--- Comment #2 from Xisco Faulí  ---
Created attachment 187893
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187893=edit
sample file

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

[Libreoffice-bugs] [Bug 150828] Place digital signatures in an existing PDF document with a visible stamp (e.g. signature scan)

[bugzilla-daemon]

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

--- Comment #12 from Lars Uffmann  ---
Created attachment 187892
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187892=edit
resulting signed document with signature line as expected & as desired in Draw
for existing PDFs

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

[Libreoffice-bugs] [Bug 97539] INSERT: SVG clippath not fully supported

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155814] SVG: use + clip-path doesn't work

[bugzilla-daemon]

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

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=97
   ||539

--- Comment #1 from Xisco Faulí  ---
This is related to 82c0a363abbceac6464b62c3571aa3225415c7db

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

[Libreoffice-bugs] [Bug 150828] Place digital signatures in an existing PDF document with a visible stamp (e.g. signature scan)

[bugzilla-daemon]

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

--- Comment #11 from Lars Uffmann  ---
Created attachment 187891
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187891=edit
the desired pop-up with the possibility to choose a png/jpg for the signature
besides the signing certificate

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