Apache OpenOffice (AOO) Bugzilla – Issue 11694
Over Quota Crash - Autosave / Save
Last modified: 2013-08-07 14:43:39 UTC
Hi, I work at an all-girls school where we use a single Windows 2000 domain to authenticate users. We had a problem recently where a few girls, well, quite a few girls were storing too much in their home directories. Shortly after I enabled disk quotas on my student home directories, I began to hear complaints from them about "random" crashes, missing documents, and frozen screens. I've been able to track this down to this scenario: - Girl logs into the domain with her account. She is given access to her home directory (we use the U: drive) - Assume girl's home directory is full, or near full. - Girl starts OOo Writer (although I suspect any part of the suite is problematic here), and beings to type. - Autosave on my computers is set on 10 minutes. In 10 minutes, Writer attempts to save. Because of the over quota directory, the save fails. - There is no error message at this point. The application locks solidly. No UI response at all. User must restart the system. - Interestingly, there are .tmp file(s) left over from the crash - all of them with 0 bytes (nothing in them). - I've been able to confirm that it's not just an autosave issue. All a user needs to do is save to the full quota'd disk. It will fail in exactly the same way. - Confirmed this in OOo 1.0.2 AND StarOffice PP2 on different PC systems running Windows 2000. What *should* happen is that the user is given a message like "Can't save, disk full", or whatever. Keep in mind, this error may not look the same to OOo as a disk full error. This would be a message from the domain controller or server telling her that she has surpassed her quota. I'd consider this to be a real showstopper for some of the corporate and education folks out there. Crashes will be attributed to OOo when a over-quota signal is the problem. Thanks as always for your attention!
I forgot to mention... I have set the default paths here to both the 'backup' and 'My Document' to the U: drive. This is why autosave is affected - it tries by default to save to the U: drive. If it's over quota, OOo locks solid.
I can't check this becaseu I don't have disk quotas set up on the drive. But I'll mark it as new, because it's important if still in 1.1 beta and a developer should look at it.
Verified with 644m13s2_8609 = There comes up an error message like could not save the document. Saveproblems. The document could not be saved.
Question: HOW was this resolved then? Does the user have any idea why he/she cannot save their document (ie., disk full?) It's not enough that the application doesn't crash. The user should have some feedback as to why they can't save. This is important because many times the user has no clue as to why they can't save something due to a full disk (or being over quota).
All tasks are verified in OOo 1.1 Beta2.
closed ...