Here is my setup:

1. Chromium browser: Version 37.0.2062.58 Ubuntu 14.04 (286351) (64-bit)

2. Okular 0.19.2 under KDE 4.13.2 in Kubuntu 14.04 (trusty)

3. kpartsplugin 20120605-1 is installed.

4. xdg-open opens up a PDF file in okular.

5.

Code: Select all

xdg-mime query default application/pdf

gives

Code: Select all

okularApplication_pdf.desktop

Yet with these settings, chromium browser does not open a PDF in okular (whether standalone or embedded) but instead asks where to save the file.

I am asking this question under okular in the hope that someone could direct me elsehwere if necessary to track the cause of this problem.

Thank you.

I don't think Chrome(ium) is kpartsplugin aware

(caveat never tested and know nothing about but) seems you need okularplugin http://andre.frimberger.de/index.php/li ... and-opera/

google01103 wrote:I don't think Chrome(ium) is kpartsplugin aware

(caveat never tested and know nothing about but) seems you need okularplugin http://andre.frimberger.de/index.php/li ... and-opera/

I have followed the instructions at the above site successfully and have this symlink:

Code: Select all

/usr/lib/chromium-browser/plugins/libokularplugin.so -> /usr/lib/libokularplugin.so

However, I cannot get chromium to recognize the plugin, let alone activate it by allowing it always.

I have left a comment for André Frimberger at his website for the above plugin and hope he will reply.

Chromium has removed support for NPAPI based plugins that's why it won't work, theres pretty much nothing you can do other than hope that somebody writes a pepper-based plugin or complain to the chromium devs (which I'm sure has been done a load of times so search their bugtracker for a reasoning)

V1del wrote:Chromium has removed support for NPAPI based plugins that's why it won't work, theres pretty much nothing you can do other than hope that somebody writes a pepper-based plugin or complain to the chromium devs (which I'm sure has been done a load of times so search their bugtracker for a reasoning)

Thank you. I have come to the same realization after searching the Web for some time. Google's (or Chromium's) rationale is laid out here:

http://www.chromium.org/nativeclient/getting-started/getting-started-background-and-basics

and here:

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/xEbgvWE7wMk

I trust that the solution for me is to download and use this extension with chromium (hoping it is as good as okular for PDFs):

https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm

Thanks for all the help.