Chromium v83 with pepper-flash **RUNS-AS-SPOT**

Message

peebee · #321 Post by **peebee** » Tue 07 Mar 2017, 11:06

simes wrote:Hello peebee,
Sorry to report, I've installed the linked Chromium 56 on lxpup xenial 16.08 and I'm getting the 'Aw, snap!' message on every page in Chromium, even the Chromium settings page. I've used Puppy for years but even so, I wonder whether I've missed something basic... All suggestions welcome.

Thanks,
Simon.

Thanks for reporting - confirmed problem.

Error causing segfault is "Received signal 8 FPE_INTDIV"

Found clue that libharfbuzz was the culprit:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=833953

Made .pet from Open-Mandriva version - attached - seems to cure problem.

Cheers
peebee

simes · #322 Post by **simes** » Tue 07 Mar 2017, 11:20

Hi peebee, that was fast, thank you very much! I confirm that your PET has fixed the problem here.

Simes.

peebee · #323 Post by **peebee** » Tue 14 Mar 2017, 15:52

Update to pepperflash-25.0.0.127

32-bit: chromium_56.0.2924.87+pepper_25.0.0.127.sfs

64-bit: chromium64_56.0.2924.87+pepper_25.0.0.127.sfs

see above for which versions of Puppy Linux are compatible.

sszindian · #324 Post by **sszindian** » Wed 15 Mar 2017, 23:30

peebee...

The new chromium_56.0.2924.87+pepper_25.0.0.127

Gives a 'failed to load plugin'

I only tried it with Slacko64-6.9.6.4 and the site was http://www.prospectingchannel.com/

Reverted back to the chromium 55 version and all works well!

Just thought I'd let you know.

>>>---Indian------>

peebee · #325 Post by **peebee** » Thu 16 Mar 2017, 07:05

sszindian wrote:peebee...

The new chromium_56.0.2924.87+pepper_25.0.0.127

Gives a 'failed to load plugin'

I only tried it with Slacko64-6.9.6.4 and the site was http://www.prospectingchannel.com/

Reverted back to the chromium 55 version and all works well!

Just thought I'd let you know.

>>>---Indian------>

Worked OK for me on the 32-bit version - did you install the 64-bit version ???

I don't run 64-bit as a rule so may take me some time to test.....so can anyone else confirm the problem?

sszindian · #326 Post by **sszindian** » Thu 16 Mar 2017, 12:56

peebee wrote:

Worked OK for me on the 32-bit version - did you install the 64-bit version ???
--------------------------------------------------------------------------------------------------

Yes I used the 64-bit version.

>>>---Indian------>

peebee · #327 Post by **peebee** » Fri 17 Mar 2017, 16:20

AlienBob builds....

chromium_57.0.2987.98+pepper_25.0.0.127_lx.sfs

chromium64_57.0.2987.98+pepper_25.0.0.127_lx.sfs

sszindian · #328 Post by **sszindian** » Fri 17 Mar 2017, 23:32

The AlienBob build...

chromium64_57.0.2987.98+pepper_25.0.0.127_lx.sfs

Did the trick... working well!!

'Thanks peebee!'

>>>---Indian------>

roadkill13 · #329 Post by **roadkill13** » Sun 19 Mar 2017, 19:16

Alien Bob build for 32 bit on TahrPup 6.0.6 fails to load. Attempted launch from terminal window yields the following results:

/usr/lib/chromium/chromium: /lib/libdbus-1.so.3: no version information available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: g_type_check_instance_is_fundamentally_a

DAC324 · #330 Post by **DAC324** » Mon 27 Mar 2017, 19:09

Dear all,

How can I fix the error on Tahrpup 6.0.5:

/usr/lib/chromium-browser-stable/chrome: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Kind regards

DAC324

peebee · #331 Post by **peebee** » Tue 11 Apr 2017, 13:53

Pepperflash update to 25.0.0.148:

chromium_57.0.2987.98-i486+pepper_25.0.0.148_lx.sfs

chromium64_57.0.2987.98+pepper_25.0.0.148_lx.sfs

DAC324 · #332 Post by **DAC324** » Sat 15 Apr 2017, 19:41

Hello,

this version throws the following errors:

/usr/lib/chromium/chromium: /lib/libdbus-1.so.3: no version information available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: g_type_check_instance_is_fundamentally_a

How can this be fixed?

Kind regards,
DAC324

peebee · #333 Post by **peebee** » Sat 15 Apr 2017, 21:40

DAC324 wrote:Hello,

this version throws the following errors:
/usr/lib/chromium/chromium: /lib/libdbus-1.so.3: no version information available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: g_type_check_instance_is_fundamentally_a
How can this be fixed?

Kind regards,
DAC324

On which pup????

