Page 1 of 1
Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 30 Nov 2016, 16:58
by Ed_P
Links such as this
http://www.uclick.com/client/adn/pff/ return an Adobe Flash Player download failed error.
Code: Select all
guest@porteus:~$ ls -lgh /mnt/live/memory/images/
total 0
drwxr-xr-x 7 root 83 Nov 27 23:39 000-kernel.xzm/
drwxrwxrwt 20 root 281 Nov 27 21:32 001-core.xzm/
drwxr-xr-x 10 root 143 Nov 27 21:38 002-xorg.xzm/
drwxr-xr-x 11 root 141 Nov 29 17:50 003-cinnamon.xzm/
drwxr-xr-x 7 root 82 Oct 14 13:17 07-printing-x86_64-26.11.2016.xzm/
drwxr-xr-x 9 root 85 Nov 30 06:19 changes/
drwxr-xr-x 5 root 49 Nov 20 16:40 firefox-50.0-x86_64-1.xzm/
drwxr-xr-x 4 root 37 Nov 28 07:40 flashplayer-plugin-23.0.0.207-x86_64-1.xzm/
drwxr-xr-x 6 root 60 Nov 20 16:49 google-chrome-54.0.2840.100-x86_64-1.xzm/
drwxr-xr-x 3 root 26 Nov 20 16:51 pepperflash-23.0.0.162-x86_64-1.xzm/
guest@porteus:~$
guest@porteus:~$ ./bootmode.sh x
Boot device: /dev/sda5
Device format: "ntfs"
Boot ISO: /ISOs/Porteus-CINNAMON-v3.2.1-x86_64.iso
Changes to be saved to a save.dat file.
Save.dat: /porteus3.2/changes/porteussave.dat
Changes: changes=EXIT:/porteus3.2/changes/porteussave.dat
Cmdline: quiet from=/ISOs/Porteus-CINNAMON-v3.2.1-x86_64.iso kmap=us changes=EXIT:/porteus3.2/changes/porteussave.dat extramod=/porteus3.2/Modules reboot=cold ramsize=80%
guest@porteus:~$
Could the Firefox Flashplayer module be conflicting with the Chrome Pepperflash module? I tried booting without the pepperflash module but had the same problem.
-update-
Same situation in AF mode.
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 04:28
by Ed_P
From what I've found on the web so far, Adobe Flashplayer is BUILT into google-chrome!! So I don't need the pepperflash module. And in the about:plugins window Adobe Flash is present.
chrome://plugins window
Code: Select all
Adobe Flash Player - Version: 23.0.0.185
Shockwave Flash 23.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 23.0 r0
Version: 23.0.0.185
Location: internal-not-yet-present
Type: PPAPI (out-of-process)
Disable
MIME types:
MIME type Description File extensions
application/x-shockwave-flash Shockwave Flash
.swf
application/futuresplash FutureSplash Player
.spl
Disable Always allowed to run
hmmmm "Location: internal-not-yet-present"
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 06:10
by ncmprhnsbl
Ed_P wrote:From what I've found on the web so far, Adobe Flashplayer is BUILT into google-chrome!
yup
the pepperflash plugin is for chromium and opera (and vivaldi?)(it comes
from google-chrome)
theres also a thing called freshplayer-plugin that allows pepperflash to be used by firefox...thats somewhat redundant now thar adobe is supporting linux with new versions now....
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 06:18
by Ed_P
^ Unfortunately, based on the "Location: internal-not-yet-present" statement I suspect that the Flashplayer is removed from the Chrome module. Therefore requiring the pepperflash module.
In searching and testing I find that the missing file is named: libpepflashplayer.so and can be found:
Code: Select all
/mnt/live/memory/images/pepperflash-23.0.0.162-x86_64-1.xzm/usr/lib64/PepperFlash/libpepflashplayer.so
/usr/lib64/PepperFlash/libpepflashplayer.so
/home/guest/.config/google-chrome/PepperFlash/23.0.0.207/libpepflashplayer.so
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 08:02
by ncmprhnsbl
Ed_P wrote: I suspect that the Flashplayer is removed from the Chrome module.
nope, its there, just tried some-random-flash-app without any pepperflash module activated(dont even have it) in chrome>works...
dunno what Location: internal-not-yet-present means exactly, but suspect it means they're just not saying where at present..
whoopsie... looks like i'm using a slightly older version :p
https://bbs.archlinux.org/viewtopic.php?id=218428
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 13:45
by ncmprhnsbl
had a closer look:
1. downloaded google-chrome-54.0.2840.100-x86_64-1.xzm and activated it (no other browsers or flash plugins)
2. looked in /.config/google-chrome >> folder: Default, & a couple of files
3.started it
4.looked in ~/.config/google-chrome >> lots of folders... including one called PepperFlash: empty
5.went to
http://www.uclick.com/client/adn/pff/ return an Adobe Flash Player 'updating'
6.looked in ~/.config/google-chrome/PepperFlash >> now we have folder > 23.0.0.207/ libpepflashplayer.so ..etc
7.reloaded uclick.com/client/adn/pff/ >> now tells me 'flash out of date' (smthing like)
8 restarted chrome >> now uclick.com/client/adn/pff/ loads correctly
conclusion: chrome automatically installs pepperflash plugin when it encounters a flash app.. but.. needs to restarted for it to work..
also if you want this plugin to persist you need to either save changes
or make a module of or merge into chrome module: ~/.config/google-chrome/PepperFlash
Re: Porteus 3.2 and Google-Chrome/Pepperflash problem
Posted: 01 Dec 2016, 15:55
by Ed_P
.
Wow!!! 
Nice work
ncmprhnsbl.
Thank you.
ncmprhnsbl wrote:conclusion: chrome automatically installs pepperflash plugin when it encounters a flash app..
Definitely an interesting situation. Did you notice where chrome looks for the plugin? I'm wondering if it downloads it from the 'net or does it look for it on the existing file system?
ncmprhnsbl wrote:also if you want this plugin to persist you need to either save changes
or make a module of or merge into chrome module: ~/.config/google-chrome/PepperFlash
Will definitely be playing around with these approaches. Thank you again
ncmprhnsbl. Definitely appreciate it.
-update-
If I start chrome this way:
Code: Select all
FLASH=/usr/lib64/PepperFlash/
google-chrome-stable --ppapi-flash-path=$FLASH
Flash is available without having to restart chrome. I have to tinker with this some more. Obviously I have the pepperflash module active.