[Libreoffice-bugs] [Bug 87892] More shapes for LibreOffice draw are needed

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87892

--- Comment #19 from matt...@sublunar.com ---
I'm not a coder or a UI programmer, I'm just a lowly end user. It seems I
always end up using Libre Office Draw to make network diagrams.  I get by with
rectangles and circles with lots of text, but it would be really wonderful if I
had an easy way to convert and import arbitrary shapes into draw.  Basically
DIA is just too clunky for my taste and honestly the available images aren't so
wonderful if you aren't doing Cisco networking.

I'm a Mac user, I used to have a proprietary application for this kind of work,
but I just can't keep up with the ever changing system requirements/

Thanks

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

[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152406

--- Comment #30 from Telesto  ---
FWIW. Some pointers. Setting the scroll factor from 1.5 to 1.0 in
https://opengrok.libreoffice.org/xref/core/vcl/osx/salframeview.mm?r=57b88be1#43
appears to solve the problem in case of swiping (didn't check with mouse with
scroll wheel)

The "-(void)scrollWheel: (NSEvent*)pEvent" code appears to be actually used
when swiping. So this
https://opengrok.libreoffice.org/xref/core/vcl/osx/salframeview.mm?r=57b88be1#1028

The apparently dedicated code for swipe events "- (void)swipeWithEvent:
(NSEvent*)pEvent"  which is more or less a copy of "-(void)scrollWheel:
(NSEvent*)pEvent" 
https://opengrok.libreoffice.org/xref/core/vcl/osx/salframeview.mm?r=57b88be1#969
does nothing. I commented out that part, but I don't notice any difference at
all

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

[Libreoffice-bugs] [Bug 153951] Toolbar ui misplacing on mac

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153951

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 152220] Previously displayed Preference tab is shown in background (in macos dark mode)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152220

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 150060] Keyboard Shortcuts for Black and White Screen don't work (Presentation Mode)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150060

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 153911] Warning when opening files with other files already open

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153911

--- 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 153976] Calc fails to resize PNG files properly

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153976

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 153965] Fields are stacked when creating a form with the helper

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153965

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 153974] Wrong choice of page margins when importing a PDF with RTL paragraph

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153974

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 153961] contextual spacing / "Do not add space..." does not work and is not saved.

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153961

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 153967] Writer import filter misinterprets/ignores direction of RTL lines

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153967

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 153063] Save dialog not working properly in spaces on MacOsX

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153063

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 153063] Save dialog not working properly in spaces on MacOsX

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153063

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

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

[Libreoffice-bugs] [Bug 152220] Previously displayed Preference tab is shown in background (in macos dark mode)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152220

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 146626] Calc crashes every time on font size operation, in a specific document

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146626

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 152220] Previously displayed Preference tab is shown in background (in macos dark mode)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152220

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

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

[Libreoffice-bugs] [Bug 146626] Calc crashes every time on font size operation, in a specific document

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146626

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

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

[Libreoffice-bugs] [Bug 141615] Documents fail to render properly with LibreOffice 7 on big endian

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141615

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150950] line numbering ON/OFF indication in Tools menu

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150950

--- Comment #4 from QA Administrators  ---
Dear peter josvai,

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 148878] If a CSV file doesn't keep delimiter

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148878

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

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 141615] Documents fail to render properly with LibreOffice 7 on big endian

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141615

--- Comment #11 from QA Administrators  ---
Dear chmeeedalf+lo,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-ux-advise] [Bug 150950] line numbering ON/OFF indication in Tools menu

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150950

--- Comment #4 from QA Administrators  ---
Dear peter josvai,

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 on the CC list for the bug.

[Libreoffice-bugs] [Bug 149510] LibreOffice windows in gnome 42 can be resized to be extremely small x11

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149510

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

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-ux-advise] [Bug 147479] Pivot table display (empty) when data source is null

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147479

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

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 on the CC list for the bug.

[Libreoffice-bugs] [Bug 139617] Optimal height isn't applied when shrinking word-wrapped cell (nor after entering the cell), only when content changes

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139617

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

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 147479] Pivot table display (empty) when data source is null

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147479

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

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 98412] SIDEBAR: Line properties not always updated

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98412

