[Libreoffice-bugs] [Bug 124462] Crash if I open the File dialog and click the 'Save' tab

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124462

Bruce Wayne  changed:

   What|Removed |Added

 Resolution|INVALID |FIXED

--- Comment #17 from Bruce Wayne  ---
I really enjoyed reading your blog, you have lots of great content. Please
visit here:
http://enterproductkey.com/
https://mcafee-activate.me/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124462] Crash if I open the File dialog and click the 'Save' tab

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124462

Bruce Wayne  changed:

   What|Removed |Added

URL|http://umcafee.com/activate |http://omcafee.com/
   |/   |

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102847
Bug 102847 depends on bug 101129, which changed state.

Bug 101129 Summary: Message [placeholder for message] at end of find bar
https://bugs.documentfoundation.org/show_bug.cgi?id=101129

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 101129] Message [placeholder for message] at end of find bar

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101129

Jim Raykowski  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124546] Negative numbers in red in the graphs

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124546

QA Administrators  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 58132] : Button “Reset” in Option Dialogs does not Work as expected

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58132

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 125116] LibreOffice 6.0.7.3 does not display images, displays image border only, image border overwrites footer.

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125116

--- Comment #3 from QA Administrators  ---
Dear Tom Johnson,

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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124546] Negative numbers in red in the graphs

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124546

--- Comment #4 from QA Administrators  ---
Dear Júnio Vieira,

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-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 58134] Reset Button in Options Dialogues does not Work with all Options

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58134

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 70841] FILESAVE: export to Excel 2003 XML (aka XMLSS) format issues

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=70841

--- Comment #14 from QA Administrators  ---
Dear dg,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 98435] dBase accepts invalid column name in select list

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98435

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 120852] FILEOPEN: DOCX set to read-only via "Restrict Editing" can be edited in LO

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120852

--- Comment #5 from QA Administrators  ---
Dear Aron Budea,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 120857] FILEOPEN DOC protected without pw can be edited

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120857

--- Comment #5 from QA Administrators  ---
Dear Aron Budea,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 115547] Firebird: Link is formed to an external file with file:///C: (three slash)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115547

--- Comment #22 from QA Administrators  ---
Dear shar,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 58929] Paste action disables cell navigation with Enter and Tab

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=58929

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

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 50045] FILESAVE Cannot 'Save graphics' from OLE object

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=50045

--- Comment #7 from QA Administrators  ---
Dear Pavel Kysilka,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 51267] after removing registrymodifications.xcu the existing user/basic/dialog.xlc and scrip.xlc are overwritten and existing user libraries seem lost

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=51267

--- Comment #20 from QA Administrators  ---
Dear Cor Nouws,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 61345] Options dialog: last checked date/time doesn't update

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61345

--- Comment #7 from QA Administrators  ---
Dear Thomas van der Meulen,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 61649] PRINTING: Printing Selected Frame doesn't print frame contents

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=61649

--- Comment #7 from QA Administrators  ---
Dear Matt Needles,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 67478] FILEOPEN: General Error for Word 2003 XML document of filetype DOC or XML (just DOCX works)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=67478

--- Comment #18 from QA Administrators  ---
Dear Razvan Calugarasu,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 120737] Word count starting again when pasting unformatted text to a footnote

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120737

--- 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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 59526] libcdr: Stretched rectangle fault import

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=59526

--- Comment #9 from QA Administrators  ---
Dear ralf.krapf,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128535] Updater offers incorrect new version

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128535

V Stuart Foote  changed:

   What|Removed |Added

 CC||cl...@documentfoundation.or
   ||g, vstuart.fo...@utsa.edu
URL||https://cgit.freedesktop.or
   ||g/libreoffice/website/tree/
   ||check.php?h=update
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from V Stuart Foote  ---
This is an infrastructure issue. The ref CURL posted check script again needs
signature updates done periodically during release cycles.

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 90456] Check for updates on Windows release builds responding "... up to Date"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90456

V Stuart Foote  changed:

   What|Removed |Added

 CC||dbonham+bugzi...@gmail.com

--- Comment #17 from V Stuart Foote  ---
*** Bug 128535 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 113066] Writer wrongly shows graphics semicircles from CAD that were pasted as GDI (preview in MSO fine but same issue if edited)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113066

--- Comment #11 from QA Administrators  ---
Dear archie,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 89288] Extra space displayed when Indic text meets non-Indic.

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89288

--- Comment #11 from QA Administrators  ---
Dear ssmithg1,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 101129] Message [placeholder for message] at end of find bar

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101129

--- Comment #22 from QA Administrators  ---
Dear B.J. Herbison,

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
http://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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 115871] "Standard" button in style dialogs fails to remove attributes

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115871

--- Comment #5 from Kenneth Hanson  ---
As of v6.3.2.2, problems with borders seem to fixed, at least for a fresh test
document.

No change to the numbering problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 117265] PDF export in Draw uses the "document background" application color in PDF export

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117265

--- Comment #3 from Kenneth Hanson  ---
No change as of v6.3.2.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 109135] SIDEBAR: Keyboard shortcuts don't work when a sidebar element is active

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109135

--- Comment #6 from Kenneth Hanson  ---
Upon quick testing, the problem seems to be partially solved as of v6.3.2.2.

For each test, I single-clicked a style in the sidebar and then pressed a key
combo.

Ctrl-C copied text. F1 opened help. Ctrl-M removed formatting. Ctrl-Shift-M
removed character styles.

Ctrl-0 DID NOT set the paragraph style. Nor did Ctrl-1. But they DID work
immediately after *double clicking* to apply a style, and other shortcuts such
as Ctrl-2 and Ctrl-3 DID work after either a single or double click.

This seemed crazy, so I tried several times, but the effect seems consistent.

The properties sidebar seems to be doing better: all style shortcuts worked.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 109029] Character style percentage font sizes are not updated automatically

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=109029

