Pipelight

Pipelight initializing everytime open browser after reboot

Asked by bowser

Hi,

I was experiencing the same problem as Q243494(unity3d plugin installer can't download files) and the answer to that question solved the problem. But now whenever I start FF after a reboot pipelight would start initializing. I rebooted and started FF in the terminal and here are the outputs

[PIPELIGHT:LIN:unknown]attached to process.
[PIPELIGHT:LIN:unknown] checking environment variable PIPELIGHT_FLASH_CONFIG.
[PIPELIGHT:LIN:unknown] searching for config file pipelight-flash.
[PIPELIGHT:LIN:unknown] trying to load config file from '/home/bee/.config/pipelight-flash'.
[PIPELIGHT:LIN:unknown] trying to load config file from '/etc/pipelight-flash'.
[PIPELIGHT:LIN:unknown] trying to load config file from '/usr/share/pipelight/configs/pipelight-flash'.
[PIPELIGHT:LIN:unknown] sandbox not found or not installed!
[PIPELIGHT:LIN:flash] using wine prefix directory /home/bee/.wine-pipelight/.
[PIPELIGHT:LIN:flash] checking plugin installation - this might take some time.
[install-dependency] wine-flash-installer is already installed in '/home/bee/.wine-pipelight/'.
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
[PIPELIGHT:WIN:flash] Read dllPath 'C:\windows\system32\Macromed\Flash' and dllName 'NPSWF32_12_0_0_44.dll' from registry
[PIPELIGHT:WIN:flash] embedded mode is on.
[PIPELIGHT:WIN:flash] windowless mode is off.
[PIPELIGHT:WIN:flash] linux windowless mode is off.
[PIPELIGHT:WIN:flash] force SetWindow is off.
[PIPELIGHT:WIN:flash] unity hacks is off.
[PIPELIGHT:WIN:flash] window class hook is on.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
[PIPELIGHT:WIN:flash] replaced API function CreateWindowExA.
[PIPELIGHT:WIN:flash] replaced API function CreateWindowExW.
[PIPELIGHT:WIN:flash] replaced API function TrackPopupMenuEx.
[PIPELIGHT:WIN:flash] replaced API function TrackPopupMenu.
[PIPELIGHT:LIN:flash] ../common/common.c:162:receiveCommand(): unable to receive data within the specified timeout.
[PIPELIGHT:LIN:flash] basicplugin.c:117:attach(): error during the initialization of the wine process - aborting.
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
err:mscms:DllMain Wine was built without support for liblcms2, expect problems
[PIPELIGHT:WIN:flash] init successful!

Is this expected behaviour? Is there a way to stop this? (and should I if there is a way?)

Thanks.

Question information

Language:
English Edit question
Status:
Answered
For:
Pipelight Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Sebastian Lackner (slackner) said : 		#1

Hi,

its expected that the browser loads Pipelight, even when its not used directly.

Browsers usually load the plugins shortly after the startup, to speed up the time later when they're really needed. Pipelight stays loaded into the memory, but will not be used until its required later.

If it doesn't start up too slow and everything else works you can savely ignore all these messages. If you don't want that Pipelight is running always in the background or your browser is too slow, you could for example use multiple browser profiles, and use the Windows version of Flash/Unity/... only when its really required. If necessary we can provide you with some additional instructions how to setup everything appropriately.

Sebastian

Revision history for this message
bowser (bwbernard-wong1) said : 		#2

Hi,

Thanks for the answer. am curious only because it didn't happen before until after I ran the commands "sudo pipelight-plugin --update" and "sudo pipelight-plugin --create-mozilla-plugins" to fix unity3d last night.

 No, it is not too slow and since it is done only in the begining of a session (instead of restarting browser) I think it is ok. But for future reference additional intsructions for proper management of piplelight plugins would be great.

Thanks.

Revision history for this message
bowser (bwbernard-wong1) said : 		#3

Hi,

I just notice that this doesn't happen in my other Ubuntu 13.10 install even though I had run the same commands to update pighlight.

The difference is that in this install I have reset firefox using Help > Troubleshooting Information > Reset Firefox as things are getting a bit cluttered. When pipelight is initializing the browser grew dim momentarily (only a few seconds) just like whenever silverlight is first loaded for Netflix. Other than that everything is fine and this only happens at first launch of the browser after a reboot.

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

Hi,

the standard behavior of Firefox is to save the plugin information into a file called pluginreg.dat which is stored inside your Firefox profile directory. The plugin will only be loaded when either the timestamp of the plugin file changes or the plugin is actually requested by a website.

As long as you do not call "pipelight-plugin --create-mozilla-plugins" or delete the pluginreg.dat file on every reboot, Firefox should only load Pipelight when it's actually necessary. Nevertheless, this is completely controlled by the browser and Pipelight does not have any influence on this, so you may get a better answer by asking the Firefox guys instead. Maybe there is another event which triggers a load on every start. This may even be caused by a browser extension.

Michael

Revision history for this message
bowser (bwbernard-wong1) said : 		#5

Hi, Thanks for the reply. I am sure it had to do with the profile change. do you think uninstalling and reinstalling piplelight would help? ( i.e sudo apt-get reinstall..)

Revision history for this message
Sebastian Lackner (slackner) said : 		#6

I don't think it can help in such a case. For me it sounds more like there is a problem with your existing firefox profile.

If you don't have any important bookmarks or things like that, I would suggest you to reset your firefox profile like described here:
https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems
please note that when using this method you will loose all the data (like bookmarks, saved passwords, ...) stored in it.

Sebastian

Revision history for this message
bowser (bwbernard-wong1) said : 		#7

Actually it happens after I did just that to reset my profile. :) But it will keep the bookmarks and opentabs. Never mind, it is not a big deal. :)

Can you help with this problem?

Provide an answer of your own, or ask bowser for more information if necessary.

To post a message you must log in.