[Libreoffice-bugs] [Bug 117095] Writer takes at least 5 minutes to open a one-page .odt file - with 131.000 bookmark lines

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117095

--- Comment #6 from Yomo Como  ---
(In reply to Yomo Como from comment #4)
> (In reply to Timur from comment #2)
> > Repro all the way from OO to master. Also slow with MS Word. 
> > But I'm not in favor of confirming a bug. Looks like WontFix to me.
> > Because this is specific ODT with large content.xml that has multiple:
> > 
> > How was this created?
> 
> I used LibreOffice 5.1 on Ubuntu to create it and saved as an rtf file.
> After getting nagged about saving it in ODT, I resaved it in ODT.

I also sometimes copied some text from the internet and pasted into the file.

-- 
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 117095] Writer takes at least 5 minutes to open a one-page .odt file - with 131.000 bookmark lines

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117095

--- Comment #5 from Yomo Como  ---
(In reply to Timur from comment #3)
> Created attachment 141482 [details]
> The same file cleaned
> 
> The same file cleaned of 131.000 bookmark lines.

Thanks for cleaning it up, Timur. I'm not sure why it was so big with just a
page of text. Abiword is also struggling opening up the original file.

-- 
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 117095] Writer takes at least 5 minutes to open a one-page .odt file - with 131.000 bookmark lines

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117095

--- Comment #4 from Yomo Como  ---
(In reply to Timur from comment #2)
> Repro all the way from OO to master. Also slow with MS Word. 
> But I'm not in favor of confirming a bug. Looks like WontFix to me.
> Because this is specific ODT with large content.xml that has multiple:
> 
> How was this created?

I used LibreOffice 5.1 on Ubuntu to create it and saved as an rtf file. After
getting nagged about saving it in ODT, I resaved it in ODT.

-- 
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 42505] EDITING: Inserting a frame around a table is not undoable - Undo is reset

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42505

--- Comment #8 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 72101] UNDO incomplete when contents of a cell with formula is deleted

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72101

--- Comment #6 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 81512] Undo: Writer fails to restore Table Name

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81512

--- Comment #7 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 107319] Clear direct formatting doesnt work with frame styled elements

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107319

--- Comment #2 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 76259] EDITING: Undo: Tables vs numbered list

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76259

--- Comment #6 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 107162] ods to xls conversion trouble

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107162

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 79404] EDITING: Undo after AutoCorrect removes the whole cell content instead of reverting just the autocorrect changes

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=79404

--- Comment #16 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 89323] undo option after entering values in table is not working in Libreoffice Impress

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89323

--- Comment #9 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 68472] UNDO incomplete: alignment not restored in cells after UNDO cells merge

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=68472

--- Comment #7 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 107317] Undo label shows 'Insert $1'

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107317

--- Comment #4 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 100298] Style names come and go (are blanked out / white) in Styles and Formatting window (OSX ≤ 10.10)

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100298

--- Comment #24 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 89611] TOC: Undos lost after modifying index/table of contents

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89611

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

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 117150] New: calc notebook toolbar menubar issues

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117150

Bug ID: 117150
   Summary: calc notebook toolbar menubar issues
   Product: LibreOffice
   Version: 6.0.3.2 release
  Hardware: All
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: perie_...@hotmail.com

issue 1: under notebookbar settings, menubar is missing. 

issue 2: Once in notebookbar settings, everything is defaulted to groupedbar
compact. Users cannot changed to contextual or to other selections. 

Both of these issues are present in windows 10 and 7

-- 
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 117149] New: Crash in: BigPtrArray::Index2Block(unsigned long) const

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117149

Bug ID: 117149
   Summary: Crash in: BigPtrArray::Index2Block(unsigned long)
const
   Product: LibreOffice
   Version: 6.0.3.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: fiendi...@gmail.com

This bug was filed from the crash reporting server and is
br-1b57d12b-1051-4a92-9ffe-00d44f7f4e81.
=

Crash happened while undoing (ctrl-z) some edits in a change-tracked docx.

-- 
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 117126] Compress image breaks crop

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117126

Luke  changed:

   What|Removed |Added

   Keywords|regression  |
  Component|LibreOffice |Impress
Version|6.0.3.2 release |4.1.0.4 release

--- Comment #5 from Luke  ---
Repo in 6.1 master and Version: 4.1.0.1


Removed the "regression" keyword. Also, I fail to see how this is not a dupe of
bug 83734. Steps to reproduce are identical, just different components.

-- 
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 117147] latest update won't open the DOCX documents, crashes

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117147

--- Comment #2 from rcdor...@gmail.com ---
Created attachment 141530
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141530=edit
A 1 page punch (to do) list

crashreport.libreoffice.org/stats/crash_details/b6262822-9547-458b-b20f-b55184394fe0

Document That failed to open In Libreoffice attached.
It appears all DOCX documents do not open But crash LO After about 15 to 20
seconds.
Gonna downgrade to a previous version and see if the behaviors the same.

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