--- Comment #9 from QA Administrators  ---
Dear Laurent BP,

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 84765] Impress Remote: add support for handling hidden slides

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84765

--- Comment #17 from QA Administrators  ---
Dear Davide Depau,

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 76785] User-defined colors in Excel not loaded properly from xls

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76785

--- Comment #11 from QA Administrators  ---
Dear M Welinder,

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 78955] Other: pasting composite selections with graphs from ods to odt-file does not preserve lines in charts linear and logarithmic

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=78955

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

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 68679] Bar charts do not allow timestamps

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68679

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

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 66617] chart2 unoapi test fails on sch.ChXDiagram::com::sun::star::chart::ChartStatistics::RegressionCurves

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=66617

--- Comment #12 from QA Administrators  ---
Dear Michael Stahl (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 66217] Wrong formatting when pasting as HTML for a text copied from Notepad++ (win only)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=66217

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

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 141101] The font color popup is not accessible to screen readers on Windows

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141101

--- Comment #2 from QA Administrators  ---
Dear Marco Zehe,

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 141060] Undesired space added after drag & drop to the end of the line

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141060

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 140683] Shift of view, after export of the document to xml (Writer)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140683

--- Comment #4 from QA Administrators  ---
Dear PiotrS.,

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 139405] FILESAVE XLSX Named range with name S not allowed in Excel is saved to XLSX

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139405

--- Comment #7 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 135838] Switching anchor from to page to paragraph attaches the image to header

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135838

--- 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 132562] Fixed column size and fixed row size don't match on the screen. Inserted image matches or doesn't match depending on whether the image has dpi set or not.

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132562

--- Comment #2 from QA Administrators  ---
Dear iggy.h,

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 125513] White rendering artefacts between Writer pages on macOS

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125513

--- Comment #11 from QA Administrators  ---
Dear Thorsten Wagner,

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 134458] FILEOPEN DOC Images in columns are misplaced

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134458

--- Comment #8 from QA Administrators  ---
Dear NSO 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 117501] FILEOPEN: DOCX: Incorrect field character style (see comment 5)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117501

--- Comment #10 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 117882] Deleting a row or adding a column decreases the height of the lines in spreadsheet.

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117882

--- Comment #18 from QA Administrators  ---
Dear Salim Habchi,

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 116040] Under specific conditions OR is acting in formulas as a Boolean operator. Same with AND

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116040

--- Comment #7 from QA Administrators  ---
Dear Wolfgang Jäger,

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 116439] OS/2 multi-image bitmap does not display correctly

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116439

--- Comment #6 from QA Administrators  ---
Dear Chris Sherlock,

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 115049] DatabaseImportDescriptors still parse SQL, even when IsNative is set to True

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115049

--- Comment #5 from QA Administrators  ---
Dear jan.benda,

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 116435] XML Form Document: Impossible to rename default-value "instanceData"

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116435

--- Comment #6 from QA Administrators  ---
Dear Robert Großkopf,

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 101611] pdfimport filter does not honor page cropping (masking) as set in a PDF document, resulting pages in LO document are oversize (comment 4)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101611

--- Comment #11 from QA Administrators  ---
Dear E.Mi,

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 154266] New: files not visible in Save|Open dialogs

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154266

Bug ID: 154266
   Summary: files not visible in Save|Open dialogs
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: p...@pfortin.com

Created attachment 186064
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186064=edit
Save dialog with all but one file invisible.

For several releases, the file dialogs do not display the files; only the file
under the cursor.  
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e1c6f36d8bcc0799281e3a7e244175f682d97cb2
CPU threads: 20; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded Jumbo

Trying to load or save a file, only the file under the cursor is visible --
until I click on it, then the blue bar stays visible; but the filename becomes
invisible.  LODev is the only application exhibiting this issue.

It's like the font is white on white for all other entries except the file
under the mouse cursor.  I kept assuming this would have been noticed; but I
may be the only one seeing this.  I did nothing to affect this; I simply update
LO every few days...

This is not a problem in LO 7.5.
Version: 7.5.1.2 (X86_64)
Build ID: 50(Build:2)
CPU threads: 20; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded Jumbo

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

[Libreoffice-bugs] [Bug 154265] Cannot return to (first) slide when in presentation mode

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154265

--- Comment #1 from Gerald Pfeifer  ---
Created attachment 186063
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186063=edit
Simplified sample document

I think I managed to simplify the original sample document even further.

Note that PowerPoint *is* able to return to the first slide for both of
these documents via  or .

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

[Libreoffice-bugs] [Bug 154265] New: Cannot return to (first) slide when in presentation mode

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154265

Bug ID: 154265
   Summary: Cannot return to (first) slide when in presentation
mode
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ger...@pfeifer.com

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

How to reproduce:

 1. Open sample document.
 2. Start presentation mode and proceed to the last slide.
 3. Try to return to earlier slides (via  or ).
 4. Notice how you never are able to return to slide 1.

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

back to 6.4 and likely earlier.

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

[Libreoffice-bugs] [Bug 132983] Automatically calculate known variance values for Z-test

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132983

--- Comment #10 from Felipe Viggiano  ---
This situation is still going on on LibreOffice 7.4.

When using the z-test feature, LibreOffice is still failing to calculate the
variance of the dataset. It continues to return a a zero value for the variance
of both inputs, when it should be using a formula like =VAR(Input).

To reproduce:

Insert two columns of random data (about 10 lines is fine). Go to the Z-test
feature in Data/Statistics and perform a Z-test using those two.



Version: 7.4.6.2
Build ID: 40(Build:2)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR
Calc: threaded

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

[Libreoffice-bugs] [Bug 80952] UI: Writer dialog Insert Frame, tab Background, choice Color, doesn't show colors..

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=80952

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 91129] comment seems empty when opening, editing not possible

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91129

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 100642] Custom Animations "Fly In" and "Fly in Slow" stopped working

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100642

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 65519] UI: Closing "Execute SQL Statement" closes LO completely

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65519

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 143415] Sheet navigation right click needs two clicks to close (Windows-only)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143415

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 139184] FORMS: List Box wizard shows error for SDBC-Driver evolution local (GTK 3 only)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139184

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 144612] Calc is slow/lag when typing/inputing values in a cell in 7.2 for some users

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144612

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 134237] Soft edge feature produces lag when scrolling (and mouse-scrolling to zoom) multiple high-resolution images in Draw

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134237

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 146047] UI: Orientation Landscape in Print dialog doesn't do anything

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146047

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 134525] File open/file copy/paste requires 3-4x more memory

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134525

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 148327] table row still visible after deletion with track & changes enabled (comment 3)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148327

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 144337] Unable to send combined correspondence (send emails) using Writer LO Fresh 7.2.0

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144337

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 150568] FILESAVE DOCX: Additional page created

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150568

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 141473] LO Writer failed to load .doc with Courier font from the Wayback Machine (regression)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141473

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 148511] Dragging top handle of the table border to increase the size of table refuses

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148511

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 147792] MySQL/MariaDB direct connection: Autoincrement won't be saved by table editor

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147792

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 152516] Crash pressing edit table in Base

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152516

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 151664] Rendered text shifted with some Hebrew fonts - but not in PDF output

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151664

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |
 CC||aron.bu...@gmail.com

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

[Libreoffice-bugs] [Bug 145122] Linux/KDE: Cursor disappears while creating a table in Base, switching between text and styles in Writer …

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145122

Aron Budea  changed:

   What|Removed |Added

 CC||aron.bu...@gmail.com
   Keywords|bibisectRequest |

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

[Libreoffice-bugs] [Bug 154261] The helppack works on Windows 7 but not on Windows11

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154261

V Stuart Foote  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from V Stuart Foote  ---
Installing the help package sets up a set of local HTTP content--system default
browser must be allowed to run the CSS and javascript needed to view the pages.

It is possible Windows 11 or some AV filter is disallowing the run of local
Help as insecure. We'd like to know more.

So, please describe where you obtained the installers for LibreOffice 7.5.1 and
the language/script specific help pack.

But first thing is to verify that the installed help pack has correct size and
signature.

Use the details link from:

https://downloadarchive.documentfoundation.org/libreoffice/old/7.5.1.2/win/x86_64/

It will include HASH values MD5, SHA1, SHA256 as well as a link to the PGP
signature. Check your downloads against those values.

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

