[Libreoffice-bugs] [Bug 91257] Cells show wrong numbers

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91257

q...@bk.ru changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|NEEDINFO|RESOLVED

--- Comment #7 from q...@bk.ru ---
I suppose this bug is not a bug. So let's close it.

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


[Libreoffice-bugs] [Bug 118408] Programm stürzt ab Nachdem beim Serienbrief-Assistent "Adressenliste auswählen" ausgewählt wurde (Linux)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118408

supp...@schumacher-packaging.com changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #3 from supp...@schumacher-packaging.com ---
Now the program crashes immediately, when i open the "Mail Merge Wizard"
Without any Error.

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


[Libreoffice-bugs] [Bug 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

--- Comment #6 from Xavier Van Wijmeersch  ---
I can not reproduce

Version: 6.2.0.0.alpha0+
Build ID: 2e142c0ee54744d35517f0b9c49a24302fb32d47
CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: gtk3; 
Locale: nl-BE (en_US.UTF-8); Calc: group 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 118404] Linux libre office does not work correctly

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118404

mkts  changed:

   What|Removed |Added

 CC||michael.lashkev...@gmail.co
   ||m

--- Comment #3 from mkts  ---
*** Bug 113973 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 113973] Linux middle mouse button copy does not work correctly

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113973

mkts  changed:

   What|Removed |Added

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

--- Comment #22 from mkts  ---


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

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


[Libreoffice-bugs] [Bug 117947] The object position doesn’t return by “Undo”

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117947

--- Comment #5 from Dr. Kiyoshi Ogawa  ---
Repro with
Version: 6.0.4.2
Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf
CPU thread 4; OS: Mac OS X 10.12.6: UI render: default;
Locale: ja-JP (j_JP.UTF-8); Calc: CL

CPU :3GHz Intel Core i7 ; OS: macOS Sierra version 10.12.6 
Memory 16GB 1600MHz DDR3, Graphics Intel Iris 1536M

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


[Libreoffice-bugs] [Bug 102195] Text between two animated lines disappears in slideshow

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102195

Mike Kaganski  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #4 from Mike Kaganski  ---
https://gerrit.libreoffice.org/56571

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


[Libreoffice-bugs] [Bug 114845] FILESAVE: PPTX Incorrect position of shapes after RT

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114845

--- Comment #9 from Commit Notification 
 ---
Justin Luth committed a patch related to this issue.
It has been pushed to "libreoffice-6-1":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=dea74f31d2a0062547e279bb934c60731f5e560d=libreoffice-6-1

tdf#114845 sd: only shift rotated group items

It will be available in 6.1.0.1.

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

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

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


[Libreoffice-bugs] [Bug 114845] FILESAVE: PPTX Incorrect position of shapes after RT

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=114845

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:6.2.0|target:6.2.0 target:6.1.0.1

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


[Libreoffice-bugs] [Bug 105610] Feature Request: Display found word/phrase in a constant position on the screen and change highlight colour

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105610

V Stuart Foote  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 118418] Should implemented scrollto, scrolltopoint, scrollsubstringto, scrollsubstringtopoint

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118418

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=10
   ||5610
 CC||vstuart.fo...@utsa.edu

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


[Libreoffice-bugs] [Bug 118424] Unusable font files installed by LibreOffice 6 on Windows.

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118424

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #2 from V Stuart Foote  ---
Can not confirm on Windows 10 Home 64-bit en-US with

GIMP 2.10.2

and 
Version: 6.0.5.2 (x64)
Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU threads: 4; OS: Windows 10.0; UI render: default (or OpenGL)
Locale: en-US (en_US); Calc: CL

Both programs launch and run with out 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 107222] FILEOPEN FORMATTING DOCX Wrong page number position

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107222

--- 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 52359] "Show Details" won't work as expected

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=52359

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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


[Libreoffice-bugs] [Bug 108649] HTML export should write what it can even if exception

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108649

--- 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 108201] [Feature request] Export superscript numbers in footnote fields to HTML

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108201

--- 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 100639] FILEOPEN Page number doesn't display (MS Publisher)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100639

--- 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 108801] Text blurred on Retina screen with low-res monitor as second screen

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108801

--- 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 108559] Pasting direct formatted text in cell edit mode doesn't always retain the original direct formatting

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108559

--- 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 107212] Drawing Object Properties toolbar shouldnt be enabled when drawing a textbox

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107212

--- 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 51022] Print range lost on file save/reopen if the file contains external link

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=51022

--- 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 93095] EDITING - sqlite3 table fields considered as SQLNull datatype in table creation mode using Xerial jdbc driver (OSX)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=93095

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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


[Libreoffice-bugs] [Bug 35136] "Reset Page Numbering after title pages" option does not work

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=35136

--- 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 94661] FORMATTING: In table of contents, page number is not aligned right when automatic numbering is removed

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=94661

--- 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 64361] EDITING: Complex fields added by Zotero expand to include text typed after them

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=64361

--- 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 85162] FORMATTING: wrong page numbers (with not standard Word field) in particular .docx

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85162

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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


[Libreoffice-bugs] [Bug 65807] Line Numbers in Comments printed "after each page" are continuous (and do not restart after each page)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=65807

--- 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 93315] Calc: Print Preview empty with a 100 bordered rows. Works, if row 85 is without borders

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=93315

--- 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 108491] XHTML export puts inline formulae on separate lines

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108491

--- 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 108639] Cannot select individual characters of span element contents with mouse

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108639

--- 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 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

malboarg  changed:

   What|Removed |Added

 CC||malbo...@gmail.com

--- Comment #5 from malboarg  ---
I can not reproduce the bug in

Version: 6.0.5.1
Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751
CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; 
Locale: es-AR (es_AR.UTF-8); Calc: group

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


[Libreoffice-bugs] [Bug 118416] SEGV when Calc exits when it tries to export an image of a whole column on the system clipboard

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118416

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #3 from Xisco Faulí  ---
No problem with

Version: 6.2.0.0.alpha0+
Build ID: 6ebc026e34d0c119067e7dfbad8d932f92844760
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded

I guess it's only in debug mode ?

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


[Libreoffice-bugs] [Bug 118380] Fatal error: Bad array new length

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118380

--- Comment #4 from Xisco Faulí  ---
No problem in 

Version: 6.2.0.0.alpha0+
Build ID: b047ae6e5bde4a20a9ad8b7d570d93496187
CPU threads: 16; OS: Windows 6.3; UI render: default; 
Locale: en-GB (en_GB); Calc: group threaded

either...

Wondering if I'm missing a step or something...

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


[Libreoffice-bugs] [Bug 118425] New: DOCX file is considered ODT when trying to digitally sign

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118425

Bug ID: 118425
   Summary: DOCX file is considered ODT when trying to digitally
sign
   Product: LibreOffice
   Version: 6.1.0.0.alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Keywords: bisected, regression
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: kelem...@ubuntu.com
CC: s.mehrbr...@gmail.com, vmik...@collabora.co.uk

Created attachment 143177
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143177=edit
Screenshot of the problem

When trying to digitally sign any DOCX file using an X.509 signature, LO lately
gives an error message stating the file contains signatures in v1.1 of ODF (!),
and save it in ODF 1.2 to continue.
In earlier releases it used to sign DOCX files.

1, Set up a digital signature certificate, make sure you can sign ODF files
2, Open any existing DOCX
3, Go to File - Digital Signatures - Digital Signatures.
4, Click the Sign Document button.
5, LO shows the dialog on the attached screenshot and does not allow to
digitally sign the file.

Bibisected using bibisect-linux-64-6.1 to this commit: 

https://cgit.freedesktop.org/libreoffice/core/commit/?id=13596e704e4b48e8b0892867b3f3fc351a2729f9

gabor@dome:~/src/bibisect-linux-64-6.1$ git bisect log
# bad: [86b830bc9ec0e18bba22a6918d402693712c4592] source
sha:5b20226bb0e431afa4505373aaa0af2d28479528
# good: [2c119f9e70d2ecbc9ba7815abd674ab6d858] source
sha:6eeac3539ea4cac32d126c5e24141f262eb5a4d9
git bisect start 'origin/master' 'oldest'
# good: [f586004c79081288c327d42bf8e900efb455155d] source
sha:ccd316d1cb310734848bd20244f509024b549b8c
git bisect good f586004c79081288c327d42bf8e900efb455155d
# good: [f6d2923b58b379ee44fc2f887fd40b57f6376ffd] source
sha:448dafe7e6b54f8e154c46f0d82da6c59febfb74
git bisect good f6d2923b58b379ee44fc2f887fd40b57f6376ffd
# good: [100534be16ec71fa1014ded5c0e8d8fef061d17f] source
sha:b46af3670cbcd503875677bcca9cba8ad49984a7
git bisect good 100534be16ec71fa1014ded5c0e8d8fef061d17f
# good: [02927ade84af64d5a4f6db9de583f8e4ea52e37b] source
sha:2bd48ad3bc29b008d756612307d3e72021bc3cbf
git bisect good 02927ade84af64d5a4f6db9de583f8e4ea52e37b
# good: [a1c72ad690fd53a4ceee02addfd107ae7f1c982e] source
sha:0c02f3c5d64bd6db96db0302169fb4c4b48dc27e
git bisect good a1c72ad690fd53a4ceee02addfd107ae7f1c982e
# bad: [894797e5886a0f5bf69184e72f8463066306bd13] source
sha:47d53d6929d449b0b53dc73eddf29fe9c18fb49e
git bisect bad 894797e5886a0f5bf69184e72f8463066306bd13
# bad: [a99ff50cd76afc31e7ff899d26a1e47fe9b33ec5] source
sha:4552096794c408110630ab2eaf47bebaa6c403f2
git bisect bad a99ff50cd76afc31e7ff899d26a1e47fe9b33ec5
# bad: [18659fd37f2833a1ce1333b4dcd7eb14a343ee83] source
sha:066abd6163a1b12e3bdcaf0385a4842c7bc7d119
git bisect bad 18659fd37f2833a1ce1333b4dcd7eb14a343ee83
# good: [3b2f801d79d4cff7d5262c4343bb923206dc106e] source
sha:99337b029a3f94257160077ecf11ee3c59c77b7c
git bisect good 3b2f801d79d4cff7d5262c4343bb923206dc106e
# bad: [b62f6c034f1c7945bad8f17afcd267c88f1bc0b9] source
sha:0f2157cb1513371829d7f8c415324cffed28c377
git bisect bad b62f6c034f1c7945bad8f17afcd267c88f1bc0b9
# bad: [fab5277f1185c30294a21b46bf12efe86e9cf0a9] source
sha:c697e7f566302d5d52c3a043d5bddd8cf65499a1
git bisect bad fab5277f1185c30294a21b46bf12efe86e9cf0a9
# bad: [98fdb418286a95c7cecd0d9cc49c836389cbe757] source
sha:57cc8b2e4f93b3a93ce9ac46a2a98eb2a799faa3
git bisect bad 98fdb418286a95c7cecd0d9cc49c836389cbe757
# bad: [4ce0cc9e90dffde1a1f6af1a8d7db11677084f88] source
sha:13596e704e4b48e8b0892867b3f3fc351a2729f9
git bisect bad 4ce0cc9e90dffde1a1f6af1a8d7db11677084f88
# first bad commit: [4ce0cc9e90dffde1a1f6af1a8d7db11677084f88] source
sha:13596e704e4b48e8b0892867b3f3fc351a2729f9
gabor@dome:~/src/bibisect-linux-64-6.1$

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


[Libreoffice-bugs] [Bug 118380] Fatal error: Bad array new length

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118380

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #3 from Xisco Faulí  ---
I can't reproduce it in

Version: 6.2.0.0.alpha0+
Build ID: 6ebc026e34d0c119067e7dfbad8d932f92844760
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group 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 118419] Wrong Context Menu Before Misspelt Word

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118419

--- Comment #1 from Jacques Guilleron  ---
Hi Harald,

I don't reproduce with
LO 6.0.4.2 Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf
Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; 
Locale : fr-FR (fr_FR); Calc: CL
Same behavior when using Open GL.

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


[Libreoffice-bugs] [Bug 118392] Document watermark takes over the whole document

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118392

--- Comment #9 from Susan Gessing  ---
Created attachment 143176
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143176=edit
Watermark issue screenshot from 6.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 118392] Document watermark takes over the whole document

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118392

--- Comment #8 from Susan Gessing  ---
Created attachment 143175
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143175=edit
Watermark issue screenshot from 6.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 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #4 from Xisco Faulí  ---
I can't reproduce it in

Version: 6.2.0.0.alpha0+
Build ID: 6ebc026e34d0c119067e7dfbad8d932f92844760
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group 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 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

--- Comment #3 from Jean-Baptiste Faure  ---
Well, if I launch LO 6.1 in the terminal, I get the following error messages:

terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'


Fatal exception: Signal 6
Stack:
/home/libo/60/instdir/program/libuno_sal.so.3(+0x13cf3)[0x7f551cc02cf3]
/home/libo/60/instdir/program/libuno_sal.so.3(+0x3d892)[0x7f551cc2c892]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0)[0x7f551c5a24b0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f551c5a2428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f551c5a402a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8f7)[0x7f551bc448f7]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92a46)[0x7f551bc4aa46]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x91aa9)[0x7f551bc49aa9]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(__gxx_personality_v0+0x2e8)[0x7f551bc4a458]
/lib/x86_64-linux-gnu/libgcc_s.so.1(+0x10573)[0x7f551b6a7573]
/lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0x125)[0x7f551b6a7df5]
/home/libo/60/instdir/program/libvcllo.so(+0x57af04)[0x7f551584df04]
/home/libo/60/instdir/program/libuno_sal.so.3(+0x16d22)[0x7f551cc05d22]
/home/libo/60/instdir/program/libuno_sal.so.3(+0x3d762)[0x7f551cc2c762]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0)[0x7f551c5a24b0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f551c5a2428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f551c5a402a]
/home/libo/60/instdir/program/libvcllo.so(_ZN16SalUserEventList18DispatchUserEventsEb+0x3c1)[0x7f5515829ee1]
/home/libo/60/instdir/program/libvclplug_gtk3lo.so(+0x7d779)[0x7f550231e779]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x15a)[0x7f550df0f04a]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0)[0x7f550df0f3f0]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f550df0f49c]
/home/libo/60/instdir/program/libvclplug_gtk3lo.so(+0x7ea94)[0x7f550231fa94]
/home/libo/60/instdir/program/libvcllo.so(_ZN11Application5YieldEv+0x2e)[0x7f55158489ae]
/home/libo/60/instdir/program/libvcllo.so(_ZN11Application7ExecuteEv+0x45)[0x7f551584a195]
/home/libo/60/instdir/program/libsofficeapp.so(+0x28a1e)[0x7f551c95fa1e]
/home/libo/60/instdir/program/libvcllo.so(+0x57c896)[0x7f551584f896]
/home/libo/60/instdir/program/libvcllo.so(_Z6SVMainv+0x30)[0x7f551584f9a0]
/home/libo/60/instdir/program/libsofficeapp.so(soffice_main+0x115)[0x7f551c989d85]
/home/libo/60/instdir/program/soffice.bin[0x4006db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f551c58d830]
/home/libo/60/instdir/program/soffice.bin[0x400719]

If nobody can reproduce I will rebuild in debug mode and run LO through gdb.

Best regards. JBF

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


[Libreoffice-bugs] [Bug 118424] Unusable font files installed by LibreOffice 6 on Windows.

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118424

--- Comment #1 from luvr  ---
Created attachment 143174
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143174=edit
BAT file to move the LibreOffice font files out of the way.

After I moved the LibreOffice font files out of the way and forced my system to
recreate its FNTCACHE.DAT file, everything returned to normal.

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


