Issue 15676 - OOo Does not warn if file can't be saved
Summary: OOo Does not warn if file can't be saved
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-16 14:57 UTC by mdekkers
Modified: 2013-02-07 22:38 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mdekkers 2003-06-16 14:57:36 UTC
saving a file to what later turns out to be a slightly corrupted VFAT filesystem does not 
generate error messages. OOo does not warn when the filesystem is not doing any saving at 
all. This leads the user (me!!) to believe that his work (a presentation I am about to deliver!!) is 
saved, when in fact, it has not. Closing OOo and late reopening leads to irrevocable data loss. 
 
It could be argued that this is a filesystem issue and not an OOo issue, however, at no point did 
I receive a warning that my filesystem is not 100% okay (using SuSE 8.2), and OOo just saves 
the file.
Comment 1 h.ilter 2003-06-16 15:20:58 UTC
HI->US: I have no VFAT. Please take over.
Comment 2 ulf.stroehler 2003-06-16 17:35:11 UTC
Martijn,

"slightly corrupted VFAT filesystem" what's that? Warnings in your
syslog? Which? Problems on mounting? What else?

Question: how should OOo control the filesystem?
Isn't an OS thought of providing proper file handling?

Although I really pitty you, but P1 seems inappropriate. Repriorityzing.

Transferring to TM.
Comment 3 Olaf Felka 2003-06-17 12:37:49 UTC
I've never heard that any application is warning if you try to save on
a "slightly corrupted" file system and I'm sure that OOo won't do
this. But this is not a defect this is an 'enormous' new feature to
integrate a system diagnostic tool to OOo.
Bettina,
please have a look.
Comment 4 ace_dent 2008-05-16 02:39:35 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 5 bettina.haberer 2010-05-21 14:42:24 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".