Issue 56914 - General error: Input/output errors
Summary: General error: Input/output errors
Status: CLOSED DUPLICATE of issue 59890
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: ab
QA Contact: issues@framework
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-10-29 10:17 UTC by terrynorth
Modified: 2008-05-17 23:06 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description terrynorth 2005-10-29 10:17:44 UTC
New basic scripts do not replace old scripts resulting in input/output errors. 
I had OOo2RC1 when I experienced this problem when opening or saving
spreadsheets or opening the macro editor.  I got a lot of error messages
relating to 1.1.4/ 1.1.5 Basic scripts.  I eventually overcame the problem using
Tools /Macros /Organize Macros /OpenOffice.org Basic Macros /Organizer
/Libraries /Location: OpenOffice.org Macros & Dialogs to delete the old scripts.
 I found at the same time that the new scripts were not entered in the Organizer
so I had to append them manually.  Judging by postings on the Users and Discuss
mailing lists, a lot of others have experienced the same problem.
Comment 1 Olaf Felka 2005-11-01 09:08:58 UTC
Wrong component. Reassigning
Comment 2 terrynorth 2005-11-07 04:47:41 UTC
I think I should clarify how this problem arose.  I installed OOo2RC1 while I
still had 1.1.5 (Mandrake Linux).  After finding that OO2RC1 was better than the
earlier version, I uninstalled 1.1.5 and re-ran the OOo2 rpms (I could not find
any "repair" mechanism referred to in the README file so decided that re-running
the rpms would have to do).  It was then I started getting the error messages. 
Perhaps the problem really relates to the lack of a repair mechanism.
Comment 3 ulisses_penna 2005-12-01 21:22:57 UTC
  I have observed the problem with "General error: Input/output errors" message
also happens when I try to save files over mounted filesystems. 
  OpenOffice.org saves the file for the first time I modify it, but the second
time I try to save the file it shows me the message.
  The problem happens with those mount types:
a) shfs, and;
b) cifs (in fact there is more problems with CIFS than related here), and;
  The problem does not happen when using SMBFS (I have no idea why!)
I'm using:
a) openoffice.org-*-2.0.0-3 RPM
b) shfsmount version 0.35(2)
c) Linux kernel 2.6.5-63077cl
   Any other information?
Comment 4 terrynorth 2005-12-04 06:05:23 UTC
In response to the previous post, I'm using:
a) openoffice.org-*-2.0.0-3 RPM
b) shfsmount - not found
c) Linux kernel 2.6.11-6mdk

There is a string of posts recounting similar difficulties on the Users' list on
1 Dec 05.  Several mentions have been made of a section in the draft Users
Manual dealing with the subject but I can find no reference either in the Table
of Contents or in chapter 13 "Troubleshooting ...".
Comment 5 joerg.skottke 2005-12-30 10:35:34 UTC
Hi terrynorth,

thank you for supporting OOo.

I can confirm the issue, in fact it is an old one - for some reason we cannot
cope with macros from older installations, migration fails. The recommended
procedure is not to migrate any personal data or even better to deinstall the
1.x office in advance.

Setting target, change owner
Comment 6 joerg.skottke 2005-12-30 13:31:39 UTC
Created a meta-bug for this. We have countless incarnations of that problem
mostly resulting in an "Error loading Basic of Document" error  

*** This issue has been marked as a duplicate of 59890 ***
Comment 7 ulisses_penna 2006-01-12 14:40:28 UTC
The problem described here *is not* related with macros but related with mounted
file systems. This is not a duplicated issue of 59890!!!
Comment 8 ace_dent 2008-05-17 21:04:34 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 9 ace_dent 2008-05-17 23:06:36 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew