[Libreoffice-bugs] [Bug 120703] Bugs found by PVS-Studio static analyzer

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120703

--- Comment #114 from Mike Kaganski  ---
V547 is essentially done.

-- 
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 120703] Bugs found by PVS-Studio static analyzer

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120703

--- Comment #113 from Commit Notification 
 ---
Mike Kaganski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/55f267856e11492ae11beadbeb553dd6717de809%5E%21

tdf#120703 PVS: remove non-functional check

It will be available in 6.2.0.

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

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

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


[Libreoffice-bugs] [Bug 120703] Bugs found by PVS-Studio static analyzer

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120703

--- Comment #112 from Commit Notification 
 ---
Mike Kaganski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/25ddf69517134305d4dffd5dc1d111fe74584fac%5E%21

tdf#120703 PVS: V555

It will be available in 6.2.0.

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

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

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


[Libreoffice-bugs] [Bug 121324] Writer 6.1 thru at least 5.4.4.2 cannot open docx files created by ver. 5.1 or MS Word

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121324

--- Comment #3 from Steven Cochran  ---
Created attachment 146534
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146534=edit
LibreOffice 5.1.0.3 test file in docx format

This docx file created in 5.1.0.3 won't open in MS Word

-- 
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 121222] Bottom table border doesn't change color until scroll (or some other action)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121222

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected
 CC||armin.le.gr...@me.com,
   ||ba...@caesar.elte.hu

--- Comment #2 from Aron Budea  ---
Bibisected to the following commit using repo bibisect-win32-6.2, I had to
clear the profile at each step for accurate results. Adding Cc: to Armin Le
Grand, please take a look.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=313392119522c21a6ecd14403d6f92c948149df7
author  Armin Le Grand   2018-10-25 10:06:05
+0200
committer   Armin Le Grand   2018-10-25 12:43:55
+0200

Reorganize FrameBorderPrimitive creation (II)

-- 
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 121292] LibreOffice Writer Deleting Formulas From Documents

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121292

david johnson  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEW |UNCONFIRMED

-- 
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 121292] LibreOffice Writer Deleting Formulas From Documents

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121292

david johnson  changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

-- 
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 121342] Access2Base Counter for OpenRecordset usage is too low

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121342

--- Comment #3 from tsultana  ---
I mentioned using CurrentDb().CloseAllRecordsets() to reset the RecordsetMax =
0 but that does not work. Since I close each Recordset the Collection is empty
so the routine exits without resetting the RecordsetMax variable. Below is the
code for the CurrentDb().CloseAllRecordsets() subroutine which exits at the If
IsNull() line.

Public Sub CloseAllRecordsets()
' Clean all recordsets for housekeeping

Dim sRecordsets() As String, i As Integer, oRecordset As Object
On Local Error Goto Exit_Sub

If IsNull(RecordsetsColl) Then Exit Sub
If RecordsetsColl.Count < 1 Then Exit Sub
For i = 1 To RecordsetsColl.Count
Set oRecordset = RecordsetsColl.Item(i)
oRecordset.mClose(False) ' Do not remove entry in collection
Next i
Set RecordsetsColl = New Collection
RecordsetMax = 0

Exit_Sub:
Exit Sub
End Sub ' CloseAllRecordsets V0.9.5

Changing the first two If statements to reset the RecordsetMax = 0 would fix
the issue but may have other side effects that I am not aware of.
If IsNull(RecordsetsColl) Then
RecordsetMax = 0
Exit Sub
End If
If RecordsetsColl.Count < 1 Then
RecordsetMax = 0
Exit Sub
End If

-- 
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 95272] Fixed line spacing works incorrectly in Impress and Draw

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=95272

--- Comment #15 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 86821] canceled actions set "document modified" flag

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86821

--- 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 103417] Mixed strings in menus (OS language shown instead of UI language)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103417

--- 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 96471] Reading documents and presentations with screen readers

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96471

--- Comment #5 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 92676] Cannot change page orientation during SELECTION print in Calc (if page A4 and not Letter, until Page style changed) or PRINT pages per sheet in Impress

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92676

--- Comment #13 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 91208] FILEOPEN Arial (Body) in pptx import causes text to wrap

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91208

--- Comment #12 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 113585] Auto Filter Columns are Treated Separately in the Attached ODS File

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113585

--- Comment #3 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 96494] Search Changes Navigation Mode

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96494

--- 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 84148] Editing conditional text field condition exposes unrelated hidden section

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84148

--- Comment #11 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 113765] PRINT Partial object are printed on other pages

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113765

--- Comment #3 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 88701] FILEOPEN: Problem with import of HTML/ MHTML files with extension XLS on Windows

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=88701

--- 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 72147] EDITING: Calc/Impress - Double clicking and dragging to select multiple words does not work

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72147

--- Comment #14 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 113313] Highlighting isn’t drawn in the background, but instead even in front of adjacent glyphs

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113313

--- Comment #12 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 47234] UI: Wrong Fonts are Displayed in Options Dialog

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47234

--- Comment #13 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 113540] Setting the alignment of a cell to "Filled" does not show an arrow on overflowing content

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113540

--- 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 71057] Missing redraw - Shadow from comments not removed (Win only)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71057

--- Comment #25 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 91349] Animated gif converted to static gif in SVG export

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91349

--- 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 113578] EDITING Clicking on a text box in a PowerPoint presentation changes text formatting to default

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113578

--- 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 102780] FILEOPEN: Hebrew characters in EMF renders as other symbols

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102780

--- Comment #5 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 106981] The Repeat feature when you select an Inserted Video for it to play in a Loop during a slideshow no longer works (64-bit only)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106981

--- Comment #11 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 121342] Access2Base Counter for OpenRecordset usage is too low

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121342

--- Comment #2 from tsultana  ---
The example code would have to be run 32768 times for the error to appear.  The
x variable is not the cause, just the OpenRecordset action.

-- 
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 121342] Access2Base Counter for OpenRecordset usage is too low

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121342

--- Comment #1 from tsultana  ---
Created attachment 146533
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146533=edit
OpenRecordset error after opening and closing 32767 Recordset objects

-- 
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 121342] New: Access2Base Counter for OpenRecordset usage is too low

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121342

Bug ID: 121342
   Summary: Access2Base Counter for OpenRecordset usage is too low
   Product: LibreOffice
   Version: 6.1.1.1 rc
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tony.sult...@pm.me

Description:
Each use of OpenRecordset increases the Integer counter RecordsetMax in
Access2Base.Database.  Once 32767 recordsets are open an error is reported with
the next OpenRecordset.  It does not matter that mClose() is used for each
OpenRecordset.

32767 may sound large but my use is a converted MS Access database used for
Monte Carlo simulations into the millions.  I am reworking the logic in many
places to use arrays or batch updates with difficulty.

The following code will error out very quickly.

Dim iRec as Object, x as Long
Set iRec = CurrentDb().OpenRecordset("table")
With iRec 
  Do While Not .EOF
x = x + 1
.MoveNext
  Loop
  .mClose
End With 



Steps to Reproduce:
1. Run the code above to get the attached error.
2.
3.

Actual Results:
Code runs until the RecordsetMax gets to 32767.  Then either 
1) run CurrentDb().CloseAllRecordsets() to reset but make sure you are not
using any open Recordsets or
2) Close all LO products and reopen Base

This problem is on Debian Linux LO 6.1.3 and Win10 LO 6.1.1

Expected Results:
Crashed of OpenRecordset with FATAL error


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Allow more Recordsets to be opened.  A counter that is Integer for RecordsetMax
is too low, perhaps changing to Long.  I do not know if the Integer limit is
carried into other tables or classes to make this practical.

The other option is to reuse OpenRecordset counters or at least provide a way
to view the RecordsetMax variable as a property call for error trapping.  As it
currently is the database cannot handle more complex uses without coding to its
deficiencies.

-- 
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 118195] FORMATTING : languages list not translated in the format cell dialog box

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118195

--- Comment #2 from Hopper  ---
[SUGGESTION]
This suggestion implies both [FORMATTING] and [LINGUISTICS] functionalities.

a. Impossible to modify the "None" option
b. There's a lack of information in the dialogue boxes concerning the functions
mentioned above.
c. An "Important!" Note is required 'in situ' (in the place of the dialogue
box.

Otherwise, it's impossible to change the dictionaries. And the problem is that
in the moment when it is needed to be changed, it seems impossible to do it
(the dialogue box "none" remains blocked without any apparent reason and/or
explanation).

It took me WEEKS to find the solution (which indeed, needed nothing to be done
but to find the proper dialogue box), since there is no problem with the
programming. However the waste of time was something to regret.

THE SOLUTION IS TO MATCH THE DESIRED DICTIONARY IN THE "Style paragraph" and
the selected dictionary for the document (F7: Spell and grammar correction)

It seems many people are suffering (or have suffered) of the same problem. I've
found issues dated since 2014 (on similar programs, such as OpenOffice).

This is very common in places where the user has to switch constantly between
more than one language dictionaries.


Example of how should the note appear in the "F7: Spell and grammar correction"
dialogue box:

"IMPORTANT!: In order to change the "none" option to any other desired
language, make sure the language of the document has been properly designated
as the designated language, in the following route:

Style> Modify style> Type of Letter> (DIALOGUE BOX) Language: [Desired
language]"

Provided that the user has downloaded the necessary dictionary (or
dictionaries).

Thank you, in advance.
Regards
HOP

-- 
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 121314] Show rows vs filter

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121314

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
I think not a bug it just does what is required, show the rows, if in MSO does
nothing then what it's their function?

-- 
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 121328] Slow startup time on SSD

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121328

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #4 from m.a.riosv  ---
I have seen this issue first time the program it's launched after installation
(not after restarr windows), usually with dev compilations.

I'm not sure and maybe only in my imagination, but a couple of things:
- Antivirus program, LibreOffice has a lot of little files, my impression it's
the AV needs to verify and register the first run of dlls.
- Net connections.

-- 
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 121336] Can not edit Cell text using Edit Bar if text contains auto-detected hyperlinks (result is different than shown in Edit Bar)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121336

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #3 from m.a.riosv  ---
The way to edit it's Menu/Inser/Hiperlink [Ctrl+K]

Not a 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 121341] choosing insert trend line causes crash

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121341

--- Comment #3 from Drew Jensen  ---
oops saved before I was done updateing

The commit effected files:
chart2/source/controller/dialogs/dlg_ObjectProperties.cxx
chart2/source/controller/inc/dlg_ObjectProperties.hxx
chart2/source/controller/main/ChartController_Insert.cxx
chart2/source/controller/main/ChartController_Properties.cxx
chart2/uiconfig/ui/attributedialog.ui
include/sfx2/tabdlg.hxx
include/vcl/weld.hxx
sd/uiconfig/simpress/ui/templatedialog.ui
sfx2/source/dialog/tabdlg.cxx
vcl/source/app/salvtables.cxx
vcl/unx/gtk3/gtk3gtkinst.cxx 

Tested with both GTK2 and GTK3, when the crash manifested, it made not
difference in behavior. 

Added developer to 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 121341] choosing insert trend line causes crash

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121341

Drew Jensen  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected
 CC||caol...@redhat.com

--- Comment #2 from Drew Jensen  ---
Bibisect reports that the anomaly arrived with commit:
8947c9b1d8cd407131fdfb6fc3c77c8532e9d2a0

author  Caolán McNamara 2018-10-18 13:00:41 +0100

Titled: weld SchAttribTabDlg

-- 
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 121318] FILEOPEN: DOC DOCX Page Formatting Bug with Compatibility Mode

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121318

Aron Budea  changed:

   What|Removed |Added

   Keywords|bibisectRequest |

--- Comment #4 from Aron Budea  ---
Scratch the final paragraph of my previous comment, that's bug 80635.

As I can see the layout change is due to floating table -> regular table
conversion. If you change 'Text wrapping' of the table in Word to None, it'll
show exactly like in Writer. It still feels like the layout is a corner case in
Word, as I'd expect it to stay stable between display and export/printing.

-- 
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 121341] choosing insert trend line causes crash

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121341

Drew Jensen  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||drewjensen.in...@gmail.com
   Keywords||bibisectRequest, regression
 OS|Windows (All)   |All
 Ever confirmed|0   |1

--- Comment #1 from Drew Jensen  ---
Confirmed with Ubuntu 18.04 and LO 6.2.1Alpha1
Also checked with 6.1.3.2 and that functioned as expected.

Marked as regresion and bibisect request. Will do so after updating the local
bibisect repository.

-- 
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 121341] New: choosing insert trend line causes crash

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121341

Bug ID: 121341
   Summary: choosing insert trend line causes crash
   Product: LibreOffice
   Version: 6.2.0.0.alpha0+
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: catbil...@gmail.com

Created attachment 146532
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146532=edit
Inserting trend line causes crash

Trying to Insert  a trend line (after selecting data in the chart) causes Calc
to crash. What I tried:

opening in safe mode
cutting and pasting data into new file
starting over with completely new data and file
restoring from backup (not sure how it is worded --- the first choice given
when trying to open a program that just crashed)

example file attached

crash report:
http://crashreport.libreoffice.org/stats/crash_details/c5f5d81f-4c57-40e1-a12c-a6688e29b28a

I don't know what more information could be useful. Please bear with me.

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


[Libreoffice-bugs] [Bug 101678] PPTX imported table renders wrong as nested table in table

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101678

--- Comment #6 from Johnny_M  ---
Still reproducible in (on Ubuntu Mate 18.04.1 liveUSB):

Version: 6.2.0.0.alpha1+
Build ID: bf4fc97131147d25b18d088023262c977f0b2787
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2018-11-10_01:52:15
Locale: en-US (C.UTF-8); UI-Language: en-US
Calc: threaded

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


[Libreoffice-bugs] [Bug 121340] New: The steps in Wizards use different header formats

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121340

Bug ID: 121340
   Summary: The steps in Wizards use different header formats
   Product: LibreOffice
   Version: 6.1.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: yakush...@gmail.com

Created attachment 146531
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146531=edit
screenshot of 5 wizards

Hi,

I have checked 5 different wizards and it appears that they have different
title formats for their steps.

"Chart Wizard" uses "Title Case" format.
"Letter Wizard" and "Agenda Wizard" use "Simple capital" title format.
"Fax Wizard" and "Address Book Data Source Wizard" use mixed title format.

Do we have the standard layout for wizards?

-- 
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 65017] FILEOPEN : Menu "File > Recent Documents" opens rtf file as a Calc document instead of in Writer

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65017

Maxim Monastirsky  changed:

   What|Removed |Added

 CC||pierre.choffar...@free.fr

--- Comment #24 from Maxim Monastirsky  ---
*** Bug 121128 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 121128] Impress opens a Draw file as a presentation file in particular conditions

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121128

Maxim Monastirsky  changed:

   What|Removed |Added

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

--- Comment #7 from Maxim Monastirsky  ---
(In reply to Pierre C from comment #4)
> No, it is not a dupe. If I select a file to open in the recent list file, I
> expect that the file will open with the correct application.
Then it's a duplicate of Bug 65017.

(In reply to raal from comment #6)
> This seems to have begun at the below commit.
> authorMaxim Monastirsky 2015-11-08 01:33:47 +0200
> commit8655fa318c1924994eb659b4bb60074c86ad70c1 (patch)
> Fix property name: ModuleName -> ModuleIdentifier
This is a bit misleading. This behavior was originally introduced as a
*feature* (at least for Writer and Calc) starting with LO 3.6 in this commit:

commit c238c19d2fed00919e02c4bc268d99ceaa73aca1
Author: Kohei Yoshida 
Date:   Wed May 30 18:33:46 2012 -0400

1) Don't pass filter name and 2) pass module name when opening file.

Then it was unintentionally broken starting with LO 4.1, because of a commit
that was cherry-picked from AOO (and obviously AOO devs didn't take into
account the other change that happened on our side in LO 3.6):

commit 8b050d1e91a6623fb2770421e564a74d6259d816
Author: Ariel Constenla-Haile 
Date:   Fri Apr 26 21:55:57 2013 +

UI Controller Factory fixes

So in my commit (which gone into LO 5.2) I only fixed the code to be at least
technically correct, and to behave the way it was designed by its original
author.

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

-- 
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 121246] Crash clicking on 'row' of a chart (with missing chart bars)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121246

Julien Nabet  changed:

   What|Removed |Added

   Keywords||haveBacktrace

-- 
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 121246] Crash clicking on 'row' of a chart (with missing chart bars)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121246

--- Comment #2 from Julien Nabet  ---
Created attachment 146530
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146530=edit
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.

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


[Libreoffice-bugs] [Bug 121209] TABLEWIZARD: Field type isn't correctly recognized for Integer and Boolean using automatic field type recognition

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121209

Julien Nabet  changed:

   What|Removed |Added

 CC|serval2...@yahoo.fr |

--- Comment #5 from Julien Nabet  ---
No idea where the type is automatically guessed, uncc myself.

-- 
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 107237] [META] Notebookbar Tabbed Implementation

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107237
Bug 107237 depends on bug 121331, which changed state.

Bug 121331 Summary: Tabbed: Wrong .uno: command in Insert and Slide Tab
https://bugs.documentfoundation.org/show_bug.cgi?id=121331

   What|Removed |Added

 Status|UNCONFIRMED |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 114077] UNO alias commands not working in notebookbar

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114077

Maxim Monastirsky  changed:

   What|Removed |Added

 CC||riz_17_...@yahoo.co.id

--- Comment #5 from Maxim Monastirsky  ---
*** Bug 121331 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 121331] Tabbed: Wrong .uno: command in Insert and Slide Tab

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121331

Maxim Monastirsky  changed:

   What|Removed |Added

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

--- Comment #1 from Maxim Monastirsky  ---
(In reply to Rizal Muttaqin from comment #0)
> Andreas Kainz (NB designer) said there's a limitation which prevent him to
> implement some "Slide" function so he used "Page" instead. Need an dev
> advice here.
The limitation in place is that those slide commands were implemented using the
command aliases feature, which was never implemented for the
sidebar/notebookbar.

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

-- 
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 121211] IMPORT: Calc range 'table definition only option selected' fails to create table

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121211

Julien Nabet  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr
   |desktop.org |

--- Comment #5 from Julien Nabet  ---
I submitted a patch on gerrit https://gerrit.libreoffice.org/#/c/63250/

-- 
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 121333] Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

Regina Henschel  changed:

   What|Removed |Added

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

--- Comment #5 from Regina Henschel  ---
The style "Default Style", which is applied to the paragraph, has the option
"Auto update" enabled. You find this option in the tab "Organize" in the edit
style dialog. You have marked not only single characters but a entire
paragraph. Therefor the character change is applied to the entire paragraph and
because of "Auto update" it does not only change the marked paragraph but the
assigned paragraph style too.

We might discuss, whether it is necessary to mark from start to end to mark an
entire paragraph or whether mark from start of paragraph to start of next
paragraph is needed.

-- 
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 34965] Make Impress slides editable during presentation

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34965

--- Comment #27 from Roland Taylor  ---
Sorry to "bump" this bug, but just wondering if anyone has taken a shot at it?

I'm not confident I'd be able to fix it so quickly, as there'd be a bit of a
learning curve involved.

But please, can someone take a look at this? I know, "someone" does not exist,
but please understand that for the average user, that response is not helpful.
If I could fix this in a timely manner, I'd pitch in and do it myself.

-- 
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 121208] TABLEWIZARD: Fields in "Column Information" too small

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121208

Julien Nabet  changed:

   What|Removed |Added

 CC|serval2...@yahoo.fr |

--- Comment #4 from Julien Nabet  ---
It seems dbaccess/source/ui/control/FieldDescControl.cxx:780 could be a start
but 
no idea how it works, uncc myself

-- 
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 121218] UI Notebookbar (all types): "Draw" tab not shown when drawing lines

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121218

--- Comment #3 from Ljiljan  ---
It works in 6.2

