Print preview email doesn't open. Status line "Print Previewing message..."
Categories
(MailNews Core :: Printing, defect)
Tracking
(Not tracked)
People
(Reporter: felix.schroeter, Unassigned)
References
()
Details
(Whiteboard: [Support])
Comment 1•8 years ago
|
||
| Reporter | ||
Comment 2•8 years ago
|
||
Comment 3•8 years ago
|
||
Comment 4•8 years ago
|
||
Comment 5•7 years ago
|
||
Updated•7 years ago
|
Comment 9•6 years ago
|
||
Sorry for the delay
For everyone included in this bug, please see the URL that Wayne added to the ticket. Here it is again if you can't find it
https://support.mozilla.org/questions/1222914
Please update TB to the latest stable version or try the latest beta, and follow the suggestions in the link above to verify the bug is resolved.
Stable: https://www.thunderbird.net
Updated•6 years ago
|
Comment 10•6 years ago
|
||
OS Windows 10
TB version 60.8.0
Print Preview failure.
Steps to reproduce:
Right-click on a mail and clicked on print preview
Actual results:
A windows flashes in and out of view at speed as if calling the function. At the bottom left corner is shown "print preview: Message" but print preview window does open.
Tests:
- Using 'services.msc' to reset print spooler had no effect.
- Using Thunderbird Safe Mode had same results.
- Uninstalled and reinstalled from fresh version 60.8.0 from these links:
https://www.thunderbird.net/en-US/thunderbird/all/
English (British) for Windows OS.
https://www.thunderbird.net/en-GB/
Still same results for both. - Uninstalled then downloaded and installed from advised beta channel.
Version 69.0b3
Same failure.
Error console information from 60.8.0 version
Error:
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIPrintSettingsService.initPrintSettingsFromPrinter]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/browser-content.js :: getPrintSettings :: line 606" data: no] (unknown)
getPrintSettings chrome://global/content/browser-content.js:606:7
enterPrintPreview chrome://global/content/browser-content.js:756:27
receiveMessage chrome://global/content/browser-content.js:570:9
[Exception... "Component returned failure code: 0x80480002 (NS_ERROR_GFX_PRINTER_NAME_NOT_FOUND) [nsIWebBrowserPrint.printPreview]" nsresult: "0x80480002 (NS_ERROR_GFX_PRINTER_NAME_NOT_FOUND)" location: "JS frame :: chrome://global/content/browser-content.js :: printPreviewInitialize :: line 770" data: no] (unknown)
printPreviewInitialize chrome://global/content/browser-content.js:770:11
TypeError: printPreviewTB is null[Learn More] printUtils.js:348:11
receiveMessage chrome://global/content/printUtils.js:348:11
NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window nsPrompter.js:340
GET
XHR
https://aus5.mozilla.org/update/6/Thunderbird/60.8.0/20190703133823/WINNT_x86-msvc-x64/en-GB/release/Windows_NT%2010.0.0.0.17763.678%20(x64)/ISET:SSE4_2,MEM:16191/default/default/update.xml
[HTTP/2.0 200 OK 359ms]
Error console information from 69.0b3 version:
NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window Prompter.jsm:437
NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window Prompter.jsm:437
openModalWindow resource://gre/modules/Prompter.jsm:437
openPrompt resource://gre/modules/Prompter.jsm:698
alert resource://gre/modules/Prompter.jsm:747
alert resource://gre/modules/Prompter.jsm:60
_displayPrintingError chrome://global/content/printUtils.js:323
receiveMessage chrome://global/content/printUtils.js:328
Comment 11•6 years ago
|
||
Well, print preview works fine for me on TB 68 and TB 69 beta. I think your print settings got themselves into a knot. You should open the config editor and check for print.printer. What you will see are preferences for any installed printers, potentially accumulated over the years (like I have nine ancient printers still in the profile). You should reset all those preferences, or easier, edit the prefs.js file in your profile while TB isn't running. Do this carefully and make a backup of the file.
Or, just create a new text profile (starting thunderbird -p) and see whether the print preview also doesn't work there.
Comment 12•6 years ago
|
||
Correct Jorg - totally in a knot. Printer not detected. Printer driver not detected. Then told not compatible with Windows 10 so ditch printer. But eventually after many attempts got computer to recognise printer and installed everything. Reset all print in config editor and bingo. How Windows 10 duffed that one up is crazy.
Now just need to remove the beta version in order to get Thunderbird back to normal.
Comment 13•6 years ago
|
||
Let's close this one. I'm quite convinced that all these problems are due to bad/old configuration.
| Reporter | ||
Updated•5 years ago
|
Description
•