--- Comment #18 from V Stuart Foote  ---
(In reply to V Stuart Foote from comment #17)
> (In reply to zahra from comment #16)
> > 
> > but i am sure that i asked this problem in nvda user maling list and someone
> > confirms this problem in libreoffice 6.0!

> 
> No, I follow NVDA user and dev ML and of course LibreOffice, and this was
> not reproduced that I recall. 

I would not call the responses by one NVDA user in
https://nvda.groups.io/g/nvda/topic/12628487#35965 an energetic or well scoped
confirmation...

Rather, with Windows 10 Pro 64-bit en-US (ver 1709) with NVDA 2017.2, 2017.3,
2018.1.1. in Object navigation mode (NVDA key + F7) from the number pad the
Numpad 4 & 6 give clear by word break sounding, the numpad 1 & 3 give clear by
character sounding. And the numpad 7 & 9 give by line sounding--though in the
About -> Help dialog, the multiple lines of the description are read--with
audible breaks at word boundries. In other words it sounds correctly.

So this really is unconfirmed and works for me.

=-=-=

As you seem stuck working on Windows XP, here are links to the EOL final
releases:

5.2.7.2 --
http://downloadarchive.documentfoundation.org/libreoffice/old/5.2.7.2/win/x86/

5.3.7.2 --
http://downloadarchive.documentfoundation.org/libreoffice/old/5.3.7.2/win/x86/

-- 
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 82009] PIVOTTABLE: Black color on fields of Pivot Table Layout window (Mac OS X only)

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82009

eisa01  changed:

   What|Removed |Added

 Blocks||42082


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=42082
[Bug 42082] [META] Make LibreOffice shine and glow on OS X
-- 
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 42082] [META] Make LibreOffice shine and glow on OS X

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42082

eisa01  changed:

   What|Removed |Added

 Depends on||82009


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=82009
[Bug 82009] PIVOTTABLE: Black color on fields of Pivot Table Layout window (Mac
OS X only)
-- 
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 108025] Kerning problem for glyph with applied OpenType Feature

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108025

LibreTraining  changed:

   What|Removed |Added

 CC||libretraining.tutorials@gma
   ||il.com

--- Comment #5 from LibreTraining  ---
Created attachment 141529
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141529=edit
Insert Special Character as Workaround - Does Not Work

I assumed directly inserting the character should work as a workaround because
that would still be the same font.
It did not work.

This appears to point to a larger OpenType kerning issue.

The attached image shows tests in LibreOffice and other applications.
The alternate A character has been inserted directly.
Some applications do the kerning right, some do it wrong.

LibreOffice 6.0.3.2 - Wrong
Word 2016 - Wrong
InDesign 2018 - Right
Scribus 1.5.4 SVN - Wrong
GIMP 2.8 - Right
Inkscape 9.92.2 - Right
FontCreator - Right

FontCreator does not show a specific kerning pair(s) for that alternate
character.
It appears it is coming from the class.

It appears that GIMP, Inkscape, and InDesign read this properly and kern the
characters properly.

Should I enter this in the tracker as a separate issue?

-- 
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 117131] Double Line Formating Has Changed After Updating To v5.4.6.2

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117131

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INSUFFICIENTDATA

--- Comment #3 from V Stuart Foote  ---
(In reply to rayisfun from comment #2)
> Sadly, I have now uninstalled LibreOffice because I can't rely on it to work
> reliably. I'm now using Apache OpenOffice which opens my document correctly.
> I'll try another version of LibreOffice sometime in the future if/when this
> bug is fixed.

OK, good luck then. We'll be 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 117148] FIREBIRD allows no edit for table with unique index, but no primary key, contrary to message

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117148

--- Comment #2 from Drew Jensen  ---
Just now using the 6.0 dev build the GUI controls work, or in this case do not
work, similarly with either hsql or firebird sdbc. 

The GUI controls do not update tables without a primary key.

If IIRC the need for a unique key is for the API (ie. singleselectqueryanalyser
service ) and I would suppose that would be true for hsql or firebird. I didn't
try that with a macro just now against either engine to check. SQL insert
statement in the SQL window works with either engine and I was AR enough to do
that just now and in both.

So the GUI stuff, looks to me, to be working as expected but maybe problems
lower down?

-- 
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 86399] find and replace dialogue - composed characters do not display properly - sometimes hidden completely

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86399

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:4.5.0 target:4.4.3   |target:4.5.0 target:4.4.3
   |target:4.3.7|target:4.3.7 target:6.1.0

-- 
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 86399] find and replace dialogue - composed characters do not display properly - sometimes hidden completely

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86399

--- Comment #17 from Commit Notification 
 ---
Khaled Hosny committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=63a4ecc3881596a448d47f564c722ad944ff7e67

tdf#86399 Correctly set cluster start for RTL runs

It will be available in 6.1.0.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

V Stuart Foote  changed:

   What|Removed |Added

 CC||quen...@nvaccess.org

--- Comment #17 from V Stuart Foote  ---
(In reply to zahra from comment #16)
> 
> but i am sure that i asked this problem in nvda user maling list and someone
> confirms this problem in libreoffice 6.0!
> why invalid?
> its a new bug which introducing harfbuzz made for nvda users!
> it does not depend on my windows, i am sure that i used remote control
> program and tested in the system of one person who has windows ten and
> observed this issue!
> i tested with libreoffice 5.3.0.3 remotely, but on that time, i did not know
> about harfbuzz and how to disable it!
> so, my report is not specific for one windows version and specific version
> of nvda!
> its one of the bugs that introducing harfbuzz made and i did not find any
> solution for resolving this issue except disabling harfbuzz as i mentioned
> that today i learned from your comment!
> why khaled removed the option for disabling harfbuzz in 5.4?
> even if libreoffice 6.0, did not support xp, i never used it, because of not
> possible to read dialogs and messages in screen review!

No, I follow NVDA user and dev ML and of course LibreOffice, and this was not
reproduced that I recall. And as you never provided a WinDbg stack trace or
link to Libreoffice crashreporter dumps for LibreOffice, nor NVDA verbose
logging catching the "crash" it is undocumented and not confirmed.

Invalid because even if it were confirmed--it has not been--it could not be
fixed as *both* software projects have moved on.  NVDA 2017.3 and 2018.1.1 or
next 2018.2 on Windows systems with GPU driver support do not have this issue--
and conflating in the HarfBuzz source is not reasonable.

It is equally likely the issue is with NVDA and the Symphony/IAccessible2
module which has some annoying locale detection language change behavior--that
HarfBuzz handling could have complicated, but with out logging its mute.

Otherwise please be aware that at the 5.4 release with a complete transition to
HarfBuzz based rendering cross platform--the legacy GDI/DirectWrite rendering
on Windows (the so called "Old" layout engine) was completely removed from the
code base. It is gone, and will not be brought back.

Making use of HarfBuzz, Windows builds of 5.4, 6.0 and current master have two
rendering modes--legacy GDI for the "Default" rendering (by CPU or Hardware)
and Direct3D DirectWrite with OpenGL rendering. Moving forward we will be
further reducing the use of legacy GDI handling again moving Direct3D
DirectWrite forward (or possibly implementing FreeType) for text rendering.

Sorry not to be cruel, but that is reality--up to you to move on.

@Quintin, do you have any perspective from the NVAccess side?

-- 
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 117125] Libreoffice stores same png multiple times

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117125

