Attempting to open any Microsoft XML document causes General I/O error after upgrade to 4.1

users
#1

Just wanted to check here before I go open a bug...

I just upgraded to 4.1, everything seemed fine, but I encountered a .docx document this morning, and got the dreaded 'General I/O' error.

I then tried a bunch of different XML documents (.docx, .xslx, and .pptx), and every one resulted in the same error.

These are all docs that opened fine in 4.0.4

Will go back to 4.0.4 and confirm it resolves the problem...

#2

Hi :slight_smile:
I sometimes get that from files "on the network" but when i copy them to local desktop machine they work fine.  I've not really been tracking which versions it happens with.  There seems to be something about the memory settings as higher spec machines with memory settings radically bumped right up seem to suffer this a lot less.  They still get it occasionally tho.

I thought it was my inexperience with networking or something
Regard from
Tom :slight_smile:

#3

FWIW:
I do not know the correlation of versions between LO and AOO, but today I got the following two security reports from the AOO users forum:

#4

Hi :slight_smile:
I am not 100% sure but LO has quietly dealt with a couple of potential threats of that nature quite a long time ago.  The 3.4.0 and i think another in that same line were both quietly being pushed due to some known issue in the 3.3.x line.  Most of us just ignored it and carried on using the supposedly problematic versions and had no problems though.

Also i know that some of the code and patches have been quietly shared between the projects even when Oracle were being all stuffy about it so i really don't know if they are fixing something that LO already fixed ages ago or if this is something new.  The 2 projects are very divergent now.  Only around 12% of the code hasn't been touched at all.  Although, as Umas said some of the changes may have been just removal or rewrites of commented-out lines.

Regards from

Tom :slight_smile:

#5

Hi,

Girvin R. Herr wrote (26-07-13 22:57)

FWIW:
I do not know the correlation of versions between LO and AOO, but today
I got the following two security reports from the AOO users forum:

FYI:
http://listarchives.documentfoundation.org/www/discuss/msg09642.html

Cheers,
Cor

#6

Girvin R. Herr wrote:

-------------------------------------------------------

CVE-2013-2189

and

-------------------------------------------

CVE-2013-4156

Both are fixed in all current LibreOffice versions. Up-to-date
information about security fixes / advisories is always available
from:

http://www.libreoffice.org/advisories/

Cheers,

-- Thorsten

#7

So, since I'm on the 4.1 release version, this isn't the cause of my problems?

Is no one else having this problem?

I'm on (32bit) XP Pro sp3 up to date, with JRE 7u25...

#8

Not sure if this was even remotely close to my reported problem.

1. Upgrade to 4.1 (Windows 32bit XP Pro sp3 fully up to date)

2. Open Writer, create a new text document with the word 'test' in the body.

3. Save as .odt file.

4. Open file (opens fine).

5. Save As > .docx file.

6. Attempt to open the file - encounter General I/O error.

Haven't tested on Windows 7 yet, but will in a bit...

#9

Hi Tanstaafl

I followed your emails and this last one with your process.

I can offer my input as to Windows 7. I am using Windows 7 Ultimate 64bit, all up to date with jre-7u21, both 32bit and 64bit installed (this should not be an issue though as covered by many emails posts, LO is reducing it's need for Java support). I was testing LO 4.1 so I have LO 4.0.4.2 stable installed alongside LO 4.1.0.3 RC3, following the online guidelines on installing two LO versions without clashes.

I did each step posted below and created the .docx document. I was able to open it with no incident whatsoever, so it might either point to a XP / LO problem under 32bit, or something you have installed in XP causing the crash.

Hope this helps to iron out some of your issue.

Regards

Andrew Brown

#10

The second one I tried it on (the first after mine, that was broken) it worked fine, so apparently it is something borked on my workstation...

Sorry for the noise...

#11

Hi :slight_smile:
Nice to see these got fixed before almost anyone knew there was even a problem and waaaay before AOO dealt with the issues! :))
Good work and congrats to the devs, yet again :slight_smile:
Regards from
Tom :slight_smile: