Closed
Bug 333624
Opened 18 years ago
Closed 18 years ago
print fails with "An unknown error occured while printing"
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u38342, Unassigned)
References
()
Details
When trying to print a page by "File"->"Print..." and choose printer (for testing, choose Postscript/default and check "Print to File" and hit "Print", enter the output file name. Then an error window appears saying "An unknown error occured while printing" After that, "Printing" window appears with "Title: blah blah" and "Progress: Preparing..." but it doesn't proceed (freezes). This happens even with emails. This didn't happen with nightly build some days ago. Today I saw this for the firat time with nightly trunk build id 2006041103 and my own build also (gtk2). What's wrong? Thanks in advance.
Updated•18 years ago
|
Assignee: general → printing
Component: General → Printing
Product: Mozilla Application Suite → Core
QA Contact: general
Comment 1•18 years ago
|
||
My guess is that this is from the switch to build with cairo by default. Printing with cairo wasn't working the last time I tried, though I'm not sure of its current status.
*** Bug 334000 has been marked as a duplicate of this bug. ***
But I build with ac_add_options --enable-default-toolkit=gtk2 explicitly in my .mozconfig and getting this error with my own build as well as with "official" nightly builds. Does it use cairo without cairo-gtk2? Just wondering. I don't know much about mozilla these days...:(
Note, this is now fixed. I pulled and built todays cvs and printing works just fine now. Please close this.
Yes, I also confirmed this worked for me (with gtk2) but don't know whether I can set to "Resolve bug, resolution to FIXED"....(I am given permission to do so). But I forgot the policy of mozilla's bugzilla. If I am authorized, I will mark it as "FIXED".
Comment 6•18 years ago
|
||
Resolving per the previous two comments. ["FIXED" is just for when we actually identify and repair the problem.]
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•