Telesto  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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


[Libreoffice-bugs] [Bug 117131] Double Line Formating Has Changed After Updating To v5.4.6.2

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117131

--- Comment #2 from rayis...@hotmail.com ---
Thanks for your help. I tried your suggestion of proportional spacing but at
200% the spacing remains unaltered. A lower percentage reduces the spacing. I
found a fix by changing the line spacing to "Leading" at 0.70cm. The document
reverts back to 456 pages as normal.

I have used LibreOffice for many years. This document was created in it and for
over a year, up until v5.4.4, worked perfectly. A friend, who is helping me
with this document, is also unclear why this problem began after the v5.4.6.2
update. If, as you say, the font is at fault then why did this problem not
occur with v5.4.4? I don't understand why this document loads correctly with
456 pages and then a couple of seconds later shrinks down to 362 pages. For
some reason LibreOffice is re-formatting the document after it has loaded
correctly.

Sadly, I have now uninstalled LibreOffice because I can't rely on it to work
reliably. I'm now using Apache OpenOffice which opens my document correctly.
I'll try another version of LibreOffice sometime in the future if/when this bug
is 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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

--- Comment #16 from zahra  ---
(In reply to V Stuart Foote from comment #15)
> @Zahra, sorry. But going to go ahead and close this invalid.
> 
> When you eventually move off Windows XP to a current Windows platform, or
> adopt a Linux OS and can use Orca you'll be better served.
> 
> For now, LibreOffice 5.4 and 6.0 with NVDA 2017.3, or 2018.2 with windows 10
> correctly sound all elements of the dialogs exposed to screen review. We
> have no issue with the words being run together with either OpenGL rendering
> or default GDI rendering being run together.
> 
> If 5.3.7.2 and NVDA 2017.3 work well for you (having disabled Harfbuzz based
> rendering) great. 5.4 builds are the end of the line for you as support for
> Windows XP, and Vista have been dropped at 6.0.
>  
> There is no going back from the LibreOffice projects perspective, and as you
> know NVAccess and the NVDA project have ended support for Windows XP at
> 2017.3 release.

but i am sure that i asked this problem in nvda user maling list and someone
confirms this problem in libreoffice 6.0!
why invalid?
its a new bug which introducing harfbuzz made for nvda users!
it does not depend on my windows, i am sure that i used remote control program
and tested in the system of one person who has windows ten and observed this
issue!
i tested with libreoffice 5.3.0.3 remotely, but on that time, i did not know
about harfbuzz and how to disable it!
so, my report is not specific for one windows version and specific version of
nvda!
its one of the bugs that introducing harfbuzz made and i did not find any
solution for resolving this issue except disabling harfbuzz as i mentioned that
today i learned from your comment!
why khaled removed the option for disabling harfbuzz in 5.4?
even if libreoffice 6.0, did not support xp, i never used it, because of not
possible to read dialogs and messages in screen review!

-- 
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 97313] Freezes using NVDA screen reader when opening a file by using control+o or in the file menu

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97313

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #24 from V Stuart Foote  ---
Closing this out as Wont Fix. 

This issue lacks reliable STR with other NVDA users unable to reproduce--we
have never been able to review a LibreOffice stack trace/crash report or an
NVDA verbose log.

OPs Windows XP system configuration does not permit testing with current dev
versions and the LibreOffice and NVDA builds involved are EOL.

OP is advised to migrate to supported OS and Assistive technology tools that
stand some chance of providing functional a11y

-- 
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 60251] [META] ACCESSIBILITY: Tracking Windows OS accessibility and AT issues

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=60251
Bug 60251 depends on bug 97313, which changed state.

Bug 97313 Summary: Freezes using NVDA screen reader when opening a file by 
using control+o or in the file menu
https://bugs.documentfoundation.org/show_bug.cgi?id=97313

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