[Libreoffice-bugs] [Bug 113374] [META] Language and help package issues

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113374

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||154261


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154261
[Bug 154261] The helppack works on Windows 7 but not on Windows11
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154261] The helppack works on Windows 7 but not on Windows11

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154261

V Stuart Foote  changed:

   What|Removed |Added

 Blocks||106040, 113374
 OS|All |Windows (All)
 CC||vsfo...@libreoffice.org


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106040
[Bug 106040] [META] Help bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113374
[Bug 113374] [META] Language and help package issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 106040] [META] Help bugs and enhancements

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106040

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||154261


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154261
[Bug 154261] The helppack works on Windows 7 but not on Windows11
-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2023-03-18 Thread Caolán McNamara (via logerrit)
 comphelper/source/officeinstdir/officeinstallationdirectories.hxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41
Author: Caolán McNamara 
AuthorDate: Sat Mar 18 19:56:48 2023 +
Commit: Caolán McNamara 
CommitDate: Sat Mar 18 23:27:08 2023 +

probably a good idea not to have two things called comphelper::UnoImplBase

Change-Id: Ib2b4456c55bcb65fba1ec67739ba08b22a4fcae0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149086
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/comphelper/source/officeinstdir/officeinstallationdirectories.hxx 
b/comphelper/source/officeinstdir/officeinstallationdirectories.hxx
index 09ded59b9a53..d0d86b76c4d5 100644
--- a/comphelper/source/officeinstdir/officeinstallationdirectories.hxx
+++ b/comphelper/source/officeinstdir/officeinstallationdirectories.hxx
@@ -35,9 +35,9 @@ namespace comphelper {
 
 typedef cppu::WeakImplHelper<
 css::util::XOfficeInstallationDirectories,
-css::lang::XServiceInfo > UnoImplBase;
+css::lang::XServiceInfo > OfficeInstallationDirectories_Base;
 
-class OfficeInstallationDirectories : public UnoImplBase
+class OfficeInstallationDirectories : public OfficeInstallationDirectories_Base
 {
 public:
 explicit OfficeInstallationDirectories(


[Libreoffice-bugs] [Bug 154264] New: LO Writer freezes while pasting from web and saving document

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154264

Bug ID: 154264
   Summary: LO Writer freezes while pasting from web and saving
document
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rajasekara...@gmail.com

I just copied and pasted two paragraphs of texts from Firefox to LO writer,it
hanged for more than five minutes.By using Task Mananger onyl,I could end the
task.Couldn't save and recover the document even after document recovery. 

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d887b6a6fa2a572f48498839c5a68791c3196634
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
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 134339] Export to pdf with "reduce resolution of images to 300 dpi" can increase image resolution and create bloated file

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=134339

eisa01  changed:

   What|Removed |Added

Summary|Export to pdf creates big   |Export to pdf with "reduce
   |bloated file|resolution of images to 300
   ||dpi" can increase image
   ||resolution and create
   ||bloated file
 OS|macOS (All) |All

--- Comment #24 from eisa01  ---
Ok, so if I read this correctly checking the "reduce resolution of images"
option can actually increase the resolution of images?

Still present, and it is not limited to macOS as mentioned in comments

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 136583] Some resources from embedded PDF files (mainly those created by Scribus) disappear when exporting to PDF

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=136583

eisa01  changed:

   What|Removed |Added

 OS|macOS (All) |All
   Keywords||filter:pdf
   Hardware|x86-64 (AMD64)  |All

--- Comment #9 from eisa01  ---
Ok, so this is not limited to macOS, although the exported file looks different
on Linux (albeit in a different version)

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded 

Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Debian package version: 1:7.0.4-4+deb11u4
Calc: threaded

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

[Libreoffice-bugs] [Bug 145095] PPT to PDF: Text with shadow effect is duplicated.

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145095

--- Comment #9 from eisa01  ---
Created attachment 186061
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186061=edit
Export of the ppt from PowerPoint

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

[Libreoffice-bugs] [Bug 145095] PPT to PDF: Text with shadow effect is duplicated.

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145095

eisa01  changed:

   What|Removed |Added

 OS|macOS (All) |All

--- Comment #8 from eisa01  ---
Still present, and likely not macOS only given the component

PowerPoint manage to export a file that doesn't have duplicate text layers when
copied out of Preview. However, copying out from Firefox PDF viewer does not
exhibit duplicate text

There's quite a few bugs exhibited in Preview only...

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152877] Dates are getting formatted as dollar amounts and can't change

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152877

