Page 1 of 1

Built pipelight, how to install?

Posted: 2019-11-10, 01:28
by moonbat
So I built pipelight from source and after some trial and error, it has generated libpipelight.so. How do I add the plugin to my Pale Moon installation, since it's not enough to copy it to /usr/lib/palemoon?

Re: Built pipelight, how to install?

Posted: 2019-11-10, 11:20
by adesh
Create a directory named plugins in your installation and put it there.

Re: Built pipelight, how to install?

Posted: 2019-11-10, 13:59
by moonbat
But if that's the case shouldn't there already be one for the Flash plugin? Tried it just now and it didn't work, i.e. nothing new shown in about:plugins, just the existing Flash. Pale Moon is installed (via package) to /usr/lib/palemoon.

Re: Built pipelight, how to install?

Posted: 2019-11-10, 17:12
by athenian200
Try using:

export MOZ_PLUGIN_PATH=$HOME/plugins

Or something similar to that, replacing $HOME/plugins with whatever directory you installed the plugin into. I've never been able to get plugins working in a portable install of PM on Unix without using that trick. Probably there's a more elegant way, but that way should work. The only time I've ever not had to do that is if it was installed by distribution's package that designated a plugin directory for all browsers that use NPAPI.

Re: Built pipelight, how to install?

Posted: 2019-11-10, 17:15
by Moonchild
moonbat wrote:
2019-11-10, 13:59
But if that's the case shouldn't there already be one for the Flash plugin?
Not necessarily. The browser looks in several places for plugins, not just one.
Also it should have worked putting it in /plugins under the application folder (but you have to restart the browser).

Re: Built pipelight, how to install?

Posted: 2019-11-11, 02:08
by moonbat
athenian200 wrote:
2019-11-10, 17:12
Try using:
export MOZ_PLUGIN_PATH=$HOME/plugins
Didn't work :(
Set it to the default plugin location, i.e. /usr/lib/palemoon/plugins
Moonchild wrote:
2019-11-10, 17:15
The browser looks in several places for plugins, not just one.
Also it should have worked putting it in /plugins under the application folder (but you have to restart the browser).
This didn't work either. I'm using the package built version of PM which is in /usr/lib/palemoon, so I've put my plugins/ directory under that. Is there any other place to put it?
I also checked that the library was correctly built i.e. 32 vs 64-bit-

Code: Select all

libpipelight.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=7c6b606a6306230ccaa32446e390a4784b158fba, not stripped

Re: Built pipelight, how to install?

Posted: 2019-11-11, 06:01
by athenian200
Well, if that didn't work, I think the plugin you built must be incompatible or missing something it requires to work. It's notoriously difficult to troubleshoot this kind of issue.

Could you test whether other plugins work when you put them in those directories? The MOZ_PLUGIN_PATH thing is basically guaranteed to pick it up if it's going to work at all, but when it fails sometimes it just refuses to load it and doesn't explain why. I've also found that sometimes after the first load failure of a plugin, it won't try to load it again when I restart.

Re: Built pipelight, how to install?

Posted: 2019-11-11, 06:34
by moonbat
I only have Flash which is installed as a system package in /usr/lib/adobe-flashplugin. I moved it from there to the folder I had created, and it got picked up and was shown in about:plugins after restarting. So looks like a problem with the way pipelight was built.

Is there a way to log plugin discovery/initialization? Browser console only seems to show javascript errors from loading chrome components.