Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 49702 "Missing Plugin" displayed even when Chrome PDF viewer plugin is enabled (64-bit)
Starred by 99 users Reported by pavanv@google.com, Jul 20 2010 Back to list
Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2010
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression
M-6

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
What steps will reproduce the problem?
1. Launch Chrome
2. Try to Open any PDF file in Chrome browser

What is the expected output? 
PDF should be rendered

What do you see instead?
"Missing Plugin" is displayed instead

This happens on Open SUSE 64 bit machine, using 6.0.472.0 build
 
pdf-bug.png
193 KB View Download
Same thing happens with Chromium 6.0.472.0 (52985) Ubuntu 10.04 (32 bit)
Labels: Mstone-6
Comment 4 by pavanv@google.com, Jul 21 2010
Note: This doesn't happen on Windows.
Since this is Linux only, assigning to evanm.
Comment 6 by evan@chromium.org, Jul 21 2010
Summary: "Missing Plugin" displayed even when Chrome PDF viewer plugin is enabled (64-bit) (was: NULL)
Do we even have a 64 bit version of our plugin?  I haven't been following...
Hrm. Good question :)  +sanjeevr since jam is OOO
This is a regression when we moved to Pepper v2. The PDF plugin does not load in the sandbox on Linux. Adding Viet-Trung because he said he is looking into this.
Here's a patch which should fix the problem:

http://codereview.chromium.org/3031011

It's not especially nice though. Suggestions on how to make it better welcome.
Comment 10 Deleted
Comment 11 by conroy@google.com, Jul 22 2010
looks like this should be merged with issue 49800
Comment 12 Deleted
Comment 13 Deleted
Comment 14 Deleted
Comment 15 Deleted
Can you please merge  Issue 49637 as they are the same issue.
Comment 17 by evan@chromium.org, Jul 25 2010
Issue 49637 has been merged into this issue.
still broken in dev build 6.472.0 
Comment 19 Deleted
The Mac version of this bug is 49800; this is specifically tracking the Linux version.
Comment 21 Deleted
Comment 22 Deleted
Comment 23 by evan@chromium.org, Jul 28 2010
Status: Assigned
since trung wrote the patch, giving him the bug
Committed r53977. Hopefully, it should fix it (there's the possibility of an additional problem, similar to on Mac), so I'll have to check that.
can someone change the title to reflect that 32-bit is affected, too?
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=53977 

------------------------------------------------------------------------
r53977 | viettrungluu@chromium.org | 2010-07-28 10:35:07 -0700 (Wed, 28 Jul 2010) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/zygote_host_linux.cc?r1=53977&r2=53976
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/zygote_main_linux.cc?r1=53977&r2=53976
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/pepper_plugin_registry.cc?r1=53977&r2=53976
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/pepper_plugin_registry.h?r1=53977&r2=53976

Linux: bit hacky way to ensure Pepper plugins get loaded by zygote.

BUG= 49702 
TEST=Integrated PDF plugin should work on Linux Chrome, and --register-pepper-plugins works on Linux even with sandbox enabled.

Review URL: http://codereview.chromium.org/3031011
------------------------------------------------------------------------

Comment 27 Deleted
Comment 28 Deleted
Comment 29 Deleted
Labels: ForMerge
Status: Started
Comment 31 Deleted
Comment 32 Deleted
Comment 33 by evan@chromium.org, Aug 1 2010
Issue 50834 has been merged into this issue.
Labels: Area-Internals
Labels: -Plugins Feature-Plugins
Status: Fixed
Gene put in the final thing required to actually fix this....
Comment 37 by evan@chromium.org, Aug 11 2010
Do we need to cherry-pick this?
I think that things should be fine (i.e., gene merged the changes which fixed the PDF plugin on Linux). (Chromium built off 472 would probably be a bit broken, but Chrome should be fine.)

If you (evan) merged the change which broke it, then we need to merge gene's fix to your patch.

If others are building and shipping Chromium off 472, then we should probably merge these two patches.
Issue 52886 has been merged into this issue.
Issue 54487 has been merged into this issue.
Comment 41 by brian@chromium.org, Sep 16 2010
Users of Ubuntu Lucid still seem to be seeing a similar issue as of 9/3: http://www.google.com/support/forum/p/Chrome/thread?tid=3413d3e34dda5cf2&hl=en
Labels: -Regression bulkmove Type-Regression
What steps will reproduce the problem?
1. Launch Chrome
2. Try to Open any PDF file in Chrome browser

What is the expected output? 
PDF should be rendered

What do you see instead?
"Missing Plugin" is displayed instead

This happens on Open SUSE 64 bit machine, using 6.0.472.0 build
Project Member Comment 43 by bugdroid1@chromium.org, Mar 9 2013
Labels: -Feature-Plugins -Mstone-6 -Area-Internals -Type-Regression Type-Bug-Regression M-6 Cr-Internals Cr-Content-Plugins
Project Member Comment 44 by bugdroid1@chromium.org, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 45 by bugdroid1@chromium.org, Apr 6 2013
Labels: Cr-Blink
Project Member Comment 46 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content-Plugins Cr-Internals-Plugins
Comment 47 by laforge@google.com, Jul 24 2013
Cc: -jeffreyc@chromium.org
Sign in to add a comment