Issue 82059 - Some files produce "General Input/Output error" when being opened
Summary: Some files produce "General Input/Output error" when being opened
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: andreas.schluens
QA Contact: issues@sw
Keywords: regression
Depends on:
Reported: 2007-09-28 13:31 UTC by kpalagin
Modified: 2013-08-07 14:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description kpalagin 2007-09-28 13:31:55 UTC
File will be sent to es@openoffice because it is confidential.

Version 2.2 opens the file just fine.
Comment 1 kpalagin 2007-09-28 13:38:04 UTC
Setting keyword regression.
Comment 2 eric.savary 2007-09-28 14:28:03 UTC
Bugdoc sent to AMA.
Comment 3 kpalagin 2007-10-01 09:20:21 UTC
Andreas, Eric,
any chance to fix this in 2.3.1 as this is regression?

Comment 4 andreas.martens 2007-10-01 10:52:34 UTC
AMA: There is always a chance :-)
There are two OLE objects in this document which causes the error message.
Comment 5 mikhail.voytenko 2007-10-09 13:11:25 UTC
This is no real regression, only the error messages are new.

The document objects seem to be broken, the internal streams of the object are
written in wrong format. It would be interesting to know how the document was
generated. It looks like a bug has happened on document generation.

Comment 6 kpalagin 2007-10-10 14:18:00 UTC
According to the user file was generated by OOo2.1.
I would suggest suppressing error messages to be more user-friendly.
Comment 7 kpalagin 2007-10-18 11:32:03 UTC
More users report this problem and all claim that files were generated by 
prior versions of OpenOffice.
Comment 8 kpalagin 2007-12-13 08:47:22 UTC
less than a month has left untill code freeze.
Are we on track for 2.4 with this issue?

Thanks a lot for your attention.
Kirill Palagin.
Comment 9 mikhail.voytenko 2007-12-13 09:08:22 UTC
As I have written, the error message is correct. Suppressing of error reporting
is no user-friendly solution.

This bug is more about the corrupted documents, but it seems to be impossible to
generate such a document with a newer office. So the only thing that can be done
for this bug is to try to repair the embedded document if it is possible,
although even in this case the error notification should be done.

Currently I am not completely sure that the change will get to 2.4, but it
stands a good chance.
Comment 10 mikhail.voytenko 2008-01-08 17:00:44 UTC
Unfortunately the repairing is allowed only with correct UI notification.
Otherwise the behavior cood look even worse, as it happens in this case. The
broken objects are not only in wrong format, they also represent empty
documents, so they are really corrupted.
In case they are not repaired, the user just gets the objects that can not be
activated. In case they are repaired, the activation shows empty document. So
the unexperienced user could loose even the replacement images. Such a behavior
is acceptable only if the user has previously accepted the repairing, means he
knows what he is doing.

So I must confess, in this case it really makes sense to go back to the old
behavior. The error message is acceptable only if it could be turned off using
checkbox or something like this ( just imagine a document with hundred broken
embedded objects ), that is not allowed after feature-freeze.

Fixed in cws fwk82, the error message should not appear any more.
Comment 11 kpalagin 2008-01-08 17:24:35 UTC
thank you very much!!

Comment 12 mikhail.voytenko 2008-01-17 08:48:08 UTC
MAV->AS: Could you please verify the issue.
Comment 13 andreas.schluens 2008-01-17 08:58:40 UTC
as: Verified.
Comment 14 thorsten.ziehm 2009-07-20 14:52:46 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
If you want to know more about the handling of fixed/verified issues =>