151902 - Can't print mail messages

Status: VERIFIED WORKSFORME

(MailNews Core :: Printing, defect)

Description

[Peter Trudelle]

Using today's commercial branch build on Win2K:

Open mail, select a message in thread pane.
Print.
Expected results: Print dialog -> printout.
Actual results: Busy cursor for a fraction of a second, no dialog, no printout.

Tried focussing in message pane first, printing from a separate message
window,using Print toolbar, Print menu item.  Same results

Comment 1

[dcone (gone)]

-->

Comment 2

[rods (gone)]

I did a pull this morning of the branch (not commercial) and it prints fine for me.

Comment 3

[rods (gone)]

WFM

Comment 4

[Peter Trudelle]

Well, I still can't print mail messages using the 6/21 verification build, but
I'll keep trying later builds.  Do you think it is a commercial-only defect?

Comment 5

[rods (gone)]

Folks who have had problems printing, often solve it by reinstalling the printer
driver(s). We still aren't sure why you need to do this (i.e. how the driver
gets corrupted.

Comment 6

[Peter Trudelle]

I don't see how that could be the problem, since I can print everything else
fine, including web pages; it is only mail messages that are a no-op.

Comment 7

[scottputterman]

Esther, can you reproduce this?  FYI, I'm using today's commercial branch build
and I get a print dialog.  Peter, are there any exception in the js console?

Comment 8

[Peter Trudelle]

No exceptions appear as a result of this command  There were a couple before I
tried it on one instance, but on another there were none before or after.  If
I'm the only one seeing this, then perhaps this is yet another corrupted profile
issue.

Comment 9

[Peter Trudelle]

This operation also appears to create zombie windows that prevent normal app
shutdown, as reported in bug 154191

Comment 10

[Peter Trudelle]

Once I set the proper prefs, I get this error on the JS console:
Error: window.arguments[3] has no properties
Source File: chrome://messenger/content/msgPrintEngine.js
Line: 64

Comment 11

[rods (gone)]

What do you mean by "set the proper prefs"? The [3] param is the print settings,
that is very strange that is null.

Comment 12

[Peter Trudelle]

Prefs needed to get app errors on the JS console in NS verification builds.

Comment 13

[esther]

Peter, is this still a problem for you?  I don't see any mention that it is
working for you now.  I took the 6-21 branch build and could print mail messages
and can still print with the 7-9 branch build.  I'm on a winxp.  Please call my
and I'll stop by to see this.

Comment 14

[esther]

I saw Peter's problem, but it's a profile specific problem that we can't
isolate.  Other Profiles print mail messages fine.  At this time verifying wfm
and will work with Peter's profile later if requested to isolate and write a new
bug.