--- Comment #16 from Gerhard Weydt  ---
(In reply to Julien Nabet from comment #14)
> (In reply to Gerhard Weydt from comment #13)
> ...
> I wasn't talking about LO but Firebird version.
> Last master sources of LO use Firebird 3.0.0 whereas current Firebird
> version is 3.0.3
> The problem is to be able to build Firebird 3.0.3 in LO master sources for
> every env: Linux, Windows and MacOS.

As I said, the use of multiple columns is already described in the manual for
Firebird 2.5, so I don't think it probable that installing Firebird 3.0.3
instead of 3.0.0 can solve the problem. It is much more probable that the
reason must be sought within LibO's connection and handling of Firebird.

-- 
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 60251] [META] ACCESSIBILITY: Tracking Windows OS accessibility and AT issues

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=60251
Bug 60251 depends on bug 108582, which changed state.

Bug 108582 Summary: using nvda screen reader activating screen review in 
libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one 
combine word!
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

V Stuart Foote  changed:

   What|Removed |Added

   Keywords|implementationError |
 Status|UNCONFIRMED |RESOLVED
 CC||vstuart.fo...@utsa.edu
   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=89 |
   |870 |
 Resolution|--- |INVALID

--- Comment #15 from V Stuart Foote  ---
@Zahra, sorry. But going to go ahead and close this invalid.

When you eventually move off Windows XP to a current Windows platform, or adopt
a Linux OS and can use Orca you'll be better served.

For now, LibreOffice 5.4 and 6.0 with NVDA 2017.3, or 2018.2 with windows 10
correctly sound all elements of the dialogs exposed to screen review. We have
no issue with the words being run together with either OpenGL rendering or
default GDI rendering being run together.

If 5.3.7.2 and NVDA 2017.3 work well for you (having disabled Harfbuzz based
rendering) great. 5.4 builds are the end of the line for you as support for
Windows XP, and Vista have been dropped at 6.0.

There is no going back from the LibreOffice projects perspective, and as you
know NVAccess and the NVDA project have ended support for Windows XP at 2017.3
release.

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

--- Comment #15 from Gerhard Weydt  ---
referring to comment 10:
I created a new bug 117048 for the problem that t is not possible to edit data
if the table has only a unique key, contrary to the statement on save that
exactly this is allowed.

-- 
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 117148] FIREBIRD allows no edit for table with unique index, but no primary key, contrary to message

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117148

Gerhard Weydt  changed:

   What|Removed |Added

Version|5.3.7.2 release |unspecified

-- 
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 117148] FIREBIRD allows no edit for table with unique index, but no primary key, contrary to message

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117148

--- Comment #1 from Gerhard Weydt  ---
Created attachment 141528
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141528=edit
TablkeOnlyUniqueIndex

-- 
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 117148] New: FIREBIRD allows no edit for table with unique index, but no primary key, contrary to message

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117148

Bug ID: 117148
   Summary: FIREBIRD allows no edit for table with unique index,
but no primary key, contrary to message
   Product: LibreOffice
   Version: 5.3.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gerhard.we...@t-online.de

When you create a table in Base with Firebird database and save it without
having created a primary key, you get the following dialog:

  No primary key

  A unique index or primary key is required for data record identification in
this database.
  You can only enter data into this table when one of these two structural
conditions has been met.

  Should a primary key be created now?

But, following the alternative stated and creating a unique index only leaves
the table not editable. Only if a primary key is added, it becomes editable.

Steps to reproduce (or open attachment TableOnlyUniqueIndex):
1. create a new database document with Firebird database engine
2. create a table using Design View, with some columns
3. save the table; you will get the message shown above
4. reject the creation of a primary key by answering: No
5. choose Tools -> Index design or its symbol
6. create a unique index for the first two columns and save it
7. close the index and table dialogs
8. save the database document
9. open the table for editing

Result: the table is not editable
Expected result: the table should be editable, as stated explicitly in the
message shown above.

It doesn't help to close the document and to open it gain, the situation
remains unchanged.

To show that editability really depends from a primary key:
10. open the table definition for editing
11. create a new column or select one of the columns not used for the unique
index
12: right-click the header of the row describing this column and choose
"Primary Key"
13. save the table definition

After that the table can be edited.

Remark: for HSQLDB primary keys were always mandatory, maybe the same test
applies now to firebird. But for HSQLDB there is no message that you can use a
unique index instead!

This issue is connected with bug 117092, saying (despite its title, because the
fact was only discovered after the bug had been created) that it is not
possible to create a primary key with more than one column.
In the present state one would have to create
1. a unique index with the columns needed
2. a primary key with one column
where one index could be sufficient.

tested with:
Version: 6.1.0.0.alpha0+
Build ID: 9c4eaa7b81a40d97fe49b85272b40bfeaaf44f86
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-04-16_03:31:36
Locale: de-DE (de_DE); Calc: group

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

--- Comment #14 from Julien Nabet  ---
(In reply to Gerhard Weydt from comment #13)
> ...
> Julien: if you do not want to create a new bug report, I will do it, but I
> will be waiting some time, in case Lionel sends a comment.

I wasn't talking about LO but Firebird version.
Last master sources of LO use Firebird 3.0.0 whereas current Firebird version
is 3.0.3
The problem is to be able to build Firebird 3.0.3 in LO master sources for
every env: Linux, Windows and MacOS.

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

--- Comment #13 from Gerhard Weydt  ---
I used the latest version available at the time of download, probably April
17th.

Version: 6.1.0.0.alpha0+
Build ID: 9c4eaa7b81a40d97fe49b85272b40bfeaaf44f86
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-04-16_03:31:36
Locale: de-DE (de_DE); Calc: group

Julien: if you do not want to create a new bug report, I will do it, but I will
be waiting some time, in case Lionel sends a comment.

-- 
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 105584] [META] Calc image bugs and enhancements

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105584
Bug 105584 depends on bug 42705, which changed state.

Bug 42705 Summary: Graphics Anchored to Cell Do Not Move With Data When Sorted, 
'Protect Position' Set or Not, 'Link' or Not
https://bugs.documentfoundation.org/show_bug.cgi?id=42705

   What|Removed |Added

 Status|REOPENED|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 42705] Graphics Anchored to Cell Do Not Move With Data When Sorted, ' Protect Position' Set or Not, 'Link' or Not

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42705

u2nBz  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #24 from u2nBz  ---
EDIT:

