Print Preview Fails To Load On Google Chrome
up vote
0
down vote
favorite
I recently encountered an issue with Google Chrome where when attempting to print any webpage from Chrome, the print preview never renders (continues to show Loading...
) and continuing with the print attempt does not result in the page being printed.
This problem appears to be isolated to a single computer, when signing into my Chrome profile on another computer the print process works fine.
Additionally, when starting Chrome from the command line and setting the --user-data-dir
flag to something like /tmp/test_profile
, the print functionality works again. However, the problem persists when using Chrome under a guest account.
With the --enable-logging
flag set, I observed several errors that resulted when trying to print:
"Refused to load the script 'chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/elements/viewer-error-screen/viewer-error-screen.html' because it violates the following Content Security Policy directive: "script-src chrome://resources 'self' 'unsafe-eval'".
There are an additional 16 error messages that follow, all referencing other components of the mhjfbmdgcfjbbpaeojofohoefgiehjai
package that failed to load due to the CSP directive.
mhjfbmdgcfjbbpaeojofohoefgiehjai
referenced in the errors refers to the Chrome PDF Viewer browser plugin, which I believe is installed by default by Chrome and is used in generating the print preview.
I have tried disabling and re-enabling the PDF Viewer plugins several times and have disabled all Chrome extensions to make sure that it was not being affected by outside interference from a misbehaving extension. I have also tried reinstalling Chrome itself.
At this point, I suspect that the problem most likely lies in one of the local files associated with my Chrome profile, given that starting Chrome with a non-existent profile from the command line or using my profile from another computer does not reproduce the issue. However, I'm unsure what exact steps to take next towards identifying the cause. If there are any other details I can provide that would be helpful, please indicate them to me.
google-chrome printing
add a comment |
up vote
0
down vote
favorite
I recently encountered an issue with Google Chrome where when attempting to print any webpage from Chrome, the print preview never renders (continues to show Loading...
) and continuing with the print attempt does not result in the page being printed.
This problem appears to be isolated to a single computer, when signing into my Chrome profile on another computer the print process works fine.
Additionally, when starting Chrome from the command line and setting the --user-data-dir
flag to something like /tmp/test_profile
, the print functionality works again. However, the problem persists when using Chrome under a guest account.
With the --enable-logging
flag set, I observed several errors that resulted when trying to print:
"Refused to load the script 'chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/elements/viewer-error-screen/viewer-error-screen.html' because it violates the following Content Security Policy directive: "script-src chrome://resources 'self' 'unsafe-eval'".
There are an additional 16 error messages that follow, all referencing other components of the mhjfbmdgcfjbbpaeojofohoefgiehjai
package that failed to load due to the CSP directive.
mhjfbmdgcfjbbpaeojofohoefgiehjai
referenced in the errors refers to the Chrome PDF Viewer browser plugin, which I believe is installed by default by Chrome and is used in generating the print preview.
I have tried disabling and re-enabling the PDF Viewer plugins several times and have disabled all Chrome extensions to make sure that it was not being affected by outside interference from a misbehaving extension. I have also tried reinstalling Chrome itself.
At this point, I suspect that the problem most likely lies in one of the local files associated with my Chrome profile, given that starting Chrome with a non-existent profile from the command line or using my profile from another computer does not reproduce the issue. However, I'm unsure what exact steps to take next towards identifying the cause. If there are any other details I can provide that would be helpful, please indicate them to me.
google-chrome printing
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently encountered an issue with Google Chrome where when attempting to print any webpage from Chrome, the print preview never renders (continues to show Loading...
) and continuing with the print attempt does not result in the page being printed.
This problem appears to be isolated to a single computer, when signing into my Chrome profile on another computer the print process works fine.
Additionally, when starting Chrome from the command line and setting the --user-data-dir
flag to something like /tmp/test_profile
, the print functionality works again. However, the problem persists when using Chrome under a guest account.
With the --enable-logging
flag set, I observed several errors that resulted when trying to print:
"Refused to load the script 'chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/elements/viewer-error-screen/viewer-error-screen.html' because it violates the following Content Security Policy directive: "script-src chrome://resources 'self' 'unsafe-eval'".
There are an additional 16 error messages that follow, all referencing other components of the mhjfbmdgcfjbbpaeojofohoefgiehjai
package that failed to load due to the CSP directive.
mhjfbmdgcfjbbpaeojofohoefgiehjai
referenced in the errors refers to the Chrome PDF Viewer browser plugin, which I believe is installed by default by Chrome and is used in generating the print preview.
I have tried disabling and re-enabling the PDF Viewer plugins several times and have disabled all Chrome extensions to make sure that it was not being affected by outside interference from a misbehaving extension. I have also tried reinstalling Chrome itself.
At this point, I suspect that the problem most likely lies in one of the local files associated with my Chrome profile, given that starting Chrome with a non-existent profile from the command line or using my profile from another computer does not reproduce the issue. However, I'm unsure what exact steps to take next towards identifying the cause. If there are any other details I can provide that would be helpful, please indicate them to me.
google-chrome printing
I recently encountered an issue with Google Chrome where when attempting to print any webpage from Chrome, the print preview never renders (continues to show Loading...
) and continuing with the print attempt does not result in the page being printed.
This problem appears to be isolated to a single computer, when signing into my Chrome profile on another computer the print process works fine.
Additionally, when starting Chrome from the command line and setting the --user-data-dir
flag to something like /tmp/test_profile
, the print functionality works again. However, the problem persists when using Chrome under a guest account.
With the --enable-logging
flag set, I observed several errors that resulted when trying to print:
"Refused to load the script 'chrome-extension://mhjfbmdgcfjbbpaeojofohoefgiehjai/elements/viewer-error-screen/viewer-error-screen.html' because it violates the following Content Security Policy directive: "script-src chrome://resources 'self' 'unsafe-eval'".
There are an additional 16 error messages that follow, all referencing other components of the mhjfbmdgcfjbbpaeojofohoefgiehjai
package that failed to load due to the CSP directive.
mhjfbmdgcfjbbpaeojofohoefgiehjai
referenced in the errors refers to the Chrome PDF Viewer browser plugin, which I believe is installed by default by Chrome and is used in generating the print preview.
I have tried disabling and re-enabling the PDF Viewer plugins several times and have disabled all Chrome extensions to make sure that it was not being affected by outside interference from a misbehaving extension. I have also tried reinstalling Chrome itself.
At this point, I suspect that the problem most likely lies in one of the local files associated with my Chrome profile, given that starting Chrome with a non-existent profile from the command line or using my profile from another computer does not reproduce the issue. However, I'm unsure what exact steps to take next towards identifying the cause. If there are any other details I can provide that would be helpful, please indicate them to me.
google-chrome printing
google-chrome printing
asked Feb 2 '17 at 14:58
user3351605
10114
10114
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14
add a comment |
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The issue actually appears to lie in the Chrome PDF viewer. I wasn't able to track down the package's location, despite several searches, so I figured I'd try the Chrome Beta Channel to see if it was any better. And it is!
I resolved the issue by updating to the current Beta channel Chrome (currently 57.0.2987.37 beta (64-bit)) on my Mac.
To do the same, go here: https://www.google.com/chrome/browser/beta.html
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1174476%2fprint-preview-fails-to-load-on-google-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The issue actually appears to lie in the Chrome PDF viewer. I wasn't able to track down the package's location, despite several searches, so I figured I'd try the Chrome Beta Channel to see if it was any better. And it is!
I resolved the issue by updating to the current Beta channel Chrome (currently 57.0.2987.37 beta (64-bit)) on my Mac.
To do the same, go here: https://www.google.com/chrome/browser/beta.html
add a comment |
up vote
0
down vote
The issue actually appears to lie in the Chrome PDF viewer. I wasn't able to track down the package's location, despite several searches, so I figured I'd try the Chrome Beta Channel to see if it was any better. And it is!
I resolved the issue by updating to the current Beta channel Chrome (currently 57.0.2987.37 beta (64-bit)) on my Mac.
To do the same, go here: https://www.google.com/chrome/browser/beta.html
add a comment |
up vote
0
down vote
up vote
0
down vote
The issue actually appears to lie in the Chrome PDF viewer. I wasn't able to track down the package's location, despite several searches, so I figured I'd try the Chrome Beta Channel to see if it was any better. And it is!
I resolved the issue by updating to the current Beta channel Chrome (currently 57.0.2987.37 beta (64-bit)) on my Mac.
To do the same, go here: https://www.google.com/chrome/browser/beta.html
The issue actually appears to lie in the Chrome PDF viewer. I wasn't able to track down the package's location, despite several searches, so I figured I'd try the Chrome Beta Channel to see if it was any better. And it is!
I resolved the issue by updating to the current Beta channel Chrome (currently 57.0.2987.37 beta (64-bit)) on my Mac.
To do the same, go here: https://www.google.com/chrome/browser/beta.html
answered Feb 10 '17 at 5:30
Kris Benson
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1174476%2fprint-preview-fails-to-load-on-google-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm getting the same issue. I just disabled the print preview and forced it to use native print menu by default. Also this issue came about in the recent 56.0.2924.87 update. It was fine before this.
– 1110101001
Feb 6 '17 at 5:14