Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Give a Better Error Message when tmp Device Is Full|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description mbayer 2008-10-21 02:15:37 UTC
On *nx systems, OOo won't be able to save a file when the device mounted to /tmp is full or not writeable for some other reason (think NFS). Unfortunately the error message provided by OOo says only "could not write content.xml", which is not very illuminative to the average user. Users should be given some hint why something went wrong, e.g. by piping through the O/S' error message ("no space left on device" or so). Also, the full path to content.xml could be given in the error message, i.e. /tmp/content.xml.
Comment 1 thorsten.martens 2008-10-21 08:26:06 UTC
TM->requirements: please have a look.
Comment 2 mbayer 2008-10-21 15:52:52 UTC
As an alternative, the error message box (not the error message itself) could be enhanced in a way that it says: "Could not write 'context.xml' to temporary directory. Change setting for temporary directory now? [Y] [N]", thus offering a short cut to Tools -> Options -> OpenOffice.org -> Paths -> Temporary Files -> Edit. Maybe this is both, easier to implement and more convenient for the user.
Comment 3 k4os 2009-07-26 13:16:07 UTC
This ticket is idle for 9 month now, are there any plans to introduce an error message that actually tells the user what the problem is? I think mbayers proposed message is a good starting point, but should be extend to "Could not write to temporary directory _because disk is full_ "(if that is the reason) I think this is one reason why one cannot recommend OOo to the average user, since a full $temp-dir is a rather common when one regards what ammounts of data openoffice writes to that directory when it aims to open or save a big document
Comment 4 eric.savary 2009-07-26 14:23:48 UTC
@MAV: can you please tell us if OOo can provide a better error message in the described case? Please also have a look at issue 103815 to see if it's a duplicate of this one or an other occurrence (but different code) of the problem. Thanx!
Comment 5 mikhail.voytenko 2009-07-27 06:56:26 UTC
Yes, it should be possible to detect that the target location is full in this case. But the change that would allow to detect it and to transport the information to the stage, where the error can be shown, might be quite complex.