Just checked further down that bug page (way long) and find the fix is pushed
out to 6.1.

Only finding 6.0.3 currently available so can not verify. However, trusting
this will be resolved in the 6.1 release, marking so. If still present in 6.1
though, "I'll be back."

-- 
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 117045] When ccache's cache limit is removed autogen print it' s less than 5GB

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117045

Jean-Baptiste Faure  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||jbfa...@libreoffice.org
 Ever confirmed|0   |1

--- Comment #1 from Jean-Baptiste Faure  ---
Confirmed. I get the following warning message:
* WARNING : ccache's cache size is less than 1GB using it is
counter-productive: auto-ccache detection disabled

Status set to NEW.

Best regards. JBF

-- 
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 105584] [META] Calc image bugs and enhancements

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105584
Bug 105584 depends on bug 42705, which changed state.

Bug 42705 Summary: Graphics Anchored to Cell Do Not Move With Data When Sorted, 
'Protect Position' Set or Not, 'Link' or Not
https://bugs.documentfoundation.org/show_bug.cgi?id=42705

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

-- 
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 42705] Graphics Anchored to Cell Do Not Move With Data When Sorted, ' Protect Position' Set or Not, 'Link' or Not

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42705

u2nBz  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

--- Comment #23 from u2nBz  ---
@Regina Henschel, @Samuel Mehrbrodt (CIB), and @ Xisco Faulí;

Please note this bug:

 - Is NOT a duplicate of 98931 (which it predates anyway)

 - Is still present in the latest release, 5.3.6.1

 - Still needs to be fixed.

Before making any changes here, please download the example Calc spreadsheet
created by @d.r...@freenet.de and do a manual sort to see that this bug is
still present. And it still has nothing to do with bug 98931.

-- 
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 117147] latest update won't open the DOCX documents, crashes

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117147

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #1 from Julien Nabet  ---
Would it be possible you attach a document so we can give a try?
Of course, remove any confidential/private part from it since it'll be
automatically made public.

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

Julien Nabet  changed:

   What|Removed |Added

 CC||lio...@mamane.lu

--- Comment #12 from Julien Nabet  ---
(In reply to Gerhard Weydt from comment #11)
> In reply to comment #9 by Julien:
> ...
> I suggest you create a new bug that Firebird does not allow primary keys
> with more than one column, in contrast to the documentation and also to
> HSQLDB. This bug here could perhaps be referenced, and a comment should be
> added that this is no migration issue, but an issue of Firebird
> implementation in Base.
> ...

I know very few Firebird process and perhaps it's already fixed in the current
version.

Lionel: thought you might be interested in this one or have some thoughts here,
so I put you in cc

-- 
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 117127] error when reading the value of a variable in the IDE

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117127

--- Comment #2 from emilio  ---

sorry, the name of the procedure is "Sub AnadirFilaTablaRF()"



I also report another error, if I declare the "LeyTConcepto()" array, (1409
elements), exceptions occur. To solve it, I have to declare the array in two
parts (LeyTConceptotemporal1(),  and LeyTConceptotemporal2()). 

unexperienced exceptions occur and the values ​​contained in the matrix are
false/error, This occurs when declaring the matrix with the 1409 elements.

-- 
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 117092] Migration to Firebird fails for a simple table

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117092

--- Comment #11 from Gerhard Weydt  ---
In reply to comment #9 by Julien:
According to the Firebird documentation for version 2.5 (!) setting a primary
key with more than one column is definitely possible. And the generated syntax
is also correct.
I suggest you create a new bug that Firebird does not allow primary keys with
more than one column, in contrast to the documentation and also to HSQLDB. This
bug here could perhaps be referenced, and a comment should be added that this
is no migration issue, but an issue of Firebird implementation in Base.
I think that's better than renaming this bug, because one has to read 8
comments before one gets to the point.

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

--- Comment #14 from Buovjaga  ---
(In reply to zahra from comment #13)
> can someone please confirm this bug?

I tried again, but I could only make it read the "Version" line, if I moved the
mouse over it. No other lines were read.
For the crash recovery, mouse hovering made it read the text.
With my Truly Ergonomic keyboard, numpad only exists using a modifier key. So I
cannot "turn numlock off" and use the keys because then they are just normal
keys (some numbers and letters).

Previously I had tried to reproduce on another machine, which did have a
numpad.

-- 
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 117147] New: latest update won't open the DOCX documents, crashes

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117147

Bug ID: 117147
   Summary: latest update won't open the DOCX documents, crashes
   Product: LibreOffice
   Version: 6.0.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rcdor...@gmail.com

Just downloaded (04/21/18 11:32 AM) version 6.0.3.2 64-bit.
Before it took about 20 seconds to open 1 page DOCX ()
now it won't open it all and crashes!
useless!
Might as well stay with decrepit Microsoft Office 2016.

-- 
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 117137] FILESAVE: DOCX: file cannot be opened in MSO / numbering lost in LO

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117137

--- Comment #5 from Justin L  ---
confirmed that reverting the identified commit resolves the problem.  
https://gerrit.libreoffice.org/53271 tdf#117137: Revert "DOCX import: don't try
to set grab-gag props as UNO props"

-- 
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 76260] FILEOPEN: extremely slow loading .docx with lots of footnotes

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=76260

--- Comment #38 from rcdor...@gmail.com ---
Just upgraded (04/21/18 11:32am) to 6.0.3.2 64-bit and now nothing works
anymore!
Before it took Up to 20 seconds to open a Single page DOCX File.(!!!)
Now nothing happens anymore and it just crashes.
Useless!

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