--- Comment #5 from Kenneth Hanson  ---
No change as of v6.3.2.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128542] In cell edit mode keyboard short CTRL + X doesn't work the first time for cut text in cell

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128542

--- Comment #1 from mugab...@gmail.com ---
Operating system Manjaro linux
gnome version 3.34

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128542] New: In cell edit mode keyboard short CTRL + X doesn't work the first time for cut text in cell

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128542

Bug ID: 128542
   Summary: In cell edit mode keyboard short CTRL + X doesn't work
the first time for cut text in cell
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mugab...@gmail.com

Description:
In edit mode of cell the keyboard shortcut CTRL + V doesn't work from the first
time. One has to undo last action, e.g the cut process and redo it the
cut/paste process once again to have it working.

Steps to Reproduce:
1.Enter edit mode cell. Make sure not to do this after just opening libreoffice
calc
2. select portion of text in the cell
3. use keyboard shortcut CTRL + X to cut the selected text
4. Paste cut text in other cell -> No content is pasted
5. Undo last action
6. use keyboard shortcut CTRL + X to cut the selected text
7. Paste cut text in other cell -> Now content is being pasted in the other
cell

Actual Results:
Keyboard shortcut CTRL + X doesn't work the first time in edit mode of cell.

Expected Results:
The keyboard shortcut CTRL + X should work the first, i.e. it should be
possible to paste the text after the first CTRL + X.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128503] Incorrect results from regular expresions from COUNTIF (but not from REGEX)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128503

m.a.riosv  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #9 from m.a.riosv  ---
Well I'm not able  to figure out what can be, no changes in calculation or
formula options for calc makes any difference.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128540] EPUB tool: some Error and Warning discovered after conversion with a validator

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128540

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #2 from Julien Nabet  ---
3.3.2 is a very old version.
Could you give a try to 6.2.8 or brand new 6.3.3?
Also, if you still reproduce this, could you attach the file so we can try to
reproduce this?
Of course, think about sanitizing it (see
https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 103229] Area fill toolbar control not supporting patterns

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103229

--- Comment #6 from Gerhard Weydt  ---
Created attachment 155458
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155458=edit
discrepancy between toolbar and sidebar

Attachmnent "discrepancy between toolbar and sidebar" shows correct fill type
in sidebar and wrong one in toolbar, while pattern is shown correctly in both.
Screenshot was taken in a German environment, "Muster" means "pattern", the
rest should be easily understandable.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128238] LibreOffice Calc - Regex Find/Replace causes massive memory usage

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128238

m.a.riosv  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #4 from m.a.riosv  ---
Happens also with:
Version: 6.4.0.0.alpha0+ (x64)
Build ID: 758516295e5f69393bd78bb4af6e7214d48ece0b
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; 
Locale: es-ES (es_ES); UI-Language: en-US Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128530] (Korean Version Only) Two icons have reversed each other.

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128530

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #2 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, when launching Calc, I
don't reproduce this.
Could you give a minimal step by step process to reproduce this?
Perhaps I just missed it.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 103229] Area fill toolbar control not supporting patterns

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103229

Gerhard Weydt  changed:

   What|Removed |Added

 CC||gerhard.we...@t-online.de

--- Comment #5 from Gerhard Weydt  ---
The bug is still there in
Version: 6.3.2.2 (x64)
Build-ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded

Moreover, it applies also to Draw and Impress (didn't test Calc).
And there is a second, connected bug: after choosing "pattern" in the
sidebar/notebook bar, the toolbar field shows the same pattern, but the
preceding field still says "bitmap". I'll add a screenshot.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128503] Incorrect results from regular expresions from COUNTIF (but not from REGEX)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128503

--- Comment #8 from David Lynch  ---
This makes no diffrence I always have wrong results:

no thread   

50  0   =COUNTIF(A1,".0")   wrong   50  =REGEX(A1,".0") right
0   1   =COUNTIF(A2,".0")   wrong   #N/A=REGEX(A2,".0") right
a0  0   =COUNTIF(A3,".0")   wrong   a0  =REGEX(A3,".0") right
57  0   =COUNTIF(A4,".7")   wrong   57  =REGEX(A4,".7") right
57  0   =COUNTIF(A5,".7")   wrong   57  =REGEX(A5,".7") right
7   0   =COUNTIF(A6,".7")   right   #N/A=REGEX(A6,".7") right
a7  0   =COUNTIF(A7,".7")   wrong   a7  =REGEX(A7,".7") right
7a  1   =COUNTIF(A8,".a")   right   7a  =REGEX(A8,".a") right
ab  1   =COUNTIF(A9,".b")   right   ab  =REGEX(A9,".b") right
50  0   =COUNTIF(A10,"5.")  wrong   50  =REGEX(A10,"5.")   
right
50  0   =COUNTIF(A11,"5.")  wrong   50  =REGEX(A11,"5.")   
right
a0  1   =COUNTIF(A12,"a.")  right   a0  =REGEX(A12,"a.")   
right

threaded
50  0   =COUNTIF(A1,".0")   wrong   50  =REGEX(A1,".0") right
0   1   =COUNTIF(A2,".0")   wrong   #N/A=REGEX(A2,".0") right
a0  0   =COUNTIF(A3,".0")   wrong   a0  =REGEX(A3,".0") right
57  0   =COUNTIF(A4,".7")   wrong   57  =REGEX(A4,".7") right
57  0   =COUNTIF(A5,".7")   wrong   57  =REGEX(A5,".7") right
7   0   =COUNTIF(A6,".7")   right   #N/A=REGEX(A6,".7") right
a7  0   =COUNTIF(A7,".7")   wrong   a7  =REGEX(A7,".7") right
7a  1   =COUNTIF(A8,".a")   right   7a  =REGEX(A8,".a") right
ab  1   =COUNTIF(A9,".b")   right   ab  =REGEX(A9,".b") right
50  0   =COUNTIF(A10,"5.")  wrong   50  =REGEX(A10,"5.")   
right
50  0   =COUNTIF(A11,"5.")  wrong   50  =REGEX(A11,"5.")   
right
a0  1   =COUNTIF(A12,"a.")  right   a0  =REGEX(A12,"a.")   
right

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128503] Incorrect results from regular expresions from COUNTIF (but not from REGEX)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128503