eisa01  changed:

   What|Removed |Added

 OS|macOS (All) |All
 Status|NEW |NEEDINFO

--- Comment #2 from eisa01  ---
So this would likely not be macOS specific

It is also not a bug that spreadsheets store Dates as numbers, that's standard
behavior

For the ods from 6.x series in 7.4.3, does that corruption still happen with
the new 7.5?

If so, can you upload a sample document that shows fine in 6.x, but not in 7.5?
So not the document you may have saved in 7.5

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

[Libreoffice-bugs] [Bug 154263] New: There is no way to anchor an image to the frame of the first label in a MAILMERGE sheet and synchronize it across all labels

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154263

Bug ID: 154263
   Summary: There is no way to anchor an image to the frame of the
first label in a MAILMERGE sheet and synchronize it
across all labels
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@kamens.us

Description:
Note: This is about 7.5.2.1 but that isn't a choice in the version list.


You should be able to anchor an inserted image to an absolute position within
the first label in a synchronized labels document and have that image
synchronize to the same position in all of the other labels when you click the
"Synchronize Labels" button.

If you anchor it to the page, it doesn't synchronize. If you anchor it to the
frame, it doesn't synchronize. It synchronize if you anchor it to the paragraph
or character or as a character, but then it floats with the text, which is no
good if you want it to have an absolute position within each label regardless
of the text.

This is especially important if you're formatting labels with mail merge
fields, because in that case the mail merge field names may be so long that
they flow over multiple lines when the data inserted into the actual labels
won't, so you literally can't see where the image is actually going to end up
in the labels if you anchor it to text after the field names.

I suppose theoretically you could anchor it to the very beginning of the text,
maybe, as a workaround? But you really should be able to do an absolute
position anchor on the label.

Steps to Reproduce:
See above.

Actual Results:
See above.

Expected Results:
See above.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.2.1 (X86_64) / LibreOffice Community
Build ID: 50(Build:1)
CPU threads: 16; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc1-0ubuntu1
Calc: threaded

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

[Libreoffice-bugs] [Bug 36799] If you insert an envelope into a document only the envelope is printed on macOS

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=36799

eisa01  changed:

   What|Removed |Added

Summary|If you insert an envelope   |If you insert an envelope
   |into a document only the|into a document only the
   |envelope is printed (Mac OS |envelope is printed on
   |X)  |macOS
   Hardware|Other   |All

--- Comment #39 from eisa01  ---
This is still present, and not present on Linux

You don't have to physically print though, it's sufficient to use the print
dialog and try to save to PDF from there

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 154262] New: MAILMERGE does the wrong thing with multiple "Next Record" field from different databases

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154262

Bug ID: 154262
   Summary: MAILMERGE does the wrong thing with multiple "Next
Record" field from different databases
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@kamens.us

Description:
If you do a mail merge into labels with multiple "Next Record" fields from
different database, the results are totally wrong.

Note: This is about LibreOffice 7.5.2.1 but that's not a choice in the version
list.

