Closed Bug 1633126 Opened 4 years ago Closed 4 years ago

Printing from composition does nothing, then fails with Printer Error: "Some printing functionality is not currently available" unexpected rv PrintingChild.jsm

Categories

(MailNews Core :: Printing, defect)

defect

Tracking

(thunderbird76 wontfix, thunderbird77 wontfix, thunderbird78+ affected)

RESOLVED WORKSFORME
Tracking Status
thunderbird76 --- wontfix
thunderbird77 --- wontfix
thunderbird78 + affected

People

(Reporter: thomas8, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [fixed by bug 1639816])

Seen on Windows 10, TB Daily 77.0a1 (2020-04-24) (64-bit)

Printing from compose window is completely disfunctional right now.

STR

  1. compose new message, To: foo@bar.com, Subject: "Test", msg body: "foo bar"
  2. Print (e.g. via Ctrl+P)
  3. Print again

Actual result

  • first print attempt does nothing at all (and no error in console)
  • subsequent print attempt shows error alert (and error in console):
[Printer Error]
Some printing functionality is not currently available
  • console error (from subsequent print attempt)
In Printing:Print:Done handler, got unexpected rv
                        2147746065. PrintingChild.jsm:406

Expected result

  • show print dialogue
  • if there's a selection, allow choosing "Selection" in print dialogue, and if chosen, print selection only

Does this have any automated tests?

Probably related to bug 1620314

reproduces with 76.0b3. I'm assuming it also fails on nightly

Flags: needinfo?(benc)
Keywords: regression
See Also: → 1620314
Summary: Printing from composition does nothing, then fails with Printer Error: "Some printing functionality is not currently available" → Printing from composition does nothing, then fails with Printer Error: "Some printing functionality is not currently available" unexpected rv PrintingChild.jsm

Printing still does not work from "Print Preview" , this feature is still broken in 76.0b3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (non,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → --

77.0b2 prints well from the "Print" command but if you try from the "Print Preview" it will still not work. I am using "Print Preview" only to make sure the settings are right then exiting that and printing directly from the open email without the use of the prevew feature. It's a workaround and takes extra steps but at least I am able to print the documents.

Also running 77.0b2.

Reset print.show_print_progress from true (default) to false and am printing from "Print Preview".

(In reply to John Gallon from comment #7)

Also running 77.0b2.

Reset print.show_print_progress from true (default) to false and am printing from "Print Preview".

However, that stops me changing my print preferences (Canon MG5700).

(In reply to John Gallon from comment #8)

(In reply to John Gallon from comment #7)

Also running 77.0b2.

Reset print.show_print_progress from true (default) to false and am printing from "Print Preview".

However, that stops me changing my print preferences (Canon MG5700).

Incorrect report re print preferences. Am able to print correctly with all printer options with print.show_print_progress set to false.

Still a no for me from the "Print Preview"

(In reply to Thomas D. from comment #1)

Does this have any automated tests?

Highly unlikely IMO - tests would be nice

Severity: -- → S2

related to bug 1625299?

This is working again, I think fixed by bug 1639816.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Whiteboard: [fixed by bug 1639816]
Flags: needinfo?(benc)
You need to log in before you can comment on or make changes to this bug.