Closed Bug 98076 Opened 23 years ago Closed 22 years ago

When I exceed quota in my home directory printing to file fails silently

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.2alpha

People

(Reporter: hramrach, Assigned: dcone)

References

Details

Used 0.9.3/Linux

steps to reproduce:
1) check that you can see a directory but can't write there
   (I tried / and my home with quota exceeded)
2) direct output into a file in this directory when printing

result: the output file is not created and no error reported

expected: eihter a root exploit should be used to allow the actual output happen
or an error should be reported (the later is a more general solution as it can
handle error conditions when no free disk space is available even to root ;-)
This is because checking disk space fails to check quotas.  Marking dupe of bug
72892 - "nsLocalFile::GetDiskSpaceAvailable ignores quotas for unix"

*** This bug has been marked as a duplicate of 72892 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
I think this is not a comlete dupe as it fails even in directory where quta is
not exceeded but I do not have write permission there. The problem is not
available space checking (the size of resulting printout may be unknown in the
time of check) but the fact that write errors are not reported (which may occur
even with the best available space checking as someone can eat the free space
after the check).
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This is a dependent on bug 100687.

-> printing.

You should consider implementing workarounds given the current brokenness. 
MailNews decided to implement partial fixes.
Assignee: dougt → dcone
Component: Networking: File → Printing
Depends on: 100687
QA Contact: benc → sujay
Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:

1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again

If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
Accidentally marked WFM, reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → mozilla1.2
The part with permissons fixed, rest in bug 72892.
Status: NEW → RESOLVED
Closed: 23 years ago22 years ago
Resolution: --- → FIXED
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.