Steps to Reproduce:
1. Create a spreadsheet with two cells: A1="field1", B1="value1". Save it as
"calc1.ods".
2. Create and register a database called "db1" connected to it.
3. Create a spreadsheet with two cells: A1="field2", B2="value2". Save it as
"calc2.ods".
4. Create and register a database called "db2" connected to it.
5. Create a labels document with this in it, synchronized across all labels:
   DB1: 
   DB2: 
   Where "field1" and "nr1" are fields from db1 (the latter is the "Next
Record" for the database, and "field2" and "nr2" are from db2.
6. Print to mail merge into a file.

Actual Results:
The first label in step 6's output file looks like this:

DB1: 
DB2: value2

The first label in step 8's output file looks like this:



Expected Results:
The first label in the output file should look like this:

DB1: value1
DB2: value2


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.2.1 (X86_64) / LibreOffice Community
Build ID: 50(Build:1)
CPU threads: 16; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc1-0ubuntu1
Calc: threaded

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

[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - sw/source

2023-03-18 Thread Xisco Fauli (via logerrit)
 sw/source/uibase/app/docsh2.cxx |   11 ++-
 1 file changed, 6 insertions(+), 5 deletions(-)

New commits:
commit 1b93a30a113e45cbf67b0683e233568e40446deb
Author: Xisco Fauli 
AuthorDate: Thu Mar 16 16:26:17 2023 +0100
Commit: Caolán McNamara 
CommitDate: Sat Mar 18 21:55:36 2023 +

sw: fix null dereference

See 
https://crashreport.libreoffice.org/stats/signature/SfxDispatcher::ExecuteList(unsigned%20short,SfxCallMode,std::initializer_list%3CSfxPoolItem%20const%20*%3E,std::initializer_list%3CSfxPoolItem%20const%20*%3E)

Change-Id: I7f5471f003798f260d9d015782bd2a798baa22d2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148999
Reviewed-by: Caolán McNamara 
Tested-by: Jenkins
Reviewed-by: Xisco Fauli 
(cherry picked from commit 11ce7e810ef5ba540afe676d58575fabf4ab386d)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149019

diff --git a/sw/source/uibase/app/docsh2.cxx b/sw/source/uibase/app/docsh2.cxx
index e5b7b63c43d0..83ea01b75b91 100644
--- a/sw/source/uibase/app/docsh2.cxx
+++ b/sw/source/uibase/app/docsh2.cxx
@@ -1185,11 +1185,12 @@ void SwDocShell::Execute(SfxRequest& rReq)
 // Ok.  I did my best.
 break;
 
-SfxStringItem aApp(SID_DOC_SERVICE, 
"com.sun.star.text.TextDocument");
-SfxStringItem aTarget(SID_TARGETNAME, "_blank");
-pViewShell->GetDispatcher()->ExecuteList(SID_OPENDOC,
-SfxCallMode::API|SfxCallMode::SYNCHRON,
-{ ,  });
+if (SfxDispatcher* pDispatch = pViewShell->GetDispatcher())
+{
+SfxStringItem aApp(SID_DOC_SERVICE, 
"com.sun.star.text.TextDocument");
+SfxStringItem aTarget(SID_TARGETNAME, "_blank");
+pDispatch->ExecuteList(SID_OPENDOC, 
SfxCallMode::API|SfxCallMode::SYNCHRON, { ,  });
+}
 }
 break;
 case SID_CLASSIFICATION_APPLY:


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

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71732
Bug 71732 depends on bug 42000, which changed state.

Bug 42000 Summary: WRITER: Character font cap height is not displayed on 
capital letters
https://bugs.documentfoundation.org/show_bug.cgi?id=42000

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 56932] (Writer) While scrolling text is distorted and some parts of the glyphs are horizontally split/disappearing

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=56932
Bug 56932 depends on bug 42000, which changed state.

Bug 42000 Summary: WRITER: Character font cap height is not displayed on 
capital letters
https://bugs.documentfoundation.org/show_bug.cgi?id=42000

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 42000] WRITER: Character font cap height is not displayed on capital letters

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42000

eisa01  changed:

   What|Removed |Added

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

--- Comment #22 from eisa01  ---
This works for me now. Retina display on 14" M1 MBP

Tested with the shift+q character on Russian keyboard layout and Helvetica

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 153142] IsMissing needs a note about use in conditions (no boolean short-circuit evaluation in Basic)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153142

--- Comment #2 from Mike Kaganski  ---
(In reply to Andreas Heinisch from comment #1)

I would like to see it in Basic, but this would be an incompatible change,
breaking any possible existing code that relies on side effects of
unconditional evaluation of all expressions.

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

[Libreoffice-bugs] [Bug 138864] FILESAVE DOCX Incorrect style names when opened in MS Office for Mac

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138864

eisa01  changed:

   What|Removed |Added

   Keywords||filter:docx
   Hardware|x86-64 (AMD64)  |All
  Component|Writer  |filters and storage
 OS|macOS (All) |All
Summary|FILESAVE DOCX Incorrect |FILESAVE DOCX Incorrect
   |style names (MS Office for  |style names when opened in
   |Mac)|MS Office for Mac

--- Comment #7 from eisa01  ---
Ok, so this is not a macOS bug. But it shows up in MS Office for mac :)

The style pane in MS office for mac has a lot of squares in the style