--- Comment #13 from zahra  ---
can someone please confirm this bug?
its very annoying for nvda screen reader users, when they read dialogs and
messages with screen review.
why my bug not be new?
i even found the cause of bug and found the solution by the patch of khaled and
comment of stuart and solved it in 5.3.4 as i said!
just see dialogs and messages of libreoffice in new and old TextLayoutEngine to
see the 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 117071] Allows choose of page size when you create a new drawing in Draw

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117071

Jean-Baptiste Faure  changed:

   What|Removed |Added

 CC||jbfa...@libreoffice.org

--- Comment #1 from Jean-Baptiste Faure  ---
If you want to change the page size of your document, you can do that with a
single click if you are use the sidebar.

A new dialog is useless for me.

Best regards. JBF

-- 
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 97313] Freezes using NVDA screen reader when opening a file by using control+o or in the file menu

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97313

zahra  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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


[Libreoffice-bugs] [Bug 97313] Freezes using NVDA screen reader when opening a file by using control+o or in the file menu

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=97313

--- Comment #23 from zahra  ---
(In reply to QA Administrators from comment #22)
> Dear Bug Submitter,
> 
> 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-20180404

hi.
i tested with many versions of libreoffice until 5.4.0 and the issue still
persists.
since i use windows xp, installing version 6.0 is not possible for me.
this issue only occur when windows dialog for open and save in libreoffice,
options, general is enabled.
if we use libreoffice dialogs, (as i tested) openning files works as normal
without crash using nvda.

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

Buovjaga  changed:

   What|Removed |Added

 Status|NEW |UNCONFIRMED
 Ever confirmed|1   |0

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

zahra  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

zahra  changed:

   What|Removed |Added

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

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

zahra  changed:

   What|Removed |Added

   Keywords|regression  |implementationError

-- 
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 117137] FILESAVE: DOCX: file cannot be opened in MSO / numbering lost in LO

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117137

Justin L  changed:

   What|Removed |Added

   Keywords||regression

-- 
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 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108582

--- Comment #12 from zahra  ---
hi again.
by the grace of God,\
finally today i found a solution for my problem.
i write the method that how to resolve problem, but unfortunately it only works
in 5.3, not 5.4 and later!
steps for screen reader users to resolve the issue of reading any message and
dialogs in libreoffice 5.3
1- open libreoffice, (i tested only with writer).
2- press alt+f12 or find the options in the tool menu and activate it.
3- under libreoffice, find advance.
4- between advance settings find expert configuration and activate it.
5- in the edit box, type TextLayoutEngine and press search button.
6- press edit and rename new to old for disabling harfbuzz!
okay, now you can read any dialog box and message using nvda screen reader with
libreoffice 5.3 without any problem!
i tested with the version 5.3.4.2and it worked perfectly.
i am very glad that today i learned expert configuration and i sincerely
appreciate Yousuf Philips, Stuart, and Khaled Hosny that made possible using
libreoffice 5.3 by adding and supporting to add one configuration in expert
configuration to desable harfbuzz!
khaled added one option for disabling and enabling harfbuzz in expert
configurations and
today reading comment of stuart taught me how to enable old engine again in
libreoffice 5.3!
https://bugs.documentfoundation.org/show_bug.cgi?id=89870#c32
but i did not understand whats the reason that this great option is removed in
5.4!
how should nvda users read dialogs in libreoffice 5.4 and later with harfbuzz
enabled?
i sincerely appreciate you again, God bless you all!

-- 
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 117125] Libreoffice stores same png multiple times

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117125

--- Comment #4 from sergio.calleg...@gmail.com ---
File was first obtained with 6.0.3.2.

Then the behavior was replicated with 6.0.4.1

1) opened file
2) opened an empty drawing
3) copied first instance of the png image and pasted to the empty drawing
4) deleted both instances of the png image from the presentation
5) saved
6) verified that both instances were gone from the odp
7) copied back instance from the drawing and adjusted the cropping
8) copied again as a second instance and adjusted the cropping here too
9) saved again
10) verified that once more the odp has two identical instances of the odp.

-- 
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 117146] Saving as .csv corrupts unicode characters

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117146

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||vstuart.fo...@utsa.edu
 Resolution|--- |NOTABUG

--- Comment #1 from V Stuart Foote  ---
The save-as export allows selection of the Character set when the "edit filter
settings" box is checked. Otherwise the CSV will be saved with the character
set  in use. Select Unicode (UTF-8) or (UTF-16).

Likewise, on import the character set encoding can be selected, and then a font
selection made in Calc for correct/prefered rendering of the Unicode glyphs.

-- 
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 117031] FILEOPEN DOCX: Table is wrongly rendered

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117031

--- Comment #12 from raal  ---
Word 2010 & Word Online - prices are not visible. I propose close the 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 117031] FILEOPEN DOCX: Table is wrongly rendered

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117031

--- Comment #11 from raal  ---
Created attachment 141527
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141527=edit
printscreen from word Online

Word Online - prices not visible

-- 
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 82009] PIVOTTABLE: Black color on fields of Pivot Table Layout window (Mac OS X only)

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=82009

--- Comment #32 from kam3...@gmail.com ---
Still present on 6.0.3.2

I made a screencast to show what happens
https://www.screencast.com/t/eQlNzhmcpcI

It's very frustrating, because clicking on the fields only sometimes partially
removes the blackout, so sometimes you can't continue.

Build ID: 8f48d515416608e3a835360314dac7e47fd0b821
CPU threads: 2; OS: Mac OS X 10.13.4; UI render: default; 
Locale: en-US (en_US.UTF-8); Calc: group

-- 
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 117031] FILEOPEN DOCX: Table is wrongly rendered

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117031

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #10 from raal  ---
Created attachment 141526
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141526=edit
printscreen from word2010

