Issue 12967 - unable to save documents
Summary: unable to save documents
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: ab
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-02 22:55 UTC by jrls
Modified: 2013-02-24 21:09 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 jrls 2003-04-02 22:55:50 UTC
I have a single user who occassionally encounters the problem that she is unable
to save any of her documents.  An error will suddenly start reporting that an
unrecoverable error has occured.  She is using Mandrake Linux 8.1 with KDE and I
have tried to fix her problem by upgrading her from ver. 1.0 to 1.0.1 but it is
still happening.  I found that a file, $HOME/user/basic/script.xlc, had a size
of zero bytes so I copied her "$HOME/user/basic/dialog.xlc" to "script.xlc" and
changed any "dialog" entries in the file to "script".  This has allowed her to
be able to save again.  The only place that I could see any error messages was
in her "$HOME/.xsession-errors".  The last modified time on the "script.xlc"
file was right around the time that she shut down her PC for the day.  If she
had a blank document still running as she shut down, could that have wiped out
this file?
Comment 1 ooo 2003-04-04 14:47:42 UTC
maybe hopeless, if it cannot be reproduced when the script.xlc becomes
zero bytes
Comment 2 ab 2003-04-15 14:54:04 UTC
There's no connection between the script/dialog.xlc files and saving
documents besides the fact that Basic is initialised before saving
a document und Basic needs these files. OOo 1.1 Beta will not crash
any more if the xlc files are damaged in this situation. So the
document saving will not be affected any more. Of course it would be
interesting, how the xlc files can be damaged at all, but I think
this should be covered by another issue if a reproducable scenario
can be found for this. So I set this issue to fixed.
Comment 3 ab 2003-06-20 16:42:16 UTC
Closed