--- Comment #7 from Oliver Brinzing  ---
(In reply to m.a.riosv from comment #6)
> Please test playing with 'Calc: threaded'  Menu/Tools/Options/LIbreOffice
> calc/Calculate.

this seems to make no difference, i have always correct results

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128541] Direct Formatting plus Style Formatting affects results from Find & Replace with Including Styles

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128541

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #2 from m.a.riosv  ---
Looks like a duplicate of
https://bugs.documentfoundation.org/show_bug.cgi?id=128064

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128503] Incorrect results from regular expresions from COUNTIF (but not from REGEX)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128503

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #6 from m.a.riosv  ---
Please test playing with 'Calc: threaded'  Menu/Tools/Options/LIbreOffice
calc/Calculate.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128260] DOCX import issues from 3-S Thesis Template, most likely sections->Page Styles conversion filter fails somehow!

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128260

--- Comment #6 from e...@sheer.us ---
Thankyou to Mike for particularly helpful comments, especially agree that the
issue is not the automatically-inserted blank-pages, which indeed come out
correctly when requested explicitly!.

Confirm this issue still exists in LO 6.4a1, as per new attachment.

Infact, PDF page 19 shows the first difference -- "xix" does not come out, a
right-hand-side page-number,  yet that on Page 17 and before were okay.

Then, similarly, PDF page 23 [page "1"] and all such beyond with footer "Right
Page Footer" do not show any page numbers.  There is clearly some issue with
importing the left/right footers correctly within the auto-generated
page-styles!.   I observe that manually re-insert the page numbers in all the
(messy!) autogenerated styles after import from DOCX, seems to work, they
appear to just be "imported as blank"...

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128541] Direct Formatting plus Style Formatting affects results from Find & Replace with Including Styles

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128541

Oliver Brinzing  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||oliver.brinz...@gmx.de

--- Comment #1 from Oliver Brinzing  ---
Thank you for reporting the bug. 

Please attach a sample document, as this makes it easier for us to verify the
bug. 
(Please note that the attachment will be public, remove any sensitive
information before attaching it. 
See
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the requested document is provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128512] LO Base incorrectly remembers position and size of its windows

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128512

Shad Sterling  changed:

   What|Removed |Added

 CC||m...@shadsterling.com

--- Comment #3 from Shad Sterling  ---
@Christian Lehmann, have you confirmed that on Linux LibreOffice Writer doesn't
use last-closed window positions from other LibreOffice apps (not just Base)? 
On macOS they're not separate apps, but Writer uses the last-closed window
position of whatever document type was closed last.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128260] DOCX import issues from 3-S Thesis Template, most likely sections->Page Styles conversion filter fails somehow!

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128260

--- Comment #5 from e...@sheer.us ---
Created attachment 155457
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155457=edit
3-S Template, exported with automatic blank pages, by LO 6.4a1 Win7 32bit.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 108598] FORMATTING Row height is changed or not changed wrongly

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108598

stefan_lange...@t-online.de  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 108598] FORMATTING Row height is changed or not changed wrongly

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108598

--- Comment #7 from stefan_lange...@t-online.de  
---
I have tested with
Version: 6.3.3.2 (x64)
Build-ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: CL

I cannot reproduce cases 1 + 2, means row is not changed neither when cell
contents is changed nor at Undo. 

The behavior of case 3 still exists but in a modified form. 

Thererfore I will close the bug as RESOLVED-WORKSFORME and report a new bug for
the behavior how row height is handled when cell contents is wrapped.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128436] Range for Name forced to lowercase

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128436

--- Comment #3 from Jonny Grant  ---
(In reply to Oliver Brinzing from comment #1)
> (In reply to Jonny Grant from comment #0)
> > If if Insert->Chart by selecting B2:B5 you need to manually enter the
> > chart's "Range for Name" needs to be manually typed, and when it is - Calc
> > changes it to lowercase, and removes any spaces.
> 
> confirming, but IMHO you need to enter an absolute cell address for "Range
> for Name" and not string title

Ah, I wonder why it works and shows the nice heading with a space and not
forced to lower case if including the column heading?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 126966] Sidebar: color selection too small for finger usage

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126966

--- Comment #11 from Commit Notification 
 ---
Marco Cecchetti committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/467429fe1dd0a7ab62e90234d71c3809ab270159

tdf#126966: Use larger buttons for the colours in the sidebar on iOS - 2

It will be available in 6.4.0.

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

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128051] PRINTING: Epson XP-455 prints images but not text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128051

Julien Nabet  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

--- Comment #7 from Julien Nabet  ---
Thank you for your feedback, let's put this one to WFM then.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128051] PRINTING: Epson XP-455 prints images but not text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128051

Doug Bainbridge  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 108800] [META] Print related issues

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108800
Bug 108800 depends on bug 128051, which changed state.

Bug 128051 Summary: PRINTING: Epson XP-455 prints images but not text
https://bugs.documentfoundation.org/show_bug.cgi?id=128051

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128051] PRINTING: Epson XP-455 prints images but not text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128051

--- Comment #6 from Doug Bainbridge  ---
I went through the FirstSteps which showed nothing wrong. By chance I was
testing with a file that had some coloured text in it - the coloured text
printed OK but the black text failed to print. Although I had previously done
maintenance checks on the printer and it had passed these I went back and did
repeated cleaning of print head, nozzle check, alignment, etc. and eventually
the printer produced normal looking text.

So SOLVED and I apologise for taking up your time!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 127648] LO on Linux crashes when accessing opend/locked File on SAMBA network share

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127648

--- Comment #17 from Jan  ---
Created attachment 155456
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155456=edit
strace with debug build

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128541] New: Direct Formatting plus Style Formatting affects results from Find & Replace with Including Styles

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128541

Bug ID: 128541
   Summary: Direct Formatting plus Style Formatting affects
results from Find & Replace with Including Styles
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: alex@gmail.com

Description:
In a document with:
- some text formatted with Strong Emphasis Character Style
- some text formatted with Bold (Direct Formatting)
- and some other text with Strong Emphasis Character Style + Bold (Direct
Formatting)
when using Find & Replace to search for Bold formatting, all texts with Bold
direct formatting are found (ok). However, when checking the Including Style
option, only the texts with only one of the formatting are found (Strong
Emphasis Character Style OR Bold (Direct Formatting), but not the text with
both formatting). The text with both Strong Emphasis Character Style formatting
and Bold (Direct Formatting) is not found contrary to what one would expect.

Steps to Reproduce:
1. Edit a text with the three formatting combinations described above: a)
Strong Emphasis Character Style, b) Bold (Direct Formatting), c) both Strong
Emphasis Character Style + Bold (Direct Formatting)
2. Open Find & Replace and search for bold formatted text, with or without the
Including Style option checked

Actual Results:
With Including Style checked, the text with both formatting is not found.

Expected Results:
Checking the Including Style option should find all three combinations of
formatting.


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 108497] Converting OpenType Font Variation instances before printing and exporting to PDF or EPUB

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108497

--- Comment #21 from Volga  ---
If HarfBuzz implement this feature it's possible to fix this bug.
https://github.com/harfbuzz/harfbuzz/issues/1558

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128540] EPUB tool: some Error and Warning discovered after conversion with a validator

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128540

--- Comment #1 from f.carbon...@libero.it ---
Created attachment 155455
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155455=edit
The warning and error that I discovered

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128540] New: EPUB tool: some Error and Warning discovered after conversion with a validator

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128540

Bug ID: 128540
   Summary: EPUB tool: some Error and Warning discovered after
conversion with a validator
   Product: LibreOffice
   Version: 3.3.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: f.carbon...@libero.it

Description:
Hi. I converted a Writer document in EPUB with the incorporated tool. After
convertion I verified the .epub di pagina EPUB-Checker (last version of this
tool) and It discovered some Error and Warning that I list below:

-- Error RSC-005
-- Error OPF-012
-- Warning RSC-017
-- Error CSS-001



Actual Results:
Create an .epub with Writer then use a validation program to check for
problems.

Expected Results:
At this point, you should see the same errors that I did.


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 55410] automatically fill in the default user's name into tools->options->user data

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=55410

--- Comment #18 from Mike Kaganski  ---
See https://git.libreoffice.org/core/+/f154f63cb662f02415d5cb0051011bdb5d0d523c

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128539] LO63: Tips of the Day do not lead to l10'd help but to en-US help pages

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128539

--- Comment #2 from himajin100...@gmail.com ---
https://opengrok.libreoffice.org/xref/core/cui/source/dialogs/tipofthedaydlg.cxx?r=07bde589#90
https://opengrok.libreoffice.org/xref/core/cui/inc/tipoftheday.hrc?r=7fef6c0f#155

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128375] CRASH: Closing LibreOffice after cutting content from document

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128375

Michael Stahl (CIB)  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |michael.st...@cib.de
   |desktop.org |

--- Comment #8 from Michael Stahl (CIB)  ---
see https://gerrit.libreoffice.org/#/c/81911/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 126785] All libreoffice programs are duplicating the inputs

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126785

Michael Weghorn  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #37 from Michael Weghorn  ---
(In reply to Victor Silva from comment #36)
> Michael I did some talking at #kde and the folks over there commented the
> issue might be on the KF5 VCL plugin.

Yes, if there's something on LibreOffice side, that must be in the kf5 plugin.
However, without knowing when the issue happens and without the possibility to
reproduce it, it's hard to impossible to analyse and do anything about it.

If you can find out more about this (e.g. what steps you need to do on your
other computer to make the issue occur there as well), that might help. At
least for myself, I unfortunately feel unable to do anything about it at the
moment...

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 104142] Hard to pick a line with an image in its background because of "grab hand" cursor

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104142

--- Comment #13 from s.p.he...@gmx.net ---
I can confirm, that this bug is still present on:

Version: 6.3.2.2
Build ID: 1:6.3.2-0ubuntu0.18.04.1~lo1

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 122218] After Update to 6.1.4 on macOS fonts are blurred on retina display (xcode 10)

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122218

--- Comment #88 from Maciej Tarmas  ---
(In reply to Olivier Croquette from comment #87)
> I hope that the latest and
> greatest version gets fixed soon.

It won't. Nobody at The Document Foundation gives a crap about the Mac port of
Libre Office.

This bug was reported almost a year ago. As I understand it, the fix is to
build the binaries with a newer version of Xcode, but it seems that the devs
can't be bothered with stuff like that.

Sometimes I wish OpenOffice was never forked and stayed with Oracle. They're
doing a great job with VirtualBox on the Mac. Sigh.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 127648] LO on Linux crashes when accessing opend/locked File on SAMBA network share

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127648

--- Comment #16 from Stephan Bergmann  ---
(In reply to Jan from comment #15)
> Created attachment 155452 [details]
> gdb output of nBytesToRead and nrc

  (gdb) print nrc
  $2 = 4294967283

is clearly bogus.  Maybe an strace log helps pinpoint what exactly is going
wrong (otherwise, I'll need to prepare a patch that logs the relevant places in
the code, and which you would need to include in your LO build):  With strace
installed on your machine, please run

  instdir/program/soffice --strace

and reproduce the issue.  This should leave a (large) strace.log file in the
current working dir, which you please attach here.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128538] Restart in safe mode: Open containig folder doesn't work and Show user profile gets a error message

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128538

charlie.it  changed:

   What|Removed |Added

 CC||casa...@email.it

--- Comment #1 from charlie.it  ---
Created attachment 155454
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155454=edit
Error message

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128539] LO63: Tips of the Day do not lead to l10'd help but to en-US help pages

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128539

Martin Srebotnjak  changed:

   What|Removed |Added

 CC||olivier.hallot@libreoffice.
   ||org

--- Comment #1 from Martin Srebotnjak  ---
BTW, using LO6322 with sl-SI langpack on macOS.
sl-SI localized help page should open.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128539] New: LO63: Tips of the Day do not lead to l10'd help but to en-US help pages

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128539

Bug ID: 128539
   Summary: LO63: Tips of the Day do not lead to l10'd help but to
en-US help pages
   Product: LibreOffice
   Version: 6.3.0.4 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mi...@filmsi.net

Description:
The Tip of the Day additional info link sometimes leads to LO help page.
But:
- it does not lead to the version's help page but to old help (i.e. to 6.2
instead to 6.3 help pages for LO63);
- it leads to online help and not to installed help, if available (it opens
internet connection even if you have local and even localized help already
installed on your computer;
- it leads to en-US pages and the links are hard-coded, so no way to open a
localized help page for a localized tip of the day.

Is this feature really ready for prime time use to be enabled for localized
builds?

Steps to Reproduce:
1. Open LO with Tip-of-the-Day enabled.
2. Example: localized tip for "Tools > Detective > Mark invalid data" includes
the additional info link to en-US help page:
https://help.libreoffice.org/6.2/en-US/text/scalc/01/06030800.html
3. Open the link  ...

Actual Results:
You get an out-of-date, unlocalized & online (and not offline) help page.

Expected Results:
Up-to-date, localized & offline (if available) help page.


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 90921] FOOTNOTES: Allow to place footnotes at the bottom of the text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90921

V Stuart Foote  changed:

   What|Removed |Added

 Status|REOPENED|UNCONFIRMED
 CC||heiko.tietze@documentfounda
   ||tion.org,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval
 Ever confirmed|1   |0

--- Comment #24 from V Stuart Foote  ---

In reply to adaw2 from comment #22)
> The latest alleged solution is still a failure:
> (1) The attachment did not resolve the problem. Note the gap between text
> and footnotes on the first page, compared to the lack of gap between text
> and footnotes on the second page.

That is exactly the correct formatting--the reflink for each footnote _must_
appear on the page where the footnote is added to the bottom of the page. The
blank space _will_ expand or contract page to page depending on the size of the
footnote for the reflink appearing on the page! Subsequent Paragraph content
holding reflink(s) is free to move to the following page to allow the preceding
footnote to grow.

 (The problem only appears to be *somewhat*
> addressed, by coincidence, due to the position and spacing of the footnotes;
> see #2.) 

No coincidence.

> (2) The attachment was formatted differently; notice the blank line between
> footnotes in my document which is not present in the alleged solution. Once
> you correct the footnote formatting in the alleged solution, the problem is
> exacerbated and the document looks like mine.
> 

No, attachment 155413 was prepared is with 'Default' page and paragraph style
formatting with just paragraph line spacing set to double, as that seemed to be
the requested format.

> Again, the section method is not a real solution--it only appears to be in
> certain situations.

It is not an appearance of solution--it is the only solution that is viable
(i.e. does not require major refactoring) page layout.

@adaw2 (not even the OP) has been unable to prepare legitimate, reproducible
example(s) screenshot(s) showing what formatting they seek, and what exactly is
perceived as lacking by using an appropriately formatted section to hold
paragraph and reflink'd footnotes.

My UX input remains as in comment 6 as this WFM, and should otherwise be a WF.

=> Unconfirmed and back for UX-advise.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 90921] FOOTNOTES: Allow to place footnotes at the bottom of the text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90921

--- Comment #23 from ad...@email.com ---
I thought of another way of making my point (from a different angle): Try to
create a multiple-paged document using the section method in which the
footnotes on the first page actually *need* to be moved up (due to a large gap
between text and footnotes) and therefore *are* moved up.

All of the proposed solutions so far did not *need* to have the footnotes on
the first page moved up (due to formatting errors). Thus, even if the section
method had not been used, the footnotes in such cases would have *seemed* to be
immediately below the text anyway due to the position of footnote links, etc.
(The last page is a different story, obviously.)

If you are successful, your document will have multiple pages, and the bottom
of the footnotes on the first page will be higher than the bottom margin of the
page, due to the footnotes actually being moved *up*. I suspect you will not be
able to create such a document, because the section method only moves the
footnotes up on the last page.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128538] New: Restart in safe mode: Open containig folder doesn't work and Show user profile gets a error message

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128538

Bug ID: 128538
   Summary: Restart in safe mode: Open containig folder doesn't
work and Show user profile gets a error message
   Product: LibreOffice
   Version: 6.2.8.2 release
  Hardware: x86-64 (AMD64)
OS: Mac OS X (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: casa...@email.it

Description:
Using "Restart in safe mode", the next dialog box displays "Archive user
profile". The command works, a .zip file is created, but the next "Open
containig folder" option does not work.

In addition, the "Show user profile command gets an error message:
"(com.sun.star.lang.IllegalArgumentException) {{{Message ="
XSystemShellExecute.execute, cannot process  ", Context =
(com.sun.star.uno.XInterface) @ 0}}, ArgumentPosition = (short) 0} "

Steps to Reproduce:
1.Restart Libre Office in safe mode
2.Choose Advanced > Archive user profile
3.Choose Open containing folder
4.Choose Show user profile

Actual Results:
3. nothing
4. error message

Expected Results:
3. show folder
4. show user profile


Reproducible: Always


User Profile Reset: Yes



Additional Info:
In o.s. windows all works.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 90921] FOOTNOTES: Allow to place footnotes at the bottom of the text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90921

ad...@email.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 Ever confirmed|0   |1

--- Comment #22 from ad...@email.com ---
The latest alleged solution is still a failure:
(1) The attachment did not resolve the problem. Note the gap between text and
footnotes on the first page, compared to the lack of gap between text and
footnotes on the second page. (The problem only appears to be *somewhat*
addressed, by coincidence, due to the position and spacing of the footnotes;
see #2.) 
(2) The attachment was formatted differently; notice the blank line between
footnotes in my document which is not present in the alleged solution. Once you
correct the footnote formatting in the alleged solution, the problem is
exacerbated and the document looks like mine.

Again, the section method is not a real solution--it only appears to be in
certain situations.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 103164] [META] Footnote and Endnote bugs and enhancements

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103164
Bug 103164 depends on bug 90921, which changed state.

Bug 90921 Summary: FOOTNOTES: Allow to place footnotes at the bottom of the text
https://bugs.documentfoundation.org/show_bug.cgi?id=90921

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128441] Crash in: mergedlo.dll

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128441

--- Comment #9 from Julien Nabet  ---
There are 2 bugs here:
1) Opengl part which crashes with LO
Xisco: Should we blacklist nvidia with device 0x2182 + Win10 ?
(with always the same question, perhaps a next driver version will fix it or
Opengl part will be fixed in LO, how to know we may remove this blacklist issue
then?)

2) the wrong rendering when OpenGl is disabled
I think a new bugtracker should be opened about this.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128051] PRINTING: Epson XP-455 prints images but not text

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128051

--- Comment #5 from Julien Nabet  ---
Thank you Doug for your feedback, there's still
https://wiki.documentfoundation.org/QA/FirstSteps to test.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128408] Impress Master Slide issue

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128408

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #5 from Julien Nabet  ---
Thank you for your feedback, let's put this one to WFM then.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124986] FILEOPEN DOCX: "text:variable-set" field has trailing quotation marks in "office:string-value"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124986

--- Comment #9 from Oliver Brinzing  ---
Created attachment 155453
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155453=edit
demo with and without trailing/leading spaces

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128537] New: Fatal Error with accidental CMD + ² key combination

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128537

Bug ID: 128537
   Summary: Fatal Error with accidental CMD + ² key combination
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: x86 (IA32)
OS: Mac OS X (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: glucos...@protonmail.com

Description:
I get a fatal error "Caught Unknown Exception: Aborting!" when accidentally
pressing CMD and ² keys.

More explanation: I'm using a classic PC keyboard with ISO layout. "²" key is
just above the tab key. I'm running macOS. Many times I want to use the CMD/Win
+ TAB key combination to switch to another app. Sometimes I press ² instead of
TAB. When doing this while using LibreOffice (tried only in Writer and Impress,
not other), it results in an instant fatal error. After that, document recovery
works as expected.

Steps to Reproduce:
1.Open LibreOffice (any document or just the launcher
2.Push CMD/Win key in combination with "²" key (situated just above the tab key
on a ISO layout keybard)

Actual Results:
"Fatal error - Caught Unknown Exception: Aborting!" then the app closes itself.

Expected Results:
Nothing I guess


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.3.2.2
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
Threads CPU : 8; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128523] clear per user icon cache (holding icons for SVG and at scaled UI) at least once during an upgrade installation

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128523

V Stuart Foote  changed:

   What|Removed |Added

Summary|remove old icon themes on   |clear per user icon cache
   |Windows during installation |(holding icons for SVG and
   |to fix blacked-out ugly |at scaled UI) at least once
   |icons   |during an upgrade
   ||installation

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128536] Libreoffice Calc 6.3.2.2 fails opening xlsx files

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128536

Oliver Brinzing  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||oliver.brinz...@gmx.de
 Ever confirmed|0   |1

--- Comment #1 from Oliver Brinzing  ---
Thank you for reporting the bug. 

To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

If the problem exists, please attach a sample document, as this makes it easier
for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive
information before attaching it. 
See
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the requested document is provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128523] remove old icon themes on Windows during installation to fix blacked-out ugly icons

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128523

--- Comment #2 from Mike Kaganski  ---
FTR:LibreOffice auto-restarts on the first start after an upgrade.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128408] Impress Master Slide issue

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128408

--- Comment #4 from ambrish dhaka  ---
Installed Ubuntu 19.10 which has LibreOffice 6.3.2.2 and so far the problem
seems to have not occured. I presume that I have been able to resolve the
issue. Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128469] PARAGRAPH STYLE DIALOG: "Reset" and "Standard" buttons: confusing names

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128469

--- Comment #4 from John  ---
Well, to be honest I regret about my idea to remove the "Reset" button. It
works in symmetry with "Apply" button - and therefore, to preserve the
consistency, it should be preserved. 

However, the names are not perfect. I would rather suggest to think about the
better names - and nothing more.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128536] New: Libreoffice Calc 6.3.2.2 fails opening xlsx files

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128536

Bug ID: 128536
   Summary: Libreoffice Calc 6.3.2.2 fails opening xlsx files
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: bing...@gmail.com

Description:
Libreoffice calc 6.3.2.2 Clear Linux has a problem opening xlsx files. It tells
that the files are corrupt and must be repaired. repair does not succeed.
If I open the same file in a kvm Debian 10 environment with Libreoffice 6.1.5.2
it can be opened normal. I tested with more xlsx files with the same result. 

Actual Results:
tells that the files are corrupt and must be repaired, but shows no filename

Expected Results:
Open the File


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 127648] LO on Linux crashes when accessing opend/locked File on SAMBA network share

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127648

Jan  changed:

   What|Removed |Added

 Attachment #155436|0   |1
is obsolete||

--- Comment #15 from Jan  ---
Created attachment 155452
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155452=edit
gdb output of nBytesToRead and nrc

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128535] Updater offers incorrect new version

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128535

--- Comment #1 from dbonham+bugzi...@gmail.com ---
Created attachment 155451
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155451=edit
Check for Updates window

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124986] FILEOPEN DOCX: "text:variable-set" field has trailing quotation marks in "office:string-value"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124986

--- Comment #8 from Oliver Brinzing  ---
Created attachment 155450
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155450=edit
DomainMapper_Impl.PNG

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124986] FILEOPEN DOCX: "text:variable-set" field has trailing quotation marks in "office:string-value"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124986

Oliver Brinzing  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

--- Comment #7 from Oliver Brinzing  ---
i think, i found the problem in "DomainMapper_Impl.cxx", will try to fix

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 41360] FORMATTING Problem with fontsize in style when expressed in percentage

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=41360

--- Comment #20 from Paolo Benvenuto  ---
still present in version 6.3.2.2 (ubuntu 18.04 via ppa)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128535] New: Updater offers incorrect new version

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128535

Bug ID: 128535
   Summary: Updater offers incorrect new version
   Product: LibreOffice
   Version: 6.3.1.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dbonham+bugzi...@gmail.com

Description:
If I check for updates and a new version is available, I am only offered a
slightly newer release... not the correct most current version available. For
example, if I am running v6.3.1.2, the updater offers me 6.3.2 even though
6.3.3 is available. The updater should always offer the most current release,
not a step in between.

This can cause a user to download the slightly newer release and install it,
then be immediately told there is a newer release.

Steps to Reproduce:
1. Select Help -> Check for Updates from within a LO program
2. Note current version installed & offered version for download
3. Visit website and note the actual newest release available.

Actual Results:
Offered one minor version newer than currently installed.

Expected Results:
I should be offered the most current release.


Reproducible: Always


User Profile Reset: Yes



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128523] remove old icon themes on Windows during installation to fix blacked-out ugly icons

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128523

V Stuart Foote  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||cl...@documentfoundation.or
   ||g,
   ||heiko.tietze@documentfounda
   ||tion.org,
   ||mikekagan...@hotmail.com,
   ||qui...@gmail.com,
   ||tima...@gmail.com,
   ||vstuart.fo...@utsa.edu
 Status|UNCONFIRMED |NEW
 OS|Windows (All)   |All
   Severity|normal  |enhancement
   Keywords||needsDevEval

--- Comment #1 from V Stuart Foote  ---
While it might be possible to craft a Windows build MSI custom action to remove
the icon cache for installation of a single user system, seems unlikely to work
on a multi-user install--so probably could not be done in the installation
packaging.

And, kind of seems like it would be useful cross platform--assure changed (or
corrected as for OP) icon themes are parsed/rebuilt at least at a major release
install. 

Without forcing users to fully reset profile, could per user clearing of the
icon cache be forced for an initial launch of a new major release? Perhaps
using the same ooSetupLastVersion test used for the What's new infobar (bug
69042).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124986] FILEOPEN DOCX: "text:variable-set" field has trailing quotation marks in "office:string-value"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124986

Oliver Brinzing  changed:

   What|Removed |Added

   Keywords||bibisected, bisected

--- Comment #6 from Oliver Brinzing  ---
this seems to have started with:

https://gerrit.libreoffice.org/plugins/gitiles/core/+/4d5ce76d894d2335b551f8c2b29437e2049894f0

commit  4d5ce76d894d2335b551f8c2b29437e2049894f0[log]
author  Jean-Sebastien Bevilacqua 
Thu Feb 16 10:16:50 2017 +0100
committer   Miklos Vajna   
Tue Mar 28 07:05:30 2017 +
tree152ac7f5dabfc7f7cb1df385dac8ed63a3afa1d1
parent  b3549aacabffad3c4c66d901938d59e4789eef22 [diff]

tdf#105975 Add Set field parsing (docx) in LibreOffice Writer

Introduction


In MSWord, you can create a variable with `SET` field and then
reference it later in a formula. When you save your file as `docx`,
this `SET` field is registered in you file. In its current state,
LibreOffice can't parse the `SET` field in `docx` file.

Context of this fix
---

This fix is entirely located in the `DomainMapper_Impl.cxx` file
because it's where the parsing is done.

How this fix works
--

First, we add `SET` support by adding it to the `aFields[]` variable.
Next, to handle the `SET` constant, we add a condition (swith case) in
`DomainMapper_Impl::CloseFieldCommand()` to call `handleFieldSet`.
Finally, `handleFieldSet` works like `handleFieldAsk` with small
differences.

Note


I have renamed `lcl_ExctractAskVariableAndHint` to
`lcl_ExctractVariableAndHint` because this function is used for both `ASK` and
`SET` fields.

Change-Id: I2bf948e26e8506ac151d1d0bc8556721bbe0392b
Reviewed-on: https://gerrit.libreoffice.org/34333
Tested-by: Jenkins 
Reviewed-by: Miklos Vajna 

/cygdrive/d/sources/bibisect/bibisect-win32-5.4
$ git bisect good
c20d8357a586fc4616a4352d0f39117492da0bc0 is the first bad commit
commit c20d8357a586fc4616a4352d0f39117492da0bc0
Author: Norbert Thiebaud 
Date:   Tue Mar 28 00:50:59 2017 -0700
source sha:4d5ce76d894d2335b551f8c2b29437e2049894f0
source sha:4d5ce76d894d2335b551f8c2b29437e2049894f0

:04 04 bf860248cec2620dfeeda7b75779bc849fd54475
cfc1f8b4ae15560de2dabfeb868973df7a2c303a M  instdir