Version: 6.2.0.0.alpha1+
Build ID: bf4fc97131147d25b18d088023262c977f0b2787
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2018-11-10_01:52:15
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

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


[Libreoffice-bugs] [Bug 121218] UI Notebookbar (all types): "Draw" tab not shown when drawing lines

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121218

Ljiljan  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEEDINFO|RESOLVED

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


[Libreoffice-bugs] [Bug 121339] New: LibreOffice takes a mighty long time to start.

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121339

Bug ID: 121339
   Summary: LibreOffice takes a mighty long time to start.
   Product: LibreOffice
   Version: 6.1.0.3 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rolandi...@gmail.com

Description:
LibreOffice seems to hang on the splash screen for up to two minutes when
starting.

This happens on two systems since upgrading to 6.1.

Steps to Reproduce:
1. Start LibreOffice.
2.
3.

Actual Results:
The splash screen appears, the progress bar gets to about half-way, and then
you have to wait for a while (quite a while). This didn't happen before.

Expected Results:
LibreOffice starts quickly, like it used to before.


Reproducible: Always


User Profile Reset: Yes



Additional Info:

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


[Libreoffice-bugs] [Bug 121338] New: Most transitions don't work.

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121338

Bug ID: 121338
   Summary: Most transitions don't work.
   Product: LibreOffice
   Version: 6.1.0.3 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rolandi...@gmail.com

Description:
Since upgrading to 6.1 in Ubuntu 18.10, transitions no longer work, on multiple
systems.

This only occurs on Linux, as the Windows systems we use don't have this
problem.

One system is using Nvidia graphics with the proprietary driver, the other,
Intel Graphics (Sandy Bridge era). In the past, some transitions were broken on
the intel system due to the lack of support for the OpenGL extensions in use.
However, now, both systems have no transitions at all.

• Hardware acceleration is enabled on both.
• OpenGL is disabled unless you disable the blacklist, but this doesn't help.
• The problem occurs in both Plasma and Gnome, and even other environments.

Steps to Reproduce:
1. Create a presentation.
2. Add a transition.
3. Cry, because it doesn't work.

Actual Results:
No transitions play. Instead, there is a black screen or black area (when
previewing), for the duration of the transition.

Expected Results:
Play the transition.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
This is a 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 113643] Editing tables in Impress lags terribly

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113643

--- Comment #11 from E Moen  ---
Running 6.1.3.2 and the improvement is impressive! Lag is as good as gone.
Guess I'll be using the fresh branche now. Thanks a lot.

-- 
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 120115] Crash in: SfxItemSet::GetItemState

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120115

--- Comment #11 from Björn Michaelsen  ---
https://gerrit.libreoffice.org/#/c/63249/

-- 
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 108141] Link to external data sometimes results in HTTP 503

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108141

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
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 112071] [META] Linked external data issues

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112071
Bug 112071 depends on bug 108141, which changed state.

Bug 108141 Summary: Link to external data sometimes results in HTTP 503
https://bugs.documentfoundation.org/show_bug.cgi?id=108141

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 108141] Link to external data sometimes results in HTTP 503

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108141

Eike Rathke  changed:

   What|Removed |Added

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

--- Comment #3 from Eike Rathke  ---
HTTP code 503 is a server error. Anyway, can't reproduce on Linux already in
5.3.6 and later releases, seems to be server or a Windows problem or 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 121337] FileDateTime("\\nonexistent\smb\path") returns bogus result rather than throwing error

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121337

--- Comment #2 from Jim Avera  ---
In case it's relevant, I'm running Ubuntu 18.04
and package "smbfs" is versuib 2:4.7.6+dfsg~ubuntu-0ubuntu2.2

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


[Libreoffice-bugs] [Bug 121337] FileDateTime("\\nonexistent\smb\path") returns bogus result rather than throwing error

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121337

--- Comment #1 from Jim Avera  ---
Created attachment 146529
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146529=edit
FileDateTimeOnError.ods (contains a macro which demos the 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 121337] FileDateTime("\\nonexistent\smb\path") returns bogus result rather than throwing error

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121337

Jim Avera  changed:

   What|Removed |Added

 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 121337] New: FileDateTime("\\nonexistent\smb\path") returns bogus result rather than throwing error

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121337

Bug ID: 121337
   Summary: FileDateTime("\\nonexistent\smb\path") returns bogus
result rather than throwing error
   Product: LibreOffice
   Version: 6.2.0.0.alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: BASIC
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jim.av...@gmail.com

Description:
In BASIC macro code, FileDateTime("/unix/style/nonexistentfile") throws an
error as it should, which can be caught with the "on error" mechanism.

However FileDateTime("\\smb\style\nonexistentfile"), when executed on a Unix
platform at least, returns a bogus result string "01/03/-0001 00:00:00" instead
of throwing an error.

Steps to Reproduce:
1. In a BASIC macro, call FileDateTime("\\bogus\path") in the context of an "on
error" hook

(or run the macro in the attached demo spreadsheet)


Actual Results:
A bogus result string is returned. An error is not thrown.

Expected Results:
Should throw an error, or in any case behave the same way with Unix and
SMB-style paths.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.2.0.0.alpha1
Build ID: ff46ad24d1d3cbcea45895520483ed1fd4ff488b
CPU threads: 12; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: threaded

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


[Libreoffice-bugs] [Bug 121263] Calc crashes when hide multiple sheets

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121263

--- Comment #6 from Commit Notification 
 ---
Noel Grandin committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/4a514e21eda561ab1025610ea492360d01cbd52d%5E%21

tdf#121263 Calc crashes when hide multiple sheets

It will be available in 6.2.0.

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

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

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


[Libreoffice-bugs] [Bug 121263] Calc crashes when hide multiple sheets

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121263

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:6.2.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 121263] Calc crashes when hide multiple sheets

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121263

Noel Grandin  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 117700] .html to .odt conversion (headless) sets asymmetrical margins

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117700

--- Comment #7 from jonas@thiem.email ---
For what it's worth, I moved to python-docx and I'm no longer using the HTML
import since in its current shape, it just doesn't produce a very usable result
without manual editing (which simply doesn't scale)

-- 
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 121333] Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

--- Comment #4 from Thomas Krumbein  ---
Document may be corrupt.

I can confirm the behaviour (Win 10, Lo 5.3.1.2 - x64), but I do not think,
this is a LO problem.

The Document structure contains a lot of Word Templates (Paragraph and
Character) (WW_xxx) and those templates will couse strange effekts sometimes. 

So, the best way ist to redesign the document and create it completly new
without importing templates and without using "Copy" becouse in this case
sometimes the "WW_xxx" templates will be imported too!

I would say: No 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 121280] Serious crash when trying to delete a table

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121280

V Stuart Foote  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 CC||vstuart.fo...@utsa.edu
 Ever confirmed|1   |0

--- Comment #5 from V Stuart Foote  ---
>From duplicate submission 121335:

"Well, I restarted LibreOffice in safe mode from Writer and the problem didn't
append again in this safe mode. But when I restarted the soft in normal mode it
was still there So, what can I do now ? The only extension I use is
Grammalecte."

-- 
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 121335] About bug 121280

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121335

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---


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

-- 
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 121280] Serious crash when trying to delete a table

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121280

--- Comment #4 from V Stuart Foote  ---
*** Bug 121335 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 121170] Add support for Dynamic Images

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121170

--- Comment #4 from SoCu  ---
Yes, if the document created in Microsoft Excel works very well, but when it is
used in LibreOffice nothing can be done.

-- 
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 121336] Can not edit Cell text using Edit Bar if text contains auto-detected hyperlinks (result is different than shown in Edit Bar)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121336

Jim Avera  changed:

   What|Removed |Added

 Attachment #146527|0   |1
is obsolete||

--- Comment #2 from Jim Avera  ---
Created attachment 146528
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146528=edit
UneditableCellString.ods

-- 
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 113672] Wrap around table position not correct for DOC

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113672

--- Comment #4 from Luke  ---
Created attachment 146526
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146526=edit
bugdoc saved as .docx also imported incorrectly

bug 80635 only affects .DOC files. This bug affects files saved as .DOC and
.DOCX.

I went through all the example duplicate bugdocs in bug 80635, and in all of
the cases they had the table border inside of the margins, that was moved
outside on import. At a minimum, this is a different variant of that issue that
must also be considered.

-- 
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 121336] Can not edit Cell text using Edit Bar if text contains auto-detected hyperlinks (result is different than shown in Edit Bar)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121336

--- Comment #1 from Jim Avera  ---
Created attachment 146527
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146527=edit
UneditableCellString.ods

-- 
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 121336] New: Can not edit Cell text using Edit Bar if text contains auto-detected hyperlinks (result is different than shown in Edit Bar)

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121336

Bug ID: 121336
   Summary: Can not edit Cell text using Edit Bar if text contains
auto-detected hyperlinks (result is different than
shown in Edit Bar)
   Product: LibreOffice
   Version: 6.2.0.0.alpha1+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jim.av...@gmail.com

Description:
If a cell contains a string and a sub-sequence in that string is auto-detected
as a hyperlink, then subsequent attempts to edit the text appear to work in the
Edit Bar but actually result in a corrupted result.

Please see the attached demo spreadsheet ("UneditableCellString.ods")

Steps to Reproduce:
1. Type "/aaa;\\bbb\ccc;\\ddd\eee" into a cell (sans quotes)
(\\bbb\ccc and \\ddd\eee will be auto-detected as hyperlinks)
2. Click elsewhere, then re-select the cell
3. In the Edit Bar, change "bbb" to "xxx"
4. Click the green check icon

Actual Results:
The edit is corrupted: The "bbb" which was changed to "xxx" in the Edit Bar was
not actually changed, and the "xxx" ended up at the end of the entire string.

Also, copy-and-paste of the text in the Edit Bar produces the corrupted result,
not what you see in the Edit Bar.

Expected Results:
The cell text should be changed to exactly what is shown in the Edit Bar (i.e.
what the user wanted).   

Any URL auto-detects should be uh-done and re-done around edits.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.2.0.0.alpha1
Build ID: ff46ad24d1d3cbcea45895520483ed1fd4ff488b
CPU threads: 12; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: threaded

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


[Libreoffice-bugs] [Bug 121335] New: About bug 121280

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121335

Bug ID: 121335
   Summary: About bug 121280
   Product: LibreOffice
   Version: 6.0.6.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jefcomp...@yahoo.fr

Description:
Hi,
Well, I'm beginning a new report because I was perfectly unable to know how to
give you the new informations about this.
I wrote first ; " After creating a table during the tests I'm doing to learn
how to use your software, I tried to delete it using the Undo function in the
Edit menu. The software crashed, disappeared from the screen after a short
while. This happened again using the delete table icon in the table toolbar. On
the other hand everything goes well apparently when using the Delete function
of the Table menu. Thank you "
Then you answered this : " Thank you for reporting the bug. To be certain the
reported issue is not related to corruption in the user profile, could you
please reset your Libreoffice profile and re-test?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present "
Well, I restarted LibreOffice in safe mode from Writer and the problem didn't
append again in this safe mode. But when I restarted the soft in normal mode it
was still there So, what can I do now ? The only extension I use is
Grammalecte. Thank you


Steps to Reproduce:
1.Create à table
2.Try to delete it
3.

Actual Results:
Crash

Expected Results:
Delete table


Reproducible: Always


User Profile Reset: Yes



Additional Info:
[Information automatically included from LibreOffice]
Locale: fr
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

-- 
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 113672] Wrap Around Table Position Not Correct for DOC and DOCX When Table Border Outside of Margins

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113672

Luke  changed:

   What|Removed |Added

   Keywords||filter:doc, filter:docx
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=80
   ||635

-- 
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 80635] FILEOPEN: DOC file floating table spacing (margin) not imported properly

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=80635

Luke  changed:

   What|Removed |Added

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

-- 
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 113672] Wrap Around Table Position Not Correct for DOC and DOCX When Table Border Outside of Margins

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113672

Luke  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Ever confirmed|0   |1
 Status|RESOLVED|NEW

-- 
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 113672] Wrap Around Table Position Not Correct for DOC and DOCX When Table Border Outside of Margins

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113672

Luke  changed:

   What|Removed |Added

Summary|Wrap around table position  |Wrap Around Table Position
   |not correct for DOC |Not Correct for DOC and
   ||DOCX When Table Border
   ||Outside of Margins

-- 
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 121333] Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

Oliver Brinzing  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||oliver.brinz...@gmx.de
 Status|UNCONFIRMED |NEW
Version|6.1.3.1 rc  |5.4.7.2 release

--- Comment #3 from Oliver Brinzing  ---
reproducible with

Version: 5.4.7.2
Build-ID: c838ef25c16710f8838b1faec480ebba495259d0
CPU-Threads: 4; BS: Windows 6.2; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: single

as mentioned above:
Font Kallos ITC is a not installed font on the OS

and attached document has several writer compatibility switches enabled,
including "use printer metrics for document formating".

-- 
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 121334] New: Printing and pdf export shrink document

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121334

Bug ID: 121334
   Summary: Printing and pdf export shrink document
   Product: LibreOffice
   Version: 5.1.6.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Printing and PDF export
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sbr...@gardenlight.org

Description:
New documents print and export to pdf with content shrunken on page. Existing
documents created under older versions of LibreOffice print and export ok.
Changing those older documents' content in new version and saving does not
manifest the issue either. 
Resetting user profile does not fix
Changing fonts does not fix

Steps to Reproduce:
1. Create a new document
2. Select print or export to pdf
3. Result is content shrunk by about 60%

Actual Results:
Printing and pdf creation reduces content of results to about 60%

Expected Results:
Printing and pdf retains 100% scaling


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Existing documents created under older versions of Libreoffice like 4 or 5.0
can be printed and exported without shrinkage

Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial4
CPU Threads: 6; OS Version: Linux 4.15; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group

Linux Mint Sylvia
Cinnamon 64-bit

-- 
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 121333] Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

--- Comment #2 from GwenDragon  ---
Created attachment 146525
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146525=edit
Screerecording (GIF) of 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 121323] Crash dragging button after un-grouping compound group

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121323

Oliver Brinzing  changed:

   What|Removed |Added

 CC||oliver.brinz...@gmx.de

--- Comment #5 from Oliver Brinzing  ---
no repro with

Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: de-DE (de_DE); Calc: 

Linux 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 121333] Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

--- Comment #1 from GwenDragon  ---
Created attachment 146524
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146524=edit
Writer file to test the 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 121322] Paste with 'Dynamic Data Exchange' does not use DDE function but inserts file link

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121322

Oliver Brinzing  changed:

   What|Removed |Added

Version|6.2.0.0.alpha1+ Master  |5.4.7.2 release

--- Comment #2 from Oliver Brinzing  ---
already reproducible with

Version: 5.4.7.2
Build-ID: c838ef25c16710f8838b1faec480ebba495259d0
CPU-Threads: 4; BS: Windows 6.2; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: single

-- 
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 121333] New: Changing character format in a single paragraph changes all paragraphs with same paragraph format

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121333

Bug ID: 121333
   Summary: Changing character format in a single paragraph
changes all paragraphs with same paragraph format
   Product: LibreOffice
   Version: 6.1.3.1 rc
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: i...@gwendragon.de

Description:
When i select a single paragraph by doubleclick and change its character
format, all paragraphs with same are changed.

Steps to Reproduce:
1. Open standard-defekt1.odt in Writer
2. Triple-click the paragraph with text "Betreff: Meeting November 2018' to
mark it completely
3. Open context menu on selected paragraph to change font style
4. Select a different bold font f.ex. Noto Sans with style Bold and confirm
with OK


Actual Results:
Selected paragraph and all others with same format 'Standard' have changed to
Noto Sans Bold.

Expected Results:
Only the one selected paragraph change to Noto Sans Bold.


Reproducible: Always


User Profile Reset: No



Additional Info:
On Windows 10 x64 (6.1.3.2 x64) and Debian 9 x64 (6.1.3.1 RC x64, from stretch
backports)

Font Kallos ITC is a not installed font on the OS

See testcase file standard-defekt1.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 121322] Paste with 'Dynamic Data Exchange' does not use DDE function but inserts file link

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121322

Oliver Brinzing  changed:

   What|Removed |Added

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

--- Comment #1 from Oliver Brinzing  ---
confirming with 

Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: de-DE (de_DE); Calc:

-- 
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 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121210

Julien Nabet  changed:

   What|Removed |Added

 CC|serval2...@yahoo.fr |

--- Comment #13 from Julien Nabet  ---
I already tried to understand the code part and got completely lost, uncc
myself.

-- 
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 121323] Crash dragging button after un-grouping compound group

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121323

--- Comment #4 from Julien Nabet  ---
Created attachment 146523
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146523=edit
console logs + bt

On pc Debian x86-64 with master sources updated today, I could reproduce this.

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


[Libreoffice-bugs] [Bug 121323] Crash dragging button after un-grouping compound group

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121323

Julien Nabet  changed:

   What|Removed |Added

   Keywords||haveBacktrace

-- 
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 121330] Error translation

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121330

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||serval2...@yahoo.fr
 Resolution|--- |FIXED

--- Comment #3 from Julien Nabet  ---
Fixed with:
-
https://translations.documentfoundation.org/fr/libo_ui/translate/#search=BfQaB=source,target,notes
-
https://translations.documentfoundation.org/fr/libo61_ui/translate/#search=BfQaB=source,target,notes

-- 
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 81012] FORMATTING: Wrong chapter title in running header after the first page of endnotes

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81012

--- Comment #14 from Kartik Subbarao  ---
This bug is still present in LibreOffice 6.0.7.3.

-- 
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 121324] Writer 6.1 thru at least 5.4.4.2 cannot open docx files created by ver. 5.1 or MS Word

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121324

V Stuart Foote  changed:

   What|Removed |Added

 CC||vstuart.fo...@utsa.edu

--- Comment #2 from V Stuart Foote  ---
In addition to posting a sample test file, this is likely a LO user profile
problem--a lot of feature changes to styles and templates from 5.1 -> 6.1
releases.

Fortunately, easy to test newer builds without clobbering your 5.1.x profile.
Perform an administrative "msiexec /a" install in parallel [1] of 6.1.3 using
the TARGETIDR= entry and then adjusting the user configuration
to "UserInstallation=$ORIGIN/../Data/settings" in the bootstrap.ini file of the
TARGETDIR program folder.

Might have a little work to adjust things, but once opening cleanly you can
migrate into a new clean user profile.


=-ref-=
[1] https://wiki.documentfoundation.org/Installing_in_parallel/Windows

-- 
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 121328] Slow startup time on SSD

2018-11-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121328

V Stuart Foote  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #3 from V Stuart Foote  ---
Wait, you say startup any module in the OP. And opening to calc UI still
requires the backend work of parsing the registrymodifications.xcu for
soffice.bin to run, before it adds the load of building the UI elements and of
rendering grid to document canvas. 

So lets keep it simple, needinfo to OP:

1. are you delayed getting to an empty StartCenter? Or is it just on Calc
module launch (icon from desktop, or start menu)?  

2. And so move this report's component to LibreOffice/UI, or keep it in Calc?


Also, notice you are on x64 build with no OpenGL support--so for your hardware
initial launch with clean profile will experience OpenGL failure, by GPU driver
blacklist or functional test fail, and then fallback to Default CPU/HA
rendering.

Subsequent launch (running or reboot) with profile in place would go directly
to CPU/HA default rendering--another hurdle in confirming any issue.

Anyhow, I updated x64 install and disabled OpenGL, and still can not reproduce
launching directly to Calc, or into an empty StartCenter. Dealy is not
excessive, after profile creation--on initial and subsequent launches ~2
seconds.


=-testing-=
Windows 10 Home en-US 64-bit, Intel HD Graphics 620 GPU (24.20.100.6229)

Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: en-US (en_US); Calc: CL

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


  1   2   >