as you can see at printscreen, the prices are not visible even in word2010

-- 
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 117146] New: Saving as .csv corrupts unicode characters

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117146

Bug ID: 117146
   Summary: Saving as .csv corrupts unicode characters
   Product: LibreOffice
   Version: 6.0.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: 2nie...@gmail.com

Description:
Saving file as .csv automatically encodes it in ANSI, and does not show unicode
characters, like Č or Ė.

Steps to Reproduce:
1. Create a calc document with characters 
2. Save file as .csv
3. Open .csv in text editor

Actual Results:  
Č, Ė, and probably more unicode characters appear as "?". 

Expected Results:
obvious :)


Reproducible: Always


User Profile Reset: No



Additional Info:
Marking all hardware with Windows, however, I suspect this is standard
behaviour which would reproduce also in other operating systems.


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101
Firefox/59.0

-- 
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 117125] Libreoffice stores same png multiple times

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117125

--- Comment #3 from Telesto  ---
There is a duplicate in the attached file However, I'm not able to reproduce
this from scratch with
Version: 6.1.0.0.alpha0+
Build ID: 9c4eaa7b81a40d97fe49b85272b40bfeaaf44f86
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-04-16_03:31:36
Locale: nl-NL (nl_NL); 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 117054] When typing into a text box keyboard characters arrive on screen in wrong order

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117054

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #2 from raal  ---
I cannot reproduce with Version: 6.1.0.0.alpha0+
Build ID: b11188835d3b87cd9d2a8cdb3da204cfda5d3e6e
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; 

For the test, could you test it in Safe mode? Help/ Restart in Safe mode. Thank
you

-- 
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 117056] Date form control does not work after pdf export

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117056

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||r...@post.cz
 Ever confirmed|0   |1

--- Comment #2 from raal  ---
Hello,

Thank you for filing the bug. Please send us a sample document, as this makes
it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to
'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive
information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Thank you

-- 
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 117137] FILESAVE: DOCX: file cannot be opened in MSO / numbering lost in LO

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117137

--- Comment #4 from Jacques Guilleron  ---
OK,
Bad manip from me. I reproduce the same eror than raal after saving the file
into
LO 6.1.0.0.alpha0+ Build ID: f80029445e2b558f0d0e0a25c2c1bbcbe5254120
CPU threads: 2; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-04-13_23:07:11
Locale: fr-FR (fr_FR); Calc: CL
but not with
LO  6.1.0.0.alpha0+ Build ID: 6fc9d4a482ab50a1bf8fefb1dae2a6ded3c7e3dd
CPU threads: 2; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-01-24_04:37:19
Locale: fr-FR (fr_FR); 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 116169] Impress remote 2.3 distributed on Fdroid does not show slides on mobile

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116169

raal  changed:

   What|Removed |Added

 CC||a...@openmailbox.org

--- Comment #4 from raal  ---
*** Bug 117076 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 117076] Can't see the thumbnails on Impress Remote 2.3.0 ( from Yalp Store) through WiFi

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117076

raal  changed:

   What|Removed |Added

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

--- Comment #3 from raal  ---


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

-- 
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 117076] Can't see the thumbnails on Impress Remote 2.3.0 ( from Yalp Store) through WiFi

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117076

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||r...@post.cz
 Ever confirmed|0   |1

--- Comment #2 from raal  ---
I can confirmr. Impress remote 2.3; Android 5; wifi and bluetooth connection.

-- 
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 117145] Crop Outline does not match Crop Area

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117145

--- Comment #1 from Luke  ---
Created attachment 141525
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141525=edit
Screenshot of 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 117119] Enable experimental features by default when build is not built in release configuration

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117119

Jean-Baptiste Faure  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||jbfa...@libreoffice.org
 Resolution|--- |NOTABUG

--- Comment #2 from Jean-Baptiste Faure  ---
(In reply to V Stuart Foote from comment #1)
> This is a horrible idea. Experimental features are expected to be unstable,
> or marginally complete. Enabling them for testing is an opt in
> decision--best controlled as always from the Tools -> Options -> Advanced
> panel.
> 
> Forcing them active would just make daily TB builds unstable and really
> unsuitable for use--meaning with fewer folks testing by building or
> downloading. We would have less stability testing and fewer regressions
> picked up during dev cycle.
> 
> So IMHO, simply no.

Agreed. Closing as NotABug.

Best regards. JBF

-- 
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 117145] Crop Outline does not match Crop Area

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117145

Luke  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression

-- 
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 117145] New: Crop Outline does not match Crop Area

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117145

Bug ID: 117145
   Summary: Crop Outline does not match Crop Area
   Product: LibreOffice
   Version: 6.1.0.0.alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: lukebe...@hotmail.com

The crop outline is broken in the Writer module of recent builds of
LibreOffice.

Steps to reproduce:
1. Open a Sample document with a cropped image such as attachment 106084 
2. Right click -> Crop
3. Attempt to crop image by dragging one of the crop handles

Expected Results
1. Crop Area is inside of image

Actual Results 
1. Crop Area is outside image area


Version: 6.1.0.0.alpha0+
Build ID: 94acabe8d0cb555e76635c4bceeb48a14bd16a2b
BAD


Version: 6.1.0.0.alpha0+
Build ID: ffc49bd2fba97659919d9232ae42ca675c1aa9d0
GOOD

-- 
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 117124] Item of notebook toolbar has no KeyID.

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117124

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

