Closed
Bug 1175645
Opened 10 years ago
Closed 1 year ago
Printing stops working on a particular tab - "Some printing functionality is not currently available."
Categories
(Core :: Printing: Setup, defect)
Core
Printing: Setup
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| e10s | - | --- |
People
(Reporter: jrmuizel, Assigned: mconley)
Details
I got this after trying to print to pdf the first time and it seemed to fail.
I get the message:
"Some printing functionality is not currently available."
Other tabs seem fine.
Here's the relavant browser console:
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
TypeError: printSettings is null browser-content.js:501:0
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
TypeError: printSettings is null browser-content.js:501:0
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
In Printing:Print:Done handler, got unexpected rv
2147746065. browser-content.js:491:0
TypeError: printSettings is null browser-content.js:501:0
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
In Printing:Print:Done handler, got unexpected rv
2147746065. browser-content.js:491:0
TypeError: printSettings is null browser-content.js:501:0
AuthenticationService.Authenticate
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
TypeError: printSettings is null browser-content.js:501:0
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
In Printing:Print:Done handler, got unexpected rv
2147746065. browser-content.js:491:0
TypeError: printSettings is null browser-content.js:501:0
Use of getAttributeNode() is deprecated. Use getAttribute() instead. 9fb342f82d6ce91f1ebf885303388390.js:82:0
[Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIPrintSettingsService.defaultPrinterName]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 426" data: no] browser-content.js:437:0
In Printing:Print:Done handler, got unexpected rv
2147746065. browser-content.js:491:0
TypeError: printSettings is null
| Reporter | ||
Updated•10 years ago
|
tracking-e10s:
--- → ?
Comment 1•10 years ago
|
||
Jeff, can you confirm this is e10s only by trying to reproduce in a non-e10s windowed tab?
Flags: needinfo?(jmuizelaar)
| Reporter | ||
Comment 2•10 years ago
|
||
(In reply to [:tracy] Tracy Walker - QA Mentor from comment #1)
> Jeff, can you confirm this is e10s only by trying to reproduce in a non-e10s
> windowed tab?
I don't know how to reproduce this.
Flags: needinfo?(jmuizelaar)
Updated•10 years ago
|
Updated•10 years ago
|
Assignee: nobody → mconley
| Assignee | ||
Comment 3•10 years ago
|
||
I finally hit this.
I get this error message when I attempt to print while a print job is already in progress - for example, if I attempt to print a large PDF, and the layout engine is still figuring it out before we've sent it off to the spool, if I try to print during this window of time, I see the error message.
| Assignee | ||
Comment 4•10 years ago
|
||
I know it's been a while jrmuizel, but do you remember which page you were on when you hit this?
Flags: needinfo?(jmuizelaar)
| Assignee | ||
Comment 6•10 years ago
|
||
Alright, well, here's what (I think) happened.
Each nsDocumentViewer can have a single mPrintEngine (which is an nsPrintEngine). The mPrintEngine is supposed to exist for the duration of a print or print preview operation, and then it is destroyed. The mPrintEngine has a GetIsPrinting method for whether or not a print is currently in progress.
If the user attempts to print while the engine is still in the process of printing the page in a different job, we hit this:
https://hg.mozilla.org/mozilla-central/file/2ddec2dedced/layout/base/nsDocumentViewer.cpp#l3694
Which causes the dialog.
I don't believe this is e10s-specific, unless, for some reason, the print engine somehow got stuck or never completed its print operation.
But for now, I think this is a tracking-e10s-.
Summary: Printing stops working on a particular tab (probably e10s) → Printing stops working on a particular tab
Updated•3 years ago
|
Severity: normal → S3
Comment 7•1 year ago
|
||
Does this still reproduce?
Flags: needinfo?(mconley)
Summary: Printing stops working on a particular tab → Printing stops working on a particular tab - "Some printing functionality is not currently available."
| Assignee | ||
Comment 8•1 year ago
|
||
I don't think we ever got reliable STR here. Let's close this as INCOMPLETE.
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(mconley)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•