Closed Bug 103208 Opened 23 years ago Closed 13 years ago

aborting printing results in error page

Categories

(Core :: Printing: Output, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: sujay, Unassigned)

References

()

Details

Rod, re-filing this one per our phone conversation

1) launch netscape
2) jump to a long web page(above URL)
3) print
4) cancel the print job from the print manager

in doing so when you pickup the print job you see one page
after the last page that looks like this:

ERROR: syntax error
OFFENDING COMMAND: --nostringval--

STACK:

/G76
[48.0.0.0 7.0 50.0 44.0 ]
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

This error page varies depending on the page you're printing
and probably at what point you aborted the print job, but
you definitely get a similar printed out error page
I think this got fixed. I remember a similar bug about canceling from Print 
Monitor. And had checked in a fix for this.

Try again and reopen if you still see this.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
still get this....REOPEN. Rod, we talked on the phone about this bug remember?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I am unable duplicate this on Win98
Status: REOPENED → ASSIGNED
I can still reproduce this. follow original steps.

Target Milestone: --- → mozilla0.9.8
DOn, can you try to reproduce this? Reassigning to you, I have no way to
reproduce this problem.
Assignee: rods → dcone
Status: ASSIGNED → NEW
Don, ping me iof you can't reproduce this...I'm pretty sure I can....
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Target Milestone: mozilla0.9.9 → mozilla1.1
retargeting
Target Milestone: mozilla1.1alpha → Future
WFM - I don't see this. gone?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2
Assignee: dcone → printing
QA Contact: sujay
Assignee: printing → nobody
QA Contact: printing
Status: NEW → RESOLVED
Closed: 23 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.