/cygdrive/d/sources/bibisect/bibisect-win32-5.4
$ git bisect log
# bad: [5b9390199c309eb0f061804e45031da85989a8ef] source
sha:534fd9aacd3eea10070a3ee88fc654eb9791aa24
# good: [633bfe84509c1953415e5dd0f564098a16890131] source
sha:4136757b4e51c4e6f7cb4132c95538a7f831ef2c
git bisect start 'master' 'oldest'
# good: [fb6ad3d5a416ac122c263bb29a8d1b90a0750432] source
sha:055c8cc676921176e2b9df76bd0e09bacab1d80b
git bisect good fb6ad3d5a416ac122c263bb29a8d1b90a0750432
# bad: [e4ec339892e747e2dfd56126e74a90411fced190] source
sha:a917902c48f21d04039da86048c5c36555137d7e
git bisect bad e4ec339892e747e2dfd56126e74a90411fced190
# good: [374673a7108c11f5a2d352f522597414093decbc] source
sha:dfdf256d828e29b430e41d1b82899680664259f5
git bisect good 374673a7108c11f5a2d352f522597414093decbc
# bad: [a868c68624daf768ba20fb4f4acf5d0fef543edd] source
sha:8005237d71a75fe9bcfd860111bb0fe1fa6064d6
git bisect bad a868c68624daf768ba20fb4f4acf5d0fef543edd
# bad: [6ce293ed08bec72f7ae1a219f81c35a85b5b84ed] source
sha:0e261a6908c2521a9967069095239eeb02810b8c
git bisect bad 6ce293ed08bec72f7ae1a219f81c35a85b5b84ed
# bad: [5757440d796f875b1392b645825b1f9ea08e56f8] source
sha:2f2296d2c328fa8bf3671f8d3591d3a2bdf2752f
git bisect bad 5757440d796f875b1392b645825b1f9ea08e56f8
# bad: [cab5d9b720db39f4b1f8701695cf34195b17cb55] source
sha:799824565b783ec0b2323bd609a0e69a70182ac1
git bisect bad cab5d9b720db39f4b1f8701695cf34195b17cb55
# good: [ac97714fa1fd6359420656e6e0591954e4038576] source
sha:2fc5ef74c5200bdb82cdbbc812d7ac05a9a489dd
git bisect good ac97714fa1fd6359420656e6e0591954e4038576
# bad: [741fb160c0ac3408f5b02b0c4f98119573ecfc17] source
sha:0cb5435dd35674b6e55e22922a0819d2a755fc10
git bisect bad 741fb160c0ac3408f5b02b0c4f98119573ecfc17
# bad: [8bef32fdac27565c8ddd500424359c5654be6368] source
sha:65aa28cc1c8a90865c3a9ea379722730c40ecb53
git bisect bad 8bef32fdac27565c8ddd500424359c5654be6368
# bad: [b1140d3e2c8263b05bb80c3f5bfabe6901037754] source
sha:157cb703888f4187c2c6709b13ebf9f779580fe2
git bisect bad b1140d3e2c8263b05bb80c3f5bfabe6901037754
# bad: [c20d8357a586fc4616a4352d0f39117492da0bc0] source
sha:4d5ce76d894d2335b551f8c2b29437e2049894f0
git bisect bad c20d8357a586fc4616a4352d0f39117492da0bc0
# good: [3482471497813663a77c7baa97558d0b8b0dd933] source
sha:b3549aacabffad3c4c66d901938d59e4789eef22
git bisect good 3482471497813663a77c7baa97558d0b8b0dd933
# first bad commit: [c20d8357a586fc4616a4352d0f39117492da0bc0] source
sha:4d5ce76d894d2335b551f8c2b29437e2049894f0

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list

[Libreoffice-bugs] [Bug 128469] PARAGRAPH STYLE DIALOG: "Reset" and "Standard" buttons: confusing names

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128469

Regina Henschel  changed:

   What|Removed |Added

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

--- Comment #3 from Regina Henschel  ---
The "Standard" button is currently the only way to remove a setting in the
style, so that the inherit setting is used. It must stay until a different
solution is implemented and tested.

It should be possible, to cancel and reopen the dialog instead of the "Reset"
button. But I don't know whether it works. The problem is, that touching a
field will produce an entry of that value to the style, but when? Is there no
entry if "Reset" is used? Is there no entry if "Cancel" is used?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128528] FORMATTING, EDITING Date format not handled correctly

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128528

pent...@gmail.com changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
   Assignee|libreoffice-b...@lists.free |pent...@gmail.com
   |desktop.org |
 Ever confirmed|1   |0

--- Comment #2 from pent...@gmail.com ---
Created attachment 155448
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155448=edit
sample spreadsheet demonstrating the error

I have created a sample spreadsheet with the current state that shows the
error. I will check the settings right away.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 124986] FILEOPEN DOCX: "text:variable-set" field has trailing quotation marks in "office:string-value"

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124986

--- Comment #5 from Oliver Brinzing  ---
Created attachment 155447
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155447=edit
demo with and without trailing space

the problem seems to be the trailing space

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128534] New: Crash if i click the print button on Writer toolbar

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128534

Bug ID: 128534
   Summary: Crash if i click the print button on Writer toolbar
   Product: LibreOffice
   Version: 6.4.0.0.alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gulsah.k...@collabora.com

Description:
Crash if i click the print button on Writer toolbar. There is a backtrace log
at the attachment after the crash.

Steps to Reproduce:
1.Open Writer
2. Click the Print button.

Actual Results:
We should see the print dialog

Expected Results:
Crashed


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128533] New: EDITING, FORMATTING: Accept any decimal separator

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128533

Bug ID: 128533
   Summary: EDITING, FORMATTING: Accept any decimal separator
   Product: LibreOffice
   Version: 6.3.2.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: anton-tsygane...@yandex.ru

Description:
I have no stable habit to use a specific decimal separator, so I may put both
dots and commas. But LibreOffice forces me to use one that is specified by my
locale settings, and it is very annoying when I type "5.12" (when decimal
separator is comma) and LO thinks that it is text, not a number.

Steps to Reproduce:
1. Check your locale settings to know your decimal separator
2. Insert some numbers in cells, putting the other separator
3. Try to find a sum of the cells
4. Find a free cell and put there a formula =1.1+0,3

Actual Results:
the sum appears to be 0. The formula gives "#NAME?" error.

Expected Results:
LO finds the actual sum, and the result of the formula is 1.4 (or 1,4,
depending on the settings).


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.3.2.2
Build ID: 6.3.2-2
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3; 
Locale: ru-RU (en_US.UTF-8); UI-Language: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 128534] Crash if i click the print button on Writer toolbar

2019-11-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128534

--- Comment #1 from Gülşah Köse  ---
Created attachment 155446
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155446=edit
Backtrace log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

  1   2   >