i've been seeing this off and on using today's build (2002.07.29.05). sometimes printing fails, and i get a not-so-useful message, "Printing has failed for some reason." :-P i think simon saw this as well, but it seems tricky to repro...
okay, this *is* admittedly vague. ;) to clarify, i don't experience print failures of this kind all of time. here were some sites where printing was flakey (ie, with the vague error msg): * http://home.netscape.com * map results from http://yp.yahoo.com or http://maps.yahoo.com
when this does occur, the print dlg doesn't appear at all --the error dlg (sheet) only appears.
Summary: unable to print (erratic?): "printing failed for some reason" → unable to print (erratic): "printing failed for some reason"
Sarah, can you test to see if this is a regression?
I too have been having this issue. I printed a page (an FAQ) so it was purely html and text, no images, etc... I clicked on file->print->print preview. It opened the file in preview and I saved it as a PDF. When I went to print another page, the print option failed with a window sheet dropping down saying "printing failed for some reason".
james, thanks for the test case...but unfortunately i couldn't repro the error condition. it'll be tricky to find if/when this regressed, unless i can get a reproducible test case. :-/
I can reproduce this reliably on Chimera/2002080905 doing the following: Start a new Chimera session (this must be the first time attempting to print during a session). Go to File / Print. Click Cancel. Go to File / Page Setup. Click Cancel. Go to File / Print. You should get a "Printing failed for some reason." message. If you click OK from the Page Setup (instead of Cancel), subsequent Prints either do nothing at all, or display the same error message. The key is that you must Cancel the first Print command. If you go to Page Setup before you go to Print, there is no problem. Also, FWIW, Mozilla/2002073008 does not have this problem.
Assignee: saari → ccarlen
Status: NEW → ASSIGNED
Target Milestone: --- → Chimera0.5
-> sdagley to see if it's anything obvious (or fixed by the move to the 1_0_1 branch) while ccarlen is busy with TBird
No, really, reassigning to sdagley :-)
Assignee: ccarlen → sdagley
Status: ASSIGNED → NEW
This seems to have been fixed by ccarlen's recent fix for page setup as I can't repro given the steps in comment #7
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
wfm using the steps in comment 7 on 10.2.2 with 2002.11.15.04.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.