On 1/21/2019 7:37 AM, Matthias Seidel wrote:
Am 21.01.19 um 16:18 schrieb Rory O'Farrell:
On Mon, 21 Jan 2019 16:09:33 +0100
Matthias Seidel <matthias.sei...@hamburg.de> wrote:
Hi Rory,
Am 21.01.19 um 15:29 schrieb Rory O'Farrell:
On Mon, 21 Jan 2019 08:39:23 +0100
Peter Kovacs <pe...@apache.org> wrote:
Hi Rory,
do we have a Bug for this?
All the Best
Peter
Seems to be bug 115156
I have added my earlier information to that bug.
Can you please attach a file that crashes?
I can not reproduce this behavior with any docx I have available.
Regards,
Matthias
Sample file attached to bug report 115156
Opened fine with AOO420m1(Build:9800) - Rev. 1851640 (Jim's build) on
Xubuntu 18.04.1 (64-bit)
When exactly should the crash occur?
Matthias
I opened it on MS Windows 10, using the 4.1.6 download from Sourceforge.
No problems. This is significant because one of the changes in 4.1.6
involves expanding line separators from one character to two, which only
happens when opening a file on an MS Windows system.
I think we need more information on where this is happening. Also, I
wonder whether profile deletion affects it.
Rory
Rory
On 20.01.19 17:45, Rory O'Farrell wrote:
On Sun, 20 Jan 2019 10:28:53 -0500
Jim Jagielski <j...@jagunet.com> wrote:
I've uploaded the latest test builds for macOS and Linux 64.
These are based on ~r1851640 and include 2 main updates from
the earlier one:
o beanshell now included
o macOS path bug should now be squashed
(https://bz.apache.org/ooo/show_bug.cgi?id=127965)
Let me know if anyone wants me to kick off a Linux 32bit
build.
Find them here:
http://home.apache.org/~jim/AOO-builds/4.2.0-dev-r1851640/
Cheers!
I have seen a report that 4.1.6 is failing to open .docx files. 4.2.0
(r1851640) and Jim's earlier version are also failing with .docx files. The
latest 4.2.0 will crash with a small .docx (~20KB) and offer to recover it; it
will then display it. With a larger .docx (365 KB) it will crash, and be
unable to recover or display that file. It also does not identify the file with
which it has crashed or is trying to recover. I have not checked these
behaviours against 4.1.6
This does not present any immediate problem for me, as I work only in .odt format, but
after repairing a corrupt .docx file on forum for a user, I was unable to open it for
testing, although the repaired document.xml passed a "Well-formed XML" check.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---
This email has been checked for viruses by AVG.
https://www.avg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