see http://www.murga-linux.com/puppy/viewto ... 521#935521

Only runs on "modern" pups as described.

DAC324 · #334 Post by **DAC324** » Sat 15 Apr 2017, 22:00

peebee wrote:
DAC324 wrote:Hello,

this version throws the following errors:
/usr/lib/chromium/chromium: /lib/libdbus-1.so.3: no version information available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: g_type_check_instance_is_fundamentally_a
How can this be fixed?

Kind regards,
DAC324
On which pup????

see http://www.murga-linux.com/puppy/viewto ... 521#935521

Only runs on "modern" pups as described.

TahrPup 6.0.5 - it is, unfortunately, not listed in the linked posting. Apparently, TahrPup is also considered "old".

Kind regards,
DAC324

Mike Walsh · #335 Post by **Mike Walsh** » Sat 15 Apr 2017, 22:32

Hi, DAC324.

Mm. It's a well-known fact that Chromium (upon which a multitude of other browsers are based...including Chrome itself) is always compiled under the newest versions of the glibc (the general 'C' library). peebee's been having various problems with recent releases because of this.

Google themselves re-compile it for Chrome under a much older glibc to maintain compatibility for the largest possible user-base. As do the builders of SlimJet, Iron and Vivaldi (all of which are Chromium-based, and all of which are available here on the forums.)

Just FYI.

Mike.

Moat · #336 Post by **Moat** » Sat 15 Apr 2017, 22:54

Hmmm... If you haven't already done it - I recall TahrPup has an updated glibc available in either Quickpet or the Tahr updates app (??). I also recall using it (i.e. - updating glibc) on any TahrPup installs I've done, and had no issues with it breaking the system. Although a huge YMMV if you give that a try... back things up first!! Might be worth a shot...

Bob

Mike Walsh · #337 Post by **Mike Walsh** » Sun 16 Apr 2017, 10:20

Morning, Bob.

Moat wrote:If you haven't already done it - I recall TahrPup has an updated glibc available in either Quickpet or the Tahr updates app (??). I also recall using it (i.e. - updating glibc) on any TahrPup installs I've done, and had no issues with it breaking the system.

Is that the one that's supposed to be the repair 'fix' for that vulnerability that was discovered with the glibc, a while back? I put it 'on ice', right at the beginning; I wasn't certain I wanted to use it, since I knew messing around with the glibc was liable to 'break' things if you weren't careful.....

You say you've found it works OK?

Mike.

Moat · #338 Post by **Moat** » Sun 16 Apr 2017, 19:26

Hi Mike -

Mike Walsh wrote:Is that the one that's supposed to be the repair 'fix' for that vulnerability that was discovered with the glibc, a while back? ...

You say you've found it works OK?

DoH! You are right, and it's just a security update - and not a version upgrade (I just checked, and the updated version remains at 2.19). So, likely not applicable to DAC324's issue. Dang it...

And yes - I've never experienced any particular issues after installing the update. Has been working OK for me, anyway...

Kinda' pitiful that an LTS Linux release from only three years ago (and officially supported for two more) is based upon a lib structure that's already treated (abandoned?) as obsolete by application/package builders.

More of that mixed-up, non-collaborative world of Linux, I guess - eh?!

Bob

Mike Walsh · #339 Post by **Mike Walsh** » Sun 16 Apr 2017, 19:53

Moat wrote:Kinda' pitiful that an LTS Linux release from only three years ago (and officially supported for two more) is based upon a lib structure that's already treated (abandoned?) as obsolete by application/package builders. More of that mixed-up, non-collaborative world of Linux, I guess - eh?!

'Nuff said, mate.... but yes, it IS 'pitiful'. And the stupid thing is that these older versions of the glibc are still perfectly functional, of course.

Though I'm certainly not knocking Linux maintainers for trying to maintain the general level of security. Far from it.

Mike.

haywirepc · #340 Post by **haywirepc** » Tue 18 Apr 2017, 13:05

I am using tahrpup linux 6.05 and tried to install this latest 32 bit chromium sfs. Sfs installs, but I get this error when attempting to load chromium :

/usr/lib/chromium/chromium: /lib/libdbus-1.so.3: no version information available (required by /usr/lib/chromium/chromium)
/usr/lib/chromium/chromium: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/lib/chromium/chromium)

Can anyone help me fix this? I have all tahrpup updates installed already.
I don't see glibc 3.4.20 or anything close in the repos.

Desperately want to get this working...

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Chromium v83 with pepper-flash RUNS-AS-SPOT

Re: Aw, snap!

Chromium fixed

chromium_56.0.2924.87+pepper_25.0.0.127

plugin problem

Re: plugin problem

plugin

chromium_57.0.2987.98+pepperflash_25.0.0.127

Chromium 57 64-bit

how do I fix missing library?