Pipelight

upgrade individual plugins

Asked by monkeybrain2012

Hi, I have a question about upgrading plugins.

There are some websites that normally don't work with system flash (there is a box saying that it needs flash even though flash 11.2 is installed.) e.g cp24.com. Now flash 11.2 would work if I just install pipelight-flash without actually switchingto it, I suppose that is because of widevine.

Today I found that some of these sites had stopped working and displayed the "require flash to play box". They were working before.

I tried the following:
1)disabled pipelight-flash,
2)ran sudo pipelight-plugin --update and
3) re-enabled pipelight-flash
4) ran update-alternatives to switch to pipelight-flash
5) opened Firefox and see the box pipelight-flash installer at work
6) closed firefox and ran update-alternatives to switch back to system flash
I then reopened firefox to check the sites, they still only displayed the box asking for flash to be installed. I checked Firefox's Tools > Addons > Plugin and noted that the pipelight-flash version was still the same as before : 12.0r0

But this worked : I disabled all the plugins, deleted ~/.wine-pipelight , then reinstalled pipelight and re-enabled all the plugins

From Firefox pipelight-flash got upgraded to 13.0r0 and all thses sites work again (with system flash)

I think I must be missing something, there must be a less clumsy way to just update one plugin without having to reinstall pipelight and removing ~/.wine-pipelight How should I have gone about it?

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Pipelight Edit question
Assignee:
No assignee Edit question
Solved by:
monkeybrain2012
Solved:
Last query:
Last reply:
Revision history for this message
Michael Müller (mqchael) said : 		#1

Hi,

the plugin actually got updated after you executed "sudo pipelight-plugin --update" and opened a flash website. The only reason why you still saw the old version number in Firefox, is that Firefox caches the plugin information till the date of the plugin library changes. If you would have done a right click on a flash application you would have seen the 13.0r0 version string.

The Pipelight library only changes between pipelight updates and not plugin updates, so Firefox tends to show wrong information. You can force Firefox reload the information by using "sudo pipelight-plugin --create-mozilla-plugins" which will implicitly change the file time.

Michael

Revision history for this message
monkeybrain2012 (kammon101) said : 		#2

Hi,

Thanks for the quick answer. I have another Ubuntu installation, I updated plugins, switch to pipelight-flash and played a flash video, sure enough right clicking showed flash 13. But after I switched back to system flash and visited the same page it still complained that flash was not installed. But if I reinstall pipelight the site will play in system flash likeI just did in another Ubuntu installation.

Revision history for this message
monkeybrain2012 (kammon101) said : 		#3

Hi, after Firefox plugin gets updated after running "sudo pipelight-plugin --create-mozilla-plugins" and those sites now work.

I have two questions though.

1)If I don't run that command will it get updated when pipelight itself does (through system update)

2)Now that I have created mozilla plugin do I have to do it again if I update pipelight-plugin next time, or will firefox check automatically?

Thanks

Revision history for this message
Michael Müller (mqchael) said : 		#4

Hi,

1) Running "sudo pipelight-plugin --update" only replaces the plugin database with a more recent version from our git repository and verifies whether the file is signed with our Pipelight GPG key. Every release of Pipelight will also ship a current version of this file and the update command is only a short cut if you do not want to wait till the next release. So yes, an update of pipelight will also update all your installed plugin to the current version.

2) Yes you will need to do this every time after manually updating the plugin via the update command, though there is no real big disadvantage in leaving it out. Firefox will only show the wrong version string, but the plugin is updated nevertheless.

Michael

Revision history for this message
monkeybrain2012 (kammon101) said : 		#5

Thanks for the answer. That clears things up.