Still present

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Debian package version: 1:7.0.4-4+deb11u4
Calc: threaded

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

[Libreoffice-bugs] [Bug 138864] FILESAVE DOCX Incorrect style names (MS Office for Mac)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138864

--- Comment #6 from eisa01  ---
Created attachment 186060
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186060=edit
Docx Saved on LO 7.0 on Debian

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

[Libreoffice-bugs] [Bug 154261] New: The helppack works on Windows 7 but not on Windows11

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154261

Bug ID: 154261
   Summary: The helppack works on Windows 7 but not on Windows11
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@pingotec.com

Description:
I installed the very same version 7.5.1 on windows 11 and on windows 7. Then
the very same Helppack on both. On Windows 7 the Help click > LibreOffice help
loaded the offline help. On windows !! it opens what looks like a document with
a blank document screen instead of the help page. Both systems were tested
offline.

Actual Results:
Load both the 7.5.1 version and the Helppack, both for Windows 86-64 and create
a document and click on Help > LibreOffice help.

Expected Results:
on Windows 7 it worked perfectly. On windows 11, loading the very same software
and HelpPack, clicking on Help > LibreOffice Help gets a blank document instead
of help pages.


Reproducible: Always


User Profile Reset: No

Additional Info:
On Windows 11 the screen should display the help file instead of a blank
document. I run my Windows 11 system offline and tested Windows 7 offline to
compare the results on both.

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

[Libreoffice-bugs] [Bug 113023] [META] MacOS performance issues

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113023
Bug 113023 depends on bug 127261, which changed state.

Bug 127261 Summary: Very slow verifying upon first run (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=127261

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 127261] Very slow verifying upon first run (macOS)

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127261

eisa01  changed:

   What|Removed |Added

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

--- Comment #5 from eisa01  ---
I don't have this behavior any more

I think it improved after the compression of the disk image was changed?

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

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

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103100
Bug 103100 depends on bug 132324, which changed state.

Bug 132324 Summary: Pasted table has larger borders in Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=132324

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 132324] Pasted table has larger borders in Mac

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132324

eisa01  changed:

   What|Removed |Added

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

--- Comment #9 from eisa01  ---
Borders in sample document looks fine

Version: 7.5.1.2 (AARCH64) / LibreOffice Community
Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 154259] MAILMERGE omits entire line if all the fields on that line are empty in database

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154259

Jonathan Kamens  changed:

   What|Removed |Added

Summary|Mail merge omits entire |MAILMERGE omits entire line
   |line if all the fields on   |if all the fields on that
   |that line are empty in  |line are empty in database
   |database|

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

[Libreoffice-bugs] [Bug 154260] New: MAILMERGE loses space at the end of calculated field when merging from xlsx, works fine from ods

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154260

Bug ID: 154260
   Summary: MAILMERGE loses space at the end of calculated field
when merging from xlsx, works fine from ods
   Product: LibreOffice
   Version: 7.5.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@kamens.us

Description:
Note: I encountered this in 7.5.2.1 but that isn't available as a choice in the
Version list.

1. Create a blank spreadsheet.
2. Put "c" in A1.
3. Put "=CONCAT(","," ")" in B1.
4. Save it in XLSX format.
5. Create and register a new database connected to the spreadsheet.
6. Create a new labels document, with a single synchronized label.
7. In the first label put "BeforeAfter", where "" is the "c" mail
merge field from the database and "" is the next record field from the same
database sheet.
8. Synchronize the labels.
9. Print to a mail merge file.
10. Open the resulting file.
11. Observe that it says "Before,After" instead of "Before, After", i.e., the
space that should be after the comma is missing.

If you repeat all of the above steps with an ODS file instead of an XLSX file
this problem does not occur.


Steps to Reproduce:
See above.

Actual Results:
See above.

Expected Results:
See above.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.2.1 (X86_64) / LibreOffice Community
Build ID: 50(Build:1)
CPU threads: 16; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc1-0ubuntu1
Calc: threaded

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

[Libreoffice-bugs] [Bug 149122] Open visio in Draw changes circular corner rectangular components

2023-03-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149122

eisa01  changed:

   What|Removed |Added

Version|7.1.4.2 release |7.0.4.2 release

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

  1   2   3   4   >