Chrome Version (from the about:version page): 6.0.489.0 (55370) Is this the most recent version: Yes (SVN) OS + version: Gentoo (current) CPU architecture (32-bit / 64-bit): 64-bit Window manager: KDE 4 The latest SVN (self compiled from source) appears to be looking for libpdf.so in the chromium directory on startup and every consecutive page load. 6::ERROR:base/nativelibrarylinux.cc(28) dlopen failed when trying to open /mnt/local/source/chromium/builds/chromium-55370/libpdf.so: /mnt/local/source/chromium/builds/chromium-55370/libpdf.so: cannot open shared object file: No such file or directory As far as I'm aware the libpdf library isn't (yet) included in the svn repository, and I have even disabled this plugin in the chrome://plugins/ So, if the browser was built without libpdf.so, doesn't include the libpdf.so, and even has this disabled, surely it should not be trying to load it with every action? On a side note: I wouldn't mind having libpdf support, any clues as to how/if I can build this in myself (Gentoo Linux AMD64), or is this not (yet) open source?

• Chromium Libpdf.so Download Free
• Chromium Libpdf.so Download Windows 10
• Chromium Libpdf.so Download Full

Processing So it's not open-source and even the binary is not available separately. Only as a part of the google-chrome download which is only available for rpm- or deb-based linux distributions. If I were to build chromium, then download a chrome.deb or.rpm, extract it and toss everything but the libpdf.so, then arrange for it to run (since it won't just because of sonames of what it's linked against) with chromium.

Would the I be violating any license? In other words: Is it possible at all to use chromium with this PDF plugin given the willingness to sell my soul? Processing The following revision refers to this bug: - 2010-08-10 12:56:51 -0700 (Tue, 10 Aug 2010) 12 lines Changed paths: M pepper: don't warn if PDF plugin is unavailable We preload plugins before we sandbox, then later attempt to fully load them once we're sandboxed. We can't ask whether the plugin exists at the second point because we don't have disk access at that point.

Chromium Libpdf.so Download Free

Chromium Libpdf.so Download Windows 10

Chromium Libpdf.so Download Full

So instead, the first time we're asked about plugins (before we're sandboxed), record whether the plugin is actually available and use that to skip loading it in the second pass. BUG= Review URL.