Page 15 of 29
Posted: Tue 23 Aug 2016, 22:15
by howling_hound
G'day All,
For what it is worth, several of my older computer single core systems exhibited the freeze up and on occasions displaying the black squares in the four corners of the screen. My solution search returned a recommendation to disable hardware acceleration in the browser "settings". Since this was easy to do, I gave it a try and have had improved results for playback and stability. The black square issue appears to be eliminated. There are still some news web sites with auto loading flash video feeds that occasionally still lock things up to the point of a power cycle but those are much less frequent.
Cheers!
Re: chromium_52.0.2743.116 + pepperflash_22.0.0.209
Posted: Thu 25 Aug 2016, 06:50
by s243a
s243a wrote:
I can't remember if I installed widvine but in July I installed Chromium 43.0.2357.132 and it worked with netflix on tahrpup. FOr me to get it to work I also installed some codec files from the puppy package manager.
There is this one:
chromium-codecs-ffmpeg-extra_50.0.2661.102.files
I'm not sure if this is interesting at all but I would like to report chromecast works with this browser via the following extension:
https://chrome.google.com/webstore/deta ... fd/support
One downside is that when you share a tab with chromecast it stops the audio on your local computer and sends it to the TV. I would like to be able to choose which device (or possibly have both) play/s the audio.
Also it is supposedly possible to share an entire desktop. I haven't figured out how to do this yet.
edit: I found a solution but the task bar comes partly off the screen when I do it.
From redit:
Figured it out.
1) Go to "Back to the Device List" on the Google Cast button in your browser.
2) Click the little chevron/down arrow
3) Click "Cast Entire Screen." Now the audio should play through your laptop; this means you can play it via headphones, or through BlueTooth audio as I'm doing!
Hope this helps.
https://www.reddit.com/r/Chromecast/com ... _keep_the/
Re: chromium_52.0.2743.116 + pepperflash_22.0.0.209
Posted: Wed 31 Aug 2016, 07:52
by s243a
s243a wrote:
I can't remember if I installed widvine but in July I installed Chromium 43.0.2357.132 and it worked with netflix on tahrpup. FOr me to get it to work I also installed some codec files from the puppy package manager.
I'm not sure if this is fixed in the newer releases but the history feature (either cntrl-H or via the menu) is shutting down the browser.
Re: chromium_52.0.2743.116 + pepperflash_22.0.0.209
Posted: Wed 31 Aug 2016, 08:52
by peebee
s243a wrote:s243a wrote:
I can't remember if I installed widvine but in July I installed Chromium 43.0.2357.132 and it worked with netflix on tahrpup. FOr me to get it to work I also installed some codec files from the puppy package manager.
I'm not sure if this is fixed in the newer releases but the history feature (either cntrl-H or via the menu) is shutting down the browser.
Not for me - works fine......
chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
Posted: Fri 09 Sep 2016, 09:09
by peebee
Updated 14-sep-2016
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_23.0.0.162_lx.sfs
chromium64_53.0.2785.92+pepper_23.0.0.162_lx.sfs - only tested on slacko64-6.9.5-uefi
Posted: Fri 09 Sep 2016, 10:54
by peebee
64-bit added - only tested on slacko64-6.9.5-uefi
Sound is fine for me....tests OK on both BBC iPlayer and YouTube
Re: chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
Posted: Sun 11 Sep 2016, 09:45
by Mike Walsh
Morning, peebee.
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
Posted: Sun 11 Sep 2016, 09:59
by peebee
Mike Walsh wrote:I'm guessing this is to do with the glibc issue again, yes?
Hi Mike
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...
Re: chromium-53.0.2785.9+pepperflash_22.0.0.209_lx.sfs
Posted: Sun 11 Sep 2016, 10:10
by 01micko
peebee wrote:Mike Walsh wrote:I'm guessing this is to do with the glibc issue again, yes?
Hi Mike
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...
..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.
http://alien.slackbook.org/blog/priorities/
Posted: Sun 11 Sep 2016, 15:39
by Mike Walsh
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.
Ouch..!
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.
Posted: Tue 13 Sep 2016, 07:48
by gcmartin
Running Chromium 53 from terminal command-line on latest Slacko64 alpha. Messages gotten when running browser is as follows:
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
#
Should this concern me?
Posted: Wed 14 Sep 2016, 06:36
by peebee
Alternative version for tahrpup etc.
Posted: Mon 19 Sep 2016, 12:36
by peebee
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
Posted: Tue 20 Sep 2016, 02:56
by edoc
Since Brave is a Chromium fork - any chance of it for Puppy via a PET or SFS, please?
Thanks ...
Posted: Tue 20 Sep 2016, 06:20
by peebee
edoc wrote:Since Brave is a Chromium fork - any chance of it for Puppy via a PET or SFS, please?
Thanks ...
Only available as 64-bit....
Brave for Linux comes in two versions:
64 bit .deb for Debian/Ubuntu and 64 bit .rpm for Fedora/openSUSE.
Would depend on what dependencies it had been compiled for - if systemd or pulseaudio is a dependency then its a NO-NO....
Posted: Wed 21 Sep 2016, 11:20
by edoc
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 ...
Posted: Wed 21 Sep 2016, 13:52
by peebee
edoc wrote:When I get some time I'll have to try the Brave user forum & ask there. Thanks ...
Quick test on slacko64-6.9.6.1 converting .rpm to .pet shows no missing dependencies however running gives errors:
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)
Doesn't look promising....
Posted: Thu 22 Sep 2016, 22:39
by edoc
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
64-bit - chromium64_53.0.2785.116+pepper_23.0.0.162
Posted: Mon 26 Sep 2016, 08:45
by peebee
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
Chromium 53 hangs when trying to print
Posted: Wed 28 Sep 2016, 06:23
by MagicZaurus
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.