-- 
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 117124] Item of notebook toolbar has no KeyID.

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117124

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #2 from raal  ---
I can confirm with Version: 6.1.0.0.alpha0+
Build ID: b11188835d3b87cd9d2a8cdb3da204cfda5d3e6e
CPU threads: 4; OS: Linux 4.4;UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time:
2018-04-20_21:52:47

-- 
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 117139] rewrite of ~/.config/libreoffice/4/user/basic/script.xlc

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117139

Jean-Baptiste Faure  changed:

   What|Removed |Added

   Hardware|All |x86-64 (AMD64)
 OS|All |Linux (All)

-- 
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 117117] Copy sheet to new file loses "Freeze Rows and Columns"

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117117

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||r...@post.cz
Version|unspecified |4.1 all versions
Summary|COPY SHEET loses some   |Copy sheet to new file
   |FORMATTING  |loses "Freeze Rows and
   ||Columns"
 Ever confirmed|0   |1
 OS|Windows (All)   |All
   Severity|enhancement |normal

--- Comment #1 from raal  ---
I can confirm with Version 4.1.0.0.alpha0+ (Build ID:
efca6f15609322f62a35619619a6d5fe5c9bd5a
and 6.1 Master

-- 
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 101957] Crash when inserting an row in Writer using the context menu (likely GTK2-related)

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101957

--- Comment #27 from David  ---
I am using Debian stable, which has versions 3.22.11 and 2.24.31 installed.  I
have not tried it without kde or gtk extensions.

-- 
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 117127] error when reading the value of a variable in the IDE

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117127

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #1 from raal  ---
Hello, how can I reproduce the bug? I doesn't see function AddFileTableRF in
the attached file.

-- 
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 117132] Setting to prevent overlap of frames, tables etc.

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117132

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||rb.hensc...@t-online.de,
   ||vstuart.fo...@utsa.edu
 Ever confirmed|0   |1

--- Comment #2 from V Stuart Foote  ---
A generalized handling of objects like MSO does for tables with tblOvelap tblPr
[1] might be nice, but then question of extending ODF to encode the objects
into the documents without corrupting the other elements.

If we can't hold / exchange the information, seems no reason to attempt add it.

=-ref-=
https://msdn.microsoft.com/en-us/library/documentformat.openxml.wordprocessing.tableproperties(v=office.15).aspx

-- 
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 117134] FILEOPEN Adjacent tables in DOCX mostly overlap

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117134

V Stuart Foote  changed:

   What|Removed |Added

 CC||vmik...@collabora.co.uk,
   ||vstuart.fo...@utsa.edu

--- Comment #4 from V Stuart Foote  ---
How should we filter import this OOXML "feature"?

Notice that export / save-as of the sample document (attachment 141508) from 
OOXML -> ODF using Word 2016 eliminates the tblOverlap. So, Microsoft does not
handle it with their ODF filters, we don't either--is it even possible? Don't
think ODF can.

-- 
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 83734] EDITING: Cropped image gets distorted when Compress Graphic is used

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83734

Luke  changed:

   What|Removed |Added

  Component|Writer  |graphics stack

-- 
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 83734] EDITING: Cropped image gets distorted when Compress Graphic is used

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83734

--- Comment #18 from Luke  ---
Created attachment 141524
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141524=edit
Impress .odp with a cropped image

I highly doubt this is a separate bug as the steps to reproduce and the results
are identical in Writer and Impress. Still reproducible in Version:
6.1.0.0.alpha0+ (x64)
Build ID: d4a01820ae094ef2d4ec2196334120600b1c9621

-- 
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 117137] FILESAVE: DOCX: file cannot be opened in MSO / numbering lost in LO

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117137

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||r...@post.cz
 Ever confirmed|0   |1

--- Comment #3 from raal  ---
I can confirm with Version: 6.1.0.0.alpha0+
Build ID: d4a01820ae094ef2d4ec2196334120600b1c9621
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; 

error in word2010: prefix not declared; Location:Part:word/numbering.xml,
Line:2, column:896

-- 
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 115690] FILESAVE: first level numbering is not displayed on MSO Word after RT

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115690

--- Comment #6 from Justin L  ---
Created attachment 141523
  --> https://bugs.documentfoundation.org/attachment.cgi?id=141523=edit
05 Orfanosentel bugRT2013.docx: .doc roundtripped by MSO2013

This actually looks more like a Microsoft bug than anything. Also, if I first
round-trip the .doc file in MSO2003/2010/2013, then LO also also round-trips it
OK as can be proven by this 2013-created .docx.

I guess it is OK to leave this bug open, but I'm going to treat it as WONTFIX
since it seems very unlikely to re-surface, probably isn't truly a regression,
and is so easily fixed by just one extra save.

-- 
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 117129] Libre office Swriter crashes when opening Microsot word doc in 97-2003 doc format

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117129

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #1 from raal  ---

Please try 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
Thank you

-- 
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 104261] VIEWING: Calc red comment indicator is changing shape

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104261

raal  changed:

   What|Removed |Added

 CC||emo_asse...@yahoo.com

--- Comment #4 from raal  ---
*** Bug 117136 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 101216] [META] Calc comment bugs and enhancements

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101216
Bug 101216 depends on bug 117136, which changed state.

Bug 117136 Summary: EDITING Comment icon not fully displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=117136

   What|Removed |Added

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

-- 
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 117136] EDITING Comment icon not fully displayed

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117136

raal  changed:

   What|Removed |Added

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

--- Comment #3 from raal  ---
Thank you, Telesto.

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

-- 
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 100061] Table cells in specific Microsoft Word document not merge without changing column width

2018-04-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100061

--- Comment #5 from Mike Kaganski  ---
(In reply to Mike Kaganski from comment #4)
> ... 2 pts ...

Sorry: it should be 2 twips.

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