Chromium v83 with pepper-flash **RUNS-AS-SPOT**
64-bit added - only tested on slacko64-6.9.5-uefi
Sound is fine for me....tests OK on both BBC iPlayer and YouTube
Sound is fine for me....tests OK on both BBC iPlayer and YouTube
Last edited by peebee on Mon 17 Oct 2016, 22:34, edited 4 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Re: chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
Morning, peebee.peebee wrote:The world moves on.....
At the moment it looks like chromium-52 will be the last version for the slackware-14.1 / tahrpup era...
chromium-53 is available - tested for the slackware-14.2 (slacko and LxPupSc) and xenialpup era pups
chromium-53.0.2785.92+pepper_22.0.0.209_lx.sfs
chromium64_53.0.2785.92+pepper_22.0.0.209_lx.sfs - only tested on slacko64-6.9.5-uefi
I'm guessing this is to do with the glibc issue again, yes? I've just packaged Chrome 53.0.2785.101 for 64-bit Tahr/Slacko, and it's working fine. I'm posting from it now.
As we all know, specific versions of Chrome have always been taken from the equivalent version's Chromium project source code.....and then re-compiled against an older version of the glibc. At least, that's how it seems to have been done for several years now.
I'm guessing Google have always employed this practice to ensure Chrome's 'use-ability' on the largest possible number of machines.....
How long this practice will continue is, of course, anybody's guess..! We shall see. I never thought I would see the practice evolving (on the Linux side of the fence) where the user has to upgrade the entire OS just to be able to continue to use their favourite browser safely.....
Mike.
Re: chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
Hi MikeMike Walsh wrote:I'm guessing this is to do with the glibc issue again, yes?
Yes
AlienBob (who does the chromium compiles) only seems to have the effort available to compile Chromium-53 for slackware-14.2 / current - maybe somebody else will take up the slackware-14.1 update....we shall see...
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
..and unfortunately for alienbob and his family and the greater community that effort may be cut short as Eric has received notice from his employer.peebee wrote:Hi MikeMike Walsh wrote:I'm guessing this is to do with the glibc issue again, yes?
Yes
AlienBob (who does the chromium compiles) only seems to have the effort available to compile Chromium-53 for slackware-14.2 / current - maybe somebody else will take up the slackware-14.1 update....we shall see...
http://alien.slackbook.org/blog/priorities/
Puppy Linux Blog - contact me for access
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Ouch..!01micko wrote:..and unfortunately for alienbob and his family and the greater community that effort may be cut short as Eric has received notice from his employer.
Alienbob's the same age as me. It's no fun trying to re-engage back in the jobs marketplace at our time of life.....
I wish him the best of luck. He's going to need it.
Mike.
Running Chromium 53 from terminal command-line on latest Slacko64 alpha. Messages gotten when running browser is as follows:Should this concern me?
Code: Select all
# chromium --user-data-dir
libva info: VA-API version 0.38.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: va_openDriver() returns -1
libva info: VA-API version 0.38.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: va_openDriver() returns -1
[1055:1443:0913/031556:ERROR:object_proxy.cc(583)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1055:1098:0913/031600:ERROR:socket_posix.cc(82)] CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol
#
PepperFlash-23.0.0.162:
chromium-53.0.2785.92+pepper_23.0.0.162_lx.sfs
chromium64_53.0.2785.92+pepper_23.0.0.162_lx.sfs
chromium-53.0.2785.92+pepper_23.0.0.162_lx.sfs
chromium64_53.0.2785.92+pepper_23.0.0.162_lx.sfs
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Alternative version for tahrpup etc.
UPDATED 11-oct-16
chromium_53.0.2785.116+pepper_23.0.0.185.sfs
This version of chromium comes from the OpenMandriva project
It appears to work on:
tahrpup-6.0.5 and derivatives (LxPupTahr-15.12.1 and X-Tahr-2.0)
It also works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.1
LxPupSc-16.09.3
It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
LxPupPrecise-15.09.1
It's also a bit smaller (10MB) than the AlienBob Slackware builds.
Please test and report any issues.
64-bit version in later post
chromium_53.0.2785.116+pepper_23.0.0.185.sfs
This version of chromium comes from the OpenMandriva project
It appears to work on:
tahrpup-6.0.5 and derivatives (LxPupTahr-15.12.1 and X-Tahr-2.0)
It also works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.1
LxPupSc-16.09.3
It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
LxPupPrecise-15.09.1
It's also a bit smaller (10MB) than the AlienBob Slackware builds.
Please test and report any issues.
64-bit version in later post
- Attachments
-
- Screenshot.png
- (121.54 KiB) Downloaded 1440 times
Last edited by peebee on Tue 11 Oct 2016, 22:38, edited 5 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Only available as 64-bit....edoc wrote:Since Brave is a Chromium fork - any chance of it for Puppy via a PET or SFS, please?
Thanks ...
Would depend on what dependencies it had been compiled for - if systemd or pulseaudio is a dependency then its a NO-NO....Brave for Linux comes in two versions:
64 bit .deb for Debian/Ubuntu and 64 bit .rpm for Fedora/openSUSE.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I've tried several Search queries & so far nothing re. Brave & either pulseaudio or systemd have shown up.
When I get some time I'll have to try the Brave user forum & ask there.
Thanks ...
When I get some time I'll have to try the Brave user forum & ask there.
Thanks ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Quick test on slacko64-6.9.6.1 converting .rpm to .pet shows no missing dependencies however running gives errors:edoc wrote:When I get some time I'll have to try the Brave user forum & ask there. Thanks ...
Code: Select all
# brave
An uncaught exception occurred in the main process Uncaught Exception:
Error: libgnome-keyring.so.0: cannot open shared object file: No such file or directory
at Error (native)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20)
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:181:18)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/share/brave/resources/app.asar/node_modules/keytar/lib/keytar.js:4:12)
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Is it a complex process to make JavaScript available where it's looking for it?
I'm a long way from even elementary coding any more - beyond some HTML & CSS.
EDIT: Just posted a question to Twitter copied to Brave - hopefully someone there will look here and offer a solution.
Thanks - David
I'm a long way from even elementary coding any more - beyond some HTML & CSS.
EDIT: Just posted a question to Twitter copied to Brave - hopefully someone there will look here and offer a solution.
Thanks - David
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
64-bit - chromium64_53.0.2785.116+pepper_23.0.0.162
Updated 11-oct-2016
64-bit "OpenMandriva" build:
chromium64_53.0.2785.116+pepper_23.0.0.185.sfs
Tested on slacko64_6.9.6.1
and after being converted on xenialpup64-7.0.7
64-bit "OpenMandriva" build:
chromium64_53.0.2785.116+pepper_23.0.0.185.sfs
Tested on slacko64_6.9.6.1
and after being converted on xenialpup64-7.0.7
Last edited by peebee on Tue 11 Oct 2016, 22:31, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 107
- Joined: Mon 05 Jan 2009, 17:35
Chromium 53 hangs when trying to print
I'm using chromium_53.0.2785.116+pepper_23.0.0.162.sfs (from the OpenMandriva Project) on Tahrpup 6.0.5.
I observed that Chromium will hang when I try to print a page from the browser directly. Choosing to save as PDF in the print dialog is fine and later printing the PDF is also fine. Maybe a newer version of CUPS is required. Here CUPS is 1.4.8.
No big issue, just in case somebody else experiences the same problem.
So far everything else seems to be working fine.
I observed that Chromium will hang when I try to print a page from the browser directly. Choosing to save as PDF in the print dialog is fine and later printing the PDF is also fine. Maybe a newer version of CUPS is required. Here CUPS is 1.4.8.
No big issue, just in case somebody else experiences the same problem.
So far everything else seems to be working fine.
Re: 64-bit - chromium64_53.0.2785.116+pepper_23.0.0.162
Cool!peebee wrote:64-bit "OpenMandriva" build:
chromium64_53.0.2785.116+pepper_23.0.0.162.sfs
Tested on slacko64_6.9.6.1
and after being converted on xenialpup64-7.0.7
I wonder when Kernel 4.8rc will be used as it opens up the possibility of use on tablets such as the Chuwi Hi12.
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
chromium_54.0.2840.59+pepper_23.0.0.207
UPDATED 09-nov-2016
***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***
chromium_54.0.2840.59+pepper_23.0.0.207.sfs
chromium64_54.0.2840.59+pepper_23.0.0.207.sfs
This version of chromium comes from the OpenMandriva project
Works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.4
LxPupSc-16.10.1
slacko64-6.9.6.4
LxPup64-16.10.1
It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***
chromium_54.0.2840.59+pepper_23.0.0.207.sfs
chromium64_54.0.2840.59+pepper_23.0.0.207.sfs
This version of chromium comes from the OpenMandriva project
Works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.4
LxPupSc-16.10.1
slacko64-6.9.6.4
LxPup64-16.10.1
It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
Last edited by peebee on Mon 12 Dec 2016, 11:35, edited 2 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Updated to pepperflash 23.0.0.207 - Adobe Security Bulletin
Last edited by peebee on Sat 12 Nov 2016, 07:38, edited 4 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 170
- Joined: Wed 06 Aug 2014, 07:12
Re: Alternative version for tahrpup etc.
So yet that's are be worked on My Tahr build (Tahr Lite 6.1 with Willy X.org Port),But if be will more modulated that's will be pack at .SFS with:peebee wrote:UPDATED 11-oct-16
chromium_53.0.2785.116+pepper_23.0.0.185.sfs
This version of chromium comes from the OpenMandriva project
It appears to work on:
tahrpup-6.0.5 and derivatives (LxPupTahr-15.12.1 and X-Tahr-2.0)
It also works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.1
LxPupSc-16.09.3
It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
LxPupPrecise-15.09.1
It's also a bit smaller (10MB) than the AlienBob Slackware builds.
Please test and report any issues.
64-bit version in later post
1. libnspr4 [/usr/lib]
2. libnss3 [/usr/lib]
3. libnss3-nssdb [/etc and /var]
but Chromium 54 doesn't be works on Tahr because that's depends at Xenial libraries as libpng16 anyway'
chromium_54.0.2840.100+pepper_23.0.0.207
UPDATED 19-nov-16
Based on AlienBob builds:
For 32 bit slackware-14.2 and xenial pups only:
chromium_54.0.2840.100+pepper_23.0.0.207_lx.sfs
For 64 bit slackware-14.2 pups only:
chromium64_54.0.2840.100+pepper_23.0.0.207_lx.sfs
Widevine plugin for 64-bits
Based on AlienBob builds:
For 32 bit slackware-14.2 and xenial pups only:
chromium_54.0.2840.100+pepper_23.0.0.207_lx.sfs
For 64 bit slackware-14.2 pups only:
chromium64_54.0.2840.100+pepper_23.0.0.207_lx.sfs
Widevine plugin for 64-bits
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64