Same thing happens with Chromium 6.0.472.0 (52985) Ubuntu 10.04 (32 bit)

(No comment was entered for this change.)

(No comment was entered for this change.)

Note: This doesn't happen on Windows.

Since this is Linux only, assigning to evanm.

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.

looks like this should be merged with  issue 49800 

Can you please merge   Issue 49637  as they are the same issue.

 Issue 49637  has been merged into this issue.

still broken in dev build 6.472.0 

The Mac version of this bug is 49800; this is specifically tracking the Linux version.

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
------------------------------------------------------------------------

(No comment was entered for this change.)

 Issue 50834  has been merged into this issue.

(No comment was entered for this change.)

(No comment was entered for this change.)

Gene put in the final thing required to actually fix this....

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.

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

<b>What steps will reproduce the problem?</b>
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?
&quot;Missing Plugin&quot; is displayed instead

This happens on Open SUSE 64 bit machine, using 6.0.472.0 build