> New chrome seems to source /etc/chrome.d/, so adding the same contents to a
> file
> such as /etc/chrome.d/pepperflashplugin-nonfree.sh seems to do the trick.
s/chrome.d/chromium.d/
Yes, this is the intended new approach for altering chromium's
environment before it gets launched.
Best wishes
On Mon, Jun 02, 2014 at 09:00:21PM -0400, Michael Gilbert wrote:
> What flags are you setting to make it work?
The package pepperflashplugin-nonfree adds these lines to /etc/chromium/default
:
| # part for pepperflashplugin-nonfree : begin
|
| flashso="/usr/lib/pepperflashplugin-nonfre
On Mon, Jun 2, 2014 at 2:37 PM, Bart Martens wrote:
> Hi Michael,
>
> See #748519, no longer shipping /etc/chromium/default in chromium breaks
> pepperflashplugin-nonfree. Do you have suggestions on how to deal with this ?
What flags are you setting to make it work?
A gyp flag like enable_plugin
Hi Michael,
See #748519, no longer shipping /etc/chromium/default in chromium breaks
pepperflashplugin-nonfree. Do you have suggestions on how to deal with this ?
Regards,
Bart Martens
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
4 matches
Mail list logo