[Libreoffice-bugs] [Bug 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

--- Comment #2 from Jean-Baptiste Faure  ---
(In reply to Drew Jensen from comment #1)
> looks to be language specific.
> 
It's not clear for me: my LO 6.1 is configured in French and my LO 6.2 is
configured in English.

Best regards. JBF

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


[Libreoffice-bugs] [Bug 96099] Reduce number of typedefs used for trivial container types

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96099

--- Comment #65 from Commit Notification 
 ---
Arkadiy Illarionov committed a patch related to this issue.
It has been pushed to "master":

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

tdf#96099 Remove *HandlerPtr typedefs in writerfilter

It will be available in 6.2.0.

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

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

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


[Libreoffice-bugs] [Bug 118424] New: Unusable font files installed by LibreOffice 6 on Windows.

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118424

Bug ID: 118424
   Summary: Unusable font files installed by LibreOffice 6 on
Windows.
   Product: LibreOffice
   Version: 6.0.5.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: luc.vanromp...@gmail.com

Description:
I installed GIMP 2.10 on Windows 10, then installed LibreOffice 6.
>From that point on, GIMP no longer worked, but instead crashed upon startup.
Furthermore, the LibreOffice startup screen displayed its text messages in a
rather unpleasant fixed-width font (see
https://drive.google.com/open?id=1wcJa8oFw8IxJsQaWaYxkgif1dZOR0dHQ)--as if the
font that it actually was trying to use didn't work.

Uninstalling LibreOffice made GIMP work normally again.

Reinstalling LibreOffice, then removing the font files that it added to my
C:\Windows\Fonts directory, also allowed GIMP to function normally. In
addition, the LibreOffice startup screen now displays a far more pleasant font.

Steps to Reproduce:
1.  Install GIMP 2.10.
2.  Start GIMP - Works OK.
3.  Install LibreOffice.
4.  Start LibreOffice - Works OK (except for the unpleasant font on its startup
screen).
5.  Start GIMP - CRASH!
6.  Remove LibreOffice font files from the system.
7.  Delete FNTCACHE.DAT from C:\Windows\System32.
8.  Reboot - FNTCACHE.DAT is recreated, but smaller than it was.
9.  Start GIMP - OK.
10. Start LibreOffice - OK.

Actual Results:
After installing LibreOffice, GIMP stops working, but crashes on startup.

Expected Results:
GIMP should continue to function normally, whether or not LibreOffice is
installed.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Removing the LibreOffice font files from my system allowed GIMP to work
normally again.

Something seems badly wrong with the LibreOffice font files, since even
LibreOffice itself seems to be unable to make sense of them.

See also https://gitlab.gnome.org/GNOME/gimp/issues/1366#note_256010

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


[Libreoffice-bugs] [Bug 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

--- Comment #1 from Drew Jensen  ---
looks to be language specific.

Using Ubuntu 18.04 (64bit) and build: Version: 6.1.0.0.beta2+
Build ID: 66881028595257fcf11985fd0e8835f4360632a0
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-1, Time:
2018-06-27_02:21:25
Locale: en-US (en_US.UTF-8); Calc: group threaded

and Version: 6.2.0.0.alpha0+
Build ID: aae64e0f9cd1582c0dc31992aa22b849d2527c80
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time:
2018-06-23_02:31:34
Locale: en-US (en_US.UTF-8); Calc: group threaded

I can open that set of options, make changes, save the changes.
Everything worked fine.

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


[Libreoffice-bugs] [Bug 118423] Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

Jean-Baptiste Faure  changed:

   What|Removed |Added

 OS|All |Linux (All)
   Keywords||regression
   Priority|medium  |high
   Hardware|All |x86-64 (AMD64)
   Severity|normal  |critical

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


[Libreoffice-bugs] [Bug 118423] New: Crash on opening writing aids options

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118423

Bug ID: 118423
   Summary: Crash on opening writing aids options
   Product: LibreOffice
   Version: 6.1.0.0.beta2+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jbfa...@libreoffice.org

Steps to reproduce:
1/ launch LibreOffice
2/ menu Tools > Options > Language Settings > Writing Aids

=> crash

Reproducible with LO 6.1.0.0.beta2+:Version: 6.1.0.0.beta2+
Build ID: ee81a4cd7778e3733b8237380b996fd3e4fee77b
Threads CPU : 4; OS : Linux 4.4; UI Render : par défaut; VCL: gtk3; 
Ubuntu_16.04_x86-64
Locale : fr-FR (fr_FR.UTF-8); Calc: threaded

Reproducible with LO 6.2.0.0.alpha0+: Version: 6.2.0.0.alpha0+
Build ID: 043701c56cae1e281e1be90a262caa14ed936867
CPU threads: 4; OS: Linux 4.4; UI render: GL; VCL: gtk3; 
Ubuntu_16.04_x86-64
Locale: fr-FR (fr_FR.UTF-8); Calc: threaded

Crash with a clean new user profile too.

Best regards. JBF

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


[Libreoffice-bugs] [Bug 117790] Caption order, caption positions for Lithuanian language

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117790

--- Comment #11 from Modestas Rimkus  ---
For Lithuanian default caption order to be correct, together with setting
Caption Order default value to "Numbering first", Numbering Separator default
value must also be changed from dot+space to space only. I have no idea if and
how this can be achieved so I would need assistance from a more technical
person (as well as with changing the default caption position). Otherwise,
current configuration is better from the two evils.
Capitalization is a translation issue that I can handle after that.

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


[Libreoffice-bugs] [Bug 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

--- Comment #7 from JesseSteele  ---
Yeah! Julien, you are seeing it, and the other problems.

I can explain. I studied Greek in college and I get the font...

Those accent mark things above and under the letters are rendered by fonts
similarly to how "ff" might be a single character. I don't know base-language
level font encoding, but UTF-8 might regard ὑ or ά as actually two separate
characters, like combo letters in creating fonts.

Dealing with that "correctly" is probably where the problem begins.

Summary:

TexGyre might not do their fonts "correctly", but that Roman default font does.

Calligra got TexGyre to render correctly... BUT, Amazon's print on demand says
the Calligra .pdf file is broken...

(Calligra rant: in Calligra, .doc > .pdf, it messed up the page numbers; .odt >
.pdf Calligra was great, but Amazon said it was broken or someth. So, not even
Calligra is perfect in this.)

That's what I know.

Cheers and kudos 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 118422] The keyboard shortcut to view the data sources doesn't work on the MAC

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118422

Hans Gerstenkorn  changed:

   What|Removed |Added

 CC||gerstenkorn.h...@gmail.com

--- Comment #1 from Hans Gerstenkorn  ---
Created attachment 143173
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143173=edit
Screenshot of shortcut key at the context menu

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


[Libreoffice-bugs] [Bug 116547] Export of mathematical formula in Writer document to DOCX is displayed incorrectly in Word

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116547

Buovjaga  changed:

   What|Removed |Added

 CC||todven...@suomi24.fi

--- Comment #6 from Buovjaga  ---
Created attachment 143172
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143172=edit
DOCX exported with 3.5.0 (oldest of 43all repo)

Alex: can you open this in Word? If it shows the problem, bibisectRequest can
be changed to preBibisect.

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


[Libreoffice-bugs] [Bug 118422] New: The keyboard shortcut to view the data sources doesn't work on the MAC

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118422

Bug ID: 118422
   Summary: The keyboard shortcut to view the data sources doesn't
work on the MAC
   Product: LibreOffice
   Version: 6.0.2.1 release
  Hardware: Other
OS: Mac OS X (All)
Status: UNCONFIRMED
  Severity: trivial
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gerstenkorn.h...@gmail.com

Description:
The keyboard shortcut (shift + command key + F4 - please see also screenshot)to
view the data sources doesn't work on the MAC, per click with the mouse it
works perfect 

Steps to Reproduce:
1.press the key combination
2.
3.

Actual Results:
press the key combination

Expected Results:
nothing


Reproducible: Always


User Profile Reset: No



Additional Info:
if I'm clicking the menu "view/data sources" it works.

LO:
Version: 6.0.2.1
Build-ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU-Threads: 8; BS: Mac OS X 10.13.5; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group

MacBook Pro
Mac OS High Sierra 10.13.5 (17F77)

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


[Libreoffice-bugs] [Bug 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

Julien Nabet  changed:

   What|Removed |Added

 CC||vmik...@collabora.co.uk

--- Comment #6 from Julien Nabet  ---
On "Problem example DOC - via LibreOffice.pdf", 9th page of pdf, I see:
hudatoen/ ὑ δάάτων

whereas in "Problem example DOC - via Calligra.pdf", I see:
hudatoen/ὑδάτων

Ok so Calligra seems ok, not LO.

Strangely, I've opened "Problem example.doc" with 6.0.5.2 LO Debian (testing)
package and exported it, I got:
hudatoen/ ὑ δάτων (from copy paste)
but I see:
hudatoen/ὑδάτων
as if the copy paste would add some spaces.

I noticed on Evince that when highlighting "ὑδάτων", "ά" was replaced by a
square only on LO PDF export.

In brief, I don't reproduce exactly what you describe but I got a pb too.

Miklos: thought you might be interested in this one since it concerns PDF
export unless it's more about fonts rendering, in that case, Khaled may help
here?

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


[Libreoffice-bugs] [Bug 108638] FORMATTING Text size is not scaled correctly according to the zoom factor

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108638

Buovjaga  changed:

   What|Removed |Added

Version|3.5.7.2 release |3.5.0 release
   Keywords|bibisectRequest |bibisected

--- Comment #26 from Buovjaga  ---
(In reply to Yousuf Philips (jay) (retired) from comment #12)
> Created attachment 136445 [details]
> sample
> 
> i noticed this bug with this attached document and it has this behaviour.
> 
> 100%: fits
> 110%: doesnt fit (aka red arrow)
> 120%: fits
> 140%: doesnt fit
> 160%: doesnt fit
> 180%: doesnt fit
> 200%: doesnt fit
> 220%: doesnt fit
> 250%: doesnt fit
> 280%: doesnt fit
> 310%: doesnt fit
> 350%: doesnt fit
> 390%: fits

Bibisected with Linux 43all and the change seems to be in this range:
https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=ceb55cd688cebede8cef8408540019fe54528869...55c5ea43a59e505297fb6fa20b77aaa28f7c67bc

It certainly has many Calc commits picked by Eike (done by others), but nothing
jumps out to me. Eike is already in CC here.

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


[Libreoffice-bugs] [Bug 118408] Programm stürzt ab Nachdem beim Serienbrief-Assistent "Adressenliste auswählen" ausgewählt wurde (Linux)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118408

Dieter Praas  changed:

   What|Removed |Added

 Blocks||102998


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=102998
[Bug 102998] [META] Mail merge bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 102998] [META] Mail merge bugs and enhancements

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102998

Dieter Praas  changed:

   What|Removed |Added

 Depends on||118408


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=118408
[Bug 118408] Programm stürzt ab Nachdem beim Serienbrief-Assistent
"Adressenliste auswählen" ausgewählt wurde (Linux)
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 118408] Programm stürzt ab Nachdem beim Serienbrief-Assistent "Adressenliste auswählen" ausgewählt wurde (Linux)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118408

Dieter Praas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||dgp-m...@gmx.de
 Status|UNCONFIRMED |NEEDINFO

--- Comment #2 from Dieter Praas  ---
(In reply to Julien Nabet from comment #1)
> Could you give a try to 6.0.5 (and respond in English please)?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version. Change to
RESOLVED WORKSFORME, if the problem went away.

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


[Libreoffice-bugs] [Bug 118420] TRACK CHANGES: Shifting status of "show track changes" or "Record track changes" changes "saved" status

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118420

Dieter Praas  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||dgp-m...@gmx.de
 Blocks||108816, 83946
 Ever confirmed|0   |1

--- Comment #1 from Dieter Praas  ---
I confirm it with

Version: 6.1.0.0.beta2 (x64)
Build ID: 0f4d2060bc90b4008fbc8e6d9a49ec7eeea60b78
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: en-US (de_DE); Calc: CL


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83946
[Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108816
[Bug 108816] [META] Writer toolbar bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108816] [META] Writer toolbar bugs and enhancements

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108816

Dieter Praas  changed:

   What|Removed |Added

 Depends on||118420


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=118420
[Bug 118420] TRACK CHANGES: Shifting status of "show track changes" or "Record
track changes" changes "saved" status
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=83946

Dieter Praas  changed:

   What|Removed |Added

 Depends on||118420


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=118420
[Bug 118420] TRACK CHANGES: Shifting status of "show track changes" or "Record
track changes" changes "saved" status
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 117115] Firebird: migration from HSQLDB does not respect language-specific characters

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117115

Drew Jensen  changed:

   What|Removed |Added

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

--- Comment #12 from Drew Jensen  ---
checked on Ubuntu 18.04 with build:
Version: 6.2.0.0.alpha0+
Build ID: aae64e0f9cd1582c0dc31992aa22b849d2527c80
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time:
2018-06-23_02:31:34
Locale: en-US (en_US.UTF-8); Calc: group threaded

Works as expected.

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


[Libreoffice-bugs] [Bug 116968] [META] Migrating existing embedded HSQLDB databases to Firebird

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116968
Bug 116968 depends on bug 117115, which changed state.

Bug 117115 Summary: Firebird: migration from HSQLDB does not respect 
language-specific characters
https://bugs.documentfoundation.org/show_bug.cgi?id=117115

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 87219] FILEOPEN: line at the top displayed at the bottom in .rtf

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87219

Buovjaga  changed:

   What|Removed |Added

   Keywords|bibisectRequest |preBibisect

--- Comment #8 from Buovjaga  ---
Already in oldest commit of 43all bibisect repo

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


[Libreoffice-bugs] [Bug 87218] FILEOPEN: table displayed in wrong position in .rtf

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87218

Buovjaga  changed:

   What|Removed |Added

 CC||todven...@suomi24.fi
   Keywords|bibisectRequest |preBibisect

--- Comment #11 from Buovjaga  ---
(In reply to Aron Budea from comment #9)
> Table already appears on the left side in 3.5.0.3 / Ubuntu 16.04.

The text
 АКБ "РОСЕВРОБАНК" (ОАО)
 БИК 044585777 
к/с 301018108777
 АКБ "РОСЕВРОБАНК" (ОАО)

is not inside a table cell in the oldest of 43all bibisect repo. In 3.3 it is
still inside a cell.

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


[Libreoffice-bugs] [Bug 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

--- Comment #5 from JesseSteele  ---
The "columns" are a product of "justify text". In Pagella, each line ends with
a different word.

Look on PDF page 9 (labeled page 1)

You will see the little "v" thing by itself. It's not supposed to be. It's been
pushed out into the margin where it shouldn't be able to be.

The u da twv should be all one word.

Looking down at PDF pages 10-11 (labeled 2-3) the Greek letters are grouped as
all one word as they should be.

You can see this in the file I put in the GitHub repo.

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


[Libreoffice-bugs] [Bug 71984] FILEOPEN: Incorrect first line indentation (tab) in footnotes for MS Word documents (doc and rtf)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=71984

--- Comment #20 from BP  ---
Quickest workaround is to open the affected Word file, go into your first
footnote, search for ^t and leave replace empty, replace all. This will leave
the original space between the note number and the text.

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


[Libreoffice-bugs] [Bug 118421] FILESAVE: Shape is incorrectly rotated after RT

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118421

Xisco Faulí  changed:

   What|Removed |Added

   Keywords||bibisected, bisected,
   ||regression
 CC||jl...@mail.com,
   ||xiscofa...@libreoffice.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=70
   ||838

--- Comment #1 from Xisco Faulí  ---
Regression introduced by:

author  Victor Mireyev2018-06-02 16:08:59
+0300
committer   Justin Luth2018-06-16 06:49:56
+0200
commit  c14911a80e3b6e66439b1d569e7cd558c6010864 (patch)
treea1a49a1073c4372ded754865f85f1df05e9231a4
parent  2c85607101e2e04e870e3b87362f39f9a9148e6c (diff)
tdf#70838 ww8export: rotate shape vertically = swap width/height
During import, rotation past 45 degrees swaps height and width
in SvxMSDffManager::ImportShape, so exporting needs to do the same.

restored from abandonment and corrected by Justin

Import also adjusts TopLeft position, but position seems to
generally be set by other factors on export. Prefer to have
an example proof document and not just guess since it seems
that position is affected by many factors. Therefore, not
doing anything about the position in this commit.

Bisected with: bibisect-linux64-6.2

@Justin, since Victor is no longer envolved, I thought it could be a good idea
to add you as 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 70838] FILESAVE: doc: wrong size and position exporting rotated shapes

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=70838

Xisco Faulí  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 118421] New: FILESAVE: Shape is incorrectly rotated after RT

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118421

Bug ID: 118421
   Summary: FILESAVE: Shape is incorrectly rotated after RT
   Product: LibreOffice
   Version: 6.2.0.0.alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: xiscofa...@libreoffice.org

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

Steps to reproduce:
1. Open attached document
2. Save it as .DOC
3. Open the new document

Observed behaviour: the arrow is incorrectly rotated compared to the original
file.

Reproduced in

Version: 6.2.0.0.alpha0+
Build ID: 6ebc026e34d0c119067e7dfbad8d932f92844760
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded 

[Bug found by office-interoperability-tools]

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


[Libreoffice-bugs] [Bug 104651] UI - Reducing user confusion: Queries, Views and Tables

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104651

--- Comment #12 from Howard Johnson  ---
In light of a better understanding of this, I'd like to revise my prior
suggestion as follows:


Make a new section for Views, and organize things like this: 

-  Tables, Queries, Views, Forms, Reports, ..
+  Tables, Views, Queries, Forms, Reports, ..



I'm hearing 'WF' from a number of people, but I'm not seeing anyone yet saying
that Views should really quietly remain in Tables.  I am hearing that Views are
important and useful, and they are.

So to those of you who are suggesting WF:

Perhaps we need to mark this as: 
   'DWF' (Don't Want to Fix), or 
   'THTFRN' (Too Hard To Fix Right Now), or better yet, 
   'FS' (Fix Someday).


I admit that when I submitted this suggestion 1.5 years ago, I was coming from
a MS Access world that I'd been using Access for more than 10 years and was
fluent in it, and where I didn't know what Views were.

In Access queries were, and are, much more capable than in base.  I found it
extremely frustrating, and I still do, at how limited base is in so many ways. 
But I hasten to add that I have now moved all of my stuff to LO base over these
past 2 years, much to the dismay of my partner who has watched my frustration
and countless months spent during this conversion process.  

This is not because I'm enamored with LO base, for I am not, ...rather it's
because I want to be on GNU/Linux, and away from Windows.

I think it's so easy for those who already know how something works to assume
that others new to it will just get it.  But I've seen many people on the LO
ask site ask questions related to moving from Access to base and struggling
with this transition, so I'm not alone in this adventure.  How are people to
move to Linux who have databases on Windows???  Do they have to spend years to
get this done?  I hope not.  Thus the focus of most all of my bug reports and
feature suggestions.


More recently, I have been using a few Views, and find them quite helpful at
times! 

But I still think if on the main screen under "Database" it says "Tables", then
that's what should be there, Tables, and only tables!

And while one could change the title to "Tables and Views" to correct it, and
though that would be the simplest way to bring the honesty back to this
misleading situation, I don't recommend this.

I still don't see what's so wrong with wanting a Views button between Tables
and Queries (Tables, Views, Queries, Forms, Reports).  For one it would cause
the new users to say, "Hey, what up with Views?  Let's go look that up..."

So please if you can mark this as FS (Fix Someday) or something, but not WF,
unless you can really justify that it should not be fixed because it would not
be a good idea.  ..Because someday I still hope to get where I can fix some
of these things.  (I'm still on that nasty Linux learning curve on the way up.)

Thanks again.

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


[Libreoffice-bugs] [Bug 118420] New: TRACK CHANGES: Shifting status of "show track changes" or "Record track changes" changes "saved" status

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118420

Bug ID: 118420
   Summary: TRACK CHANGES: Shifting status of "show track changes"
or "Record track changes" changes "saved" status
   Product: LibreOffice
   Version: 5.4.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

1.  Open a new document.
2.  Shift status of "Show Track Changes" or "Record Track Changes"

Result:  "Save" status of document is now shown as "unsaved".

 (Same situation occur with any document)

Expected behavior: 

Changing "show track changes" or "record track changes" status does not change
the "Saved" status of the document.

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


[Libreoffice-bugs] [Bug 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

--- Comment #4 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, I git cloned your repo.

I noticed that LO pdf showed pairs of words in columns, on Calligra pdf it's
not the case.
Then I opened the odt, I saw these same colums.
I exported the file on pdf, same columns too.

I didn't see:
πολλῶ ν
ὑδά των
OR
ὑ δά των

I suppose I missed something but don't know what.

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


[Libreoffice-bugs] [Bug 102521] Bad docx text alignment in table

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102521

Timur  changed:

   What|Removed |Added

Summary|Bad docx text alignment |Bad docx text alignment in
   ||table

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


[Libreoffice-bugs] [Bug 107830] [META] DOCX (OOXML) paragraph-related issues

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107830
Bug 107830 depends on bug 102521, which changed state.

Bug 102521 Summary: Bad docx text alignment
https://bugs.documentfoundation.org/show_bug.cgi?id=102521

   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 102521] Bad docx text alignment

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102521

Timur  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 102521] Bad docx text alignment

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102521

--- Comment #5 from Timur  ---
Created attachment 143170
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143170=edit
example2 COMPARED

Looks fixed in master 6.2+, probably recently.

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


[Libreoffice-bugs] [Bug 118419] New: Wrong Context Menu Before Misspelt Word

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118419

Bug ID: 118419
   Summary: Wrong Context Menu Before Misspelt Word
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: harald.koes...@mail.de
Blocks: 86349

In order to reproduce the bug:

[1] Create new text document. 
[2] Enable Automatic Spell Checking: Menu > Tools > Automatic Spell Checking
[3] Choose center alignment.
[4] Insert a misspelt word. The word is underlined with a read wavy line.
[5] Right click on misspelt word. A context menu is displayed with correction
items. This is OK.
[6] Right click right of misspelt word. A context menu with copy and paste and
formatting items is displayed. This is also OK.
[7] Right click and don't release mouse key left of misspelt word. The misspelt
word is selected and the context menu with the correction items is displayed.
Expected: Context menu like in step 6.
[8] Release mouse key. The context menu is no longer displayed. Expected:
Display of context menu like in step 6.

The same bug also occurs if the text is right-aligned and also in tables with
the respective alignements.

Bug occurs in version 6.0.5 (64 bit, Win 10)
The bug already exists in version 3.3.0. Hence inherited from OOo.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=86349
[Bug 86349] [META] Context menu bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86349] [META] Context menu bugs and enhancements

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86349

Harald Koester  changed:

   What|Removed |Added

 Depends on||118419


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=118419
[Bug 118419] Wrong Context Menu Before Misspelt 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 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

--- Comment #3 from JesseSteele  ---
You may need TexGyre installed to use real fonts for real publishing...

sudo apt install tex-gyre

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


[Libreoffice-bugs] [Bug 118405] Export as PDF from Greek, using TexGyre fonts

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118405

--- Comment #2 from JesseSteele  ---
Yo, Julien,

I'm cool, so I'm using Ubuntu 18.04.

I added your repo and tried 6.0.5. Same problem.

I hacked your W!nd@w$ link and the .deb package didn't install.

But, just clone or DL the repo and try it yourself, either the .doc or .odt
files and see if you get the spaces after the Greek letters that look like "a"
or "w"...

WRONG:
πολλῶ ν

ὑδά των
OR
ὑ δά των

RIGHT:
πολλῶν

ὑδάτων

git clone http://github.com/jessesteele/pdf-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 92796] [ODF] Writer does not remove unused page background image/bitmap

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92796

Buovjaga  changed:

   What|Removed |Added

   Keywords|bibisectRequest |preBibisect

--- Comment #17 from Buovjaga  ---
(In reply to raal from comment #11)
> Reproducible with LibreOffice 3.5.0 Build ID: d6cde02

preBibisect because this commit is the first in our bibisect repos

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


[Libreoffice-bugs] [Bug 87165] FILEOPEN RTF text missing in tables (partial regression)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87165

Buovjaga  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected
 CC||todven...@suomi24.fi
Summary|FILEOPEN: text missing in   |FILEOPEN RTF text missing
   |tables in .rtf  |in tables (partial
   ||regression)

--- Comment #12 from Buovjaga  ---
(In reply to Aron Budea from comment #10)
> This deteriorates in multiple steps.
> In 3.5.0.3 the rows with the missing text are flattened, but the text can
> still be found via search.
> In 4.0.0.3 the text can't be found anymore at all.

I checked this in Linux 43all and it seems to be in this range:
https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=a43a76cd5aa2f145f2cb43fcdbc8f21fb6c89af0...19f4ebd8a54da0ae03b9cc8481613e5cd20ee1e7=150

The only RTF commit is about tables, which is promising:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=c4b91ae3178011c66c76c711c1a6469ba658872e

Miklos is already in CC...

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


[Libreoffice-bugs] [Bug 118418] Should implemented scrollto, scrolltopoint, scrollsubstringto, scrollsubstringtopoint

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118418

Samuel Thibault  changed:

   What|Removed |Added

 CC||alexarn...@hypra.fr
  Component|UI  |sdk

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


[Libreoffice-bugs] [Bug 116721] copying text hangs LibO for 3-5 seconds

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116721

Timur  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #13 from Timur  ---
NeedInfo is quite appropriate, until we get some backtrace or steps.

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


[Libreoffice-bugs] [Bug 91706] Android: LibreOffice Viewer does not have localized UI

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91706

Xisco Faulí  changed:

   What|Removed |Added

   Priority|highest |high
 CC||xiscofa...@libreoffice.org

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


[Libreoffice-bugs] [Bug 106854] Unable to digitally sign exported PDF

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106854

Gabor Kelemen  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 106854] Unable to digitally sign exported PDF

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106854

--- Comment #16 from Gabor Kelemen  ---
Created attachment 143169
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143169=edit
Trying to sign with 6.2master and GOVCA example certificate

Still happens, but my hunch is that this particular cert I was given contains
something funny.

While testing bug #109180 I was able to digitally sign a PDF with the HW key of
my eID card, from the very same provider.

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


[Libreoffice-bugs] [Bug 118418] New: Should implemented scrollto, scrolltopoint, scrollsubstringto, scrollsubstringtopoint

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118418

Bug ID: 118418
   Summary: Should implemented scrollto, scrolltopoint,
scrollsubstringto, scrollsubstringtopoint
   Product: LibreOffice
   Version: 6.2.0.0.alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: samuel.thiba...@ens-lyon.org

Description:
For better accessibility, libreoffice should implement the scroll*to*
accessibility calls, which allow the screen reader to fix what is shown, so
that a blind user and a sighted user can understand each other when they are
working together on a document.


Actual Results:
iaccessible2 and atspi scrollto calls have no effect

Expected Results:
iaccessible2 and atspi scrollto calls should scroll the document


Reproducible: Always


User Profile Reset: No



Additional Info:
More precisely, for instance winaccessibility/source/UAccCOM/MAccessible.cxx
reads:

STDMETHODIMP CMAccessible:: scrollTo(enum IA2ScrollType)
{
return E_NOTIMPL;
}

It should support the requested scroll instead :)
(and similar for scrollToPoint, and in
winaccessibility/source/UAccCOM/AccTextBase.cxx for scrollSubstringTo and
scrollSubstringToPoint)

The code mentioned above is for Windows, Linux' atspi2 has just gotten scrollTo
and scrollToPoint in atk 2.29.1, and scrollSubstringTo and
scrollSubstringToPoint will probably be added before 2.30 too.

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


[Libreoffice-bugs] [Bug 118408] Programm stürzt ab Nachdem beim Serienbrief-Assistent "Adressenliste auswählen" ausgewählt wurde (Linux)

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118408

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #1 from Julien Nabet  ---
Could you give a try to 6.0.5 (and respond in English please)?

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


[Libreoffice-bugs] [Bug 118416] SEGV when Calc exits when it tries to export an image of a whole column on the system clipboard

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118416

--- Comment #2 from Tor Lillqvist  ---
Not sure why I don't get any message from the shell when running soffice and
doing the same thing that the process would have been killed by that SEGV. Does
cairo actually catch it? Anyway, even if it does, surely what the code tries to
do is insane?

The code in ScTransferObj::GetData() already shrinks the range handled in the
case of RTF or RICHTEXT. Most likely it should do that for *all* cases. But
Eike points out on IRC that it should not use the ShrinkToUsedDataArea()
function to do it, as that will apparently drop empty cells that still have
some visible formatting applied to them. Probably it should use
ScTable::GetPrintArea().

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


[Libreoffice-bugs] [Bug 118413] High CPU when working with remote files

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118413

lucas  changed:

   What|Removed |Added

   Hardware|All |x86-64 (AMD64)

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


[Libreoffice-bugs] [Bug 116721] copying text hangs LibO for 3-5 seconds

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116721

tommy27  changed:

   What|Removed |Added

Summary|copying text hang LibO for  |copying text hangs LibO for
   |3-5 seconds |3-5 seconds

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


[Libreoffice-bugs] [Bug 116721] copying text hang LibO for 3-5 seconds

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116721

tommy27  changed:

   What|Removed |Added

Version|6.0.2.1 release |5.3 all versions
 Status|NEEDINFO|NEW

--- Comment #12 from tommy27  ---
Ok, let's set status to NEW and version to "5.3 all versions"
thanks Timur for 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 118417] New: OpenType tags wrongly exported on xhtml or EPUB

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118417

Bug ID: 118417
   Summary: OpenType tags wrongly exported on xhtml or EPUB
   Product: LibreOffice
   Version: 6.0.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: filters and storage
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rgb.m...@gmail.com

Created attachment 143168
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143168=edit
Test files. Original ODT, plus exported EPUB and xhtml and "fixed" xhtml

Let's suppose I build a document using Libertinus Serif as main font and that
some portion of the text have an OpenType tag like "smcp" (small caps) applied.
When exporting the document to xhtml or EPUB the corresponding css style gets
as font name

font-family:Libertinus Serif:smcp;

which of course is not interpreted by the target program. I do not know that
much of css, but I think the font name should translate as an style with
something like

font-family:Libertinus Serif; font-feature-settings:"smcp" 1; 

In fact, if I manually "fix" the xhtml file by changing the line

.T1 { font-family:Libertinus Serif:smcp; }

into 

.T1 { font-family:Libertinus Serif; font-feature-settings:"smcp" 1; }

the small caps text works without problems on my browser.

This problem is particularly important when fonts are embedded on the document
and the target renderer does not recognize the badly formatted font family,
giving a replacement font instead. 

The attachment contains:

- original odt file
- exported EPUB file
- exported xhtml file
- "fixed" xhtml file

Everything tested on LibO 6.0.5.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 118409] Untranslated strings strings

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118409

--- Comment #1 from Pénzes Dávid  ---
Created attachment 143167
  --> https://bugs.documentfoundation.org/attachment.cgi?id=143167=edit
A screenshot about the bug.

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


[Libreoffice-bugs] [Bug 69460] Copy/Paste of a column in Calc file followed by Cmd-Q causes soffice process to consume all resources

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=69460

--- Comment #28 from Tor Lillqvist  ---
(I mean select *and* *copy* in my previous comment, of course.)

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


[Libreoffice-bugs] [Bug 116721] copying text hang LibO for 3-5 seconds

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116721

--- Comment #11 from Timur  ---
This also happens to me..sometimes. Now I'm on 5.4.7 but I experienced on 5.3
and before. Can't remember when it started. 
Problem with this issue is not being reproducible, I guess. 
What seems like a "few seconds hang" is probably a dump. 

2 possible solutions:
-  run LO via procdump (always or before longer work with copying text) to get
a dump 
- upgrade LO to new versions and test whether it happens

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


[Libreoffice-bugs] [Bug 117176] LibreOffice remains on background if Base crashes, making it to crash all the time afterwards

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117176

Alex Thurgood  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 118397] MacOS: LibreOffice won't terminate after crash. It keeps showing the crash dialog in certain cases

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118397

Alex Thurgood  changed:

   What|Removed |Added

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

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


[Libreoffice-bugs] [Bug 118397] MacOS: LibreOffice won't terminate after crash. It keeps showing the crash dialog in certain cases

2018-06-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118397

--- Comment #3 from Alex Thurgood  ---
See also bug 117176 (where Xisco reported similar behaviour).

-- 
You are receiving this mail because:
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   3   >