Page 2 of 29

Posted: Tue 17 Sep 2013, 12:42
by z_weld
Hello, I just installed the latest chromium.pet on my macpup550

I managed to open up chromium without issues, but when I got into youtube.com and a couple of seconds after flash tried to play a video, chromium crashed and I got this message..

dont know what it means, just reporting it...

Posted: Tue 17 Sep 2013, 19:43
by peebee
z_weld wrote:Hello, I just installed the latest chromium.pet on my macpup550

I managed to open up chromium without issues, but when I got into youtube.com and a couple of seconds after flash tried to play a video, chromium crashed and I got this message..

dont know what it means, just reporting it...
Hi

No real answers I'm afraid - Macpup550 is based on Precise 5.5 so it may be worth trying an earlier version of Chromium - say 25.

Also, which flashplayer does Macpup come with? If it is an older version it may be worth trying updating to a later version....

Then, Macpup has E17 - it might be worth seeing if the error occurs with vanilla Precise 5.5 (or 5.7.1 as Precise is now).

Cheers
peebee

Chrome 30 sfs

Posted: Mon 21 Oct 2013, 18:37
by peebee
Whilst waiting for the next Chromium to become available on slacky.eu I have made an sfs of Chrome 30.1599.101

This version runs "as is" on Precise 5.7.1 and Upup Raring 3.9.9.2 HOWEVER Slacko 5.6 needs GConf-3.2.5 installing - use the Puppy Package Manager and search for gconf from the Slackware 14.0 Official repository. Adds about 1MB.

The sfs (47MB) can be downloaded from:
chrome-30.0.1599.101-i386-1sl.sfs

If you need a pet - can I suggest that you create a pet from the sfs - just click on the sfs to extract its contents into a folder and then use dir2pet from a terminal to make the folder into a pet.

If you worry about such things, chrome://sandbox indicates that this version is not "adequately sandboxed".

Cheers
peebee

Chromium 30.0.1599.101

Posted: Wed 23 Oct 2013, 08:09
by peebee
The sfs (c. 36MB - xz compressed) of chromium-30.0.1599.101 can be downloaded from:

33e426a5108cbcb8fb6c548a94820346 chromium-30.0.1599.101-i486-2sl.sfs

Repackaging of chromium-30.0.1599.101-i486-2sl.txz originally from
http://repository.slacky.eu/slackware-1 ... .1599.101/

Tested to work OK on both Precise Puppy 5.7.1 & Slacko 5.6 & Upup Raring 3.9.9 & LxPup 13.10

This version still shows an annoying message each time it starts about missing Google API-Keys...

If you need a pet - can I suggest that you create a pet from the sfs - just click on the sfs and copy its contents into a new folder and then use dir2pet from a terminal to make the folder into a pet.

Cheers
peebee

Posted: Sun 01 Dec 2013, 19:59
by sunburnt
HI peebee; I`m making a RoxApp type package from your Chromium and I`ve hit a snag.

Your run script does: chmod 4755 /usr/lib/chromium/chrome-sandbox
So you`re relying on Puppy`s union Save file to create another modded chrome-sandbox file.
This leaves an orphan chrome-sandbox file when the SFS is removed. Not the best idea...
But worse for me is that no-install apps don`t use the union, so an SFS file can`t be chmod.

If this were just for me, I`d make a new SFS file with chrome-sandbox having the correct mod.
But for a Puppy forum download, to have to make a new SFS file is just way too much effort.

# Would it be possible for you to remake your SFS file so chrome-sandbox is mod 4755 ?

Many thanks for any help you can provide peebee. Terry B.
.

Posted: Sun 01 Dec 2013, 21:51
by peebee
sunburnt wrote:# Would it be possible for you to remake your SFS file so chrome-sandbox is mod 4755 ?

Many thanks for any help you can provide peebee. Terry B.
.
Hi sunburnt

Changes made as requested and sfs uploaded (new location and new md5).

Cheers
peebee

Posted: Mon 02 Dec 2013, 00:31
by sunburnt
WOW...! Talk about developer response.! A different site url I see... Thanks peebee.

A thought: SFS files have no way to cleanup after themselves, so I avoid making new dirs/files.
No-install apps like RoxApp and AppDir can cleanup and pretty much do anything.

Utilities like seaside`s ExeSfs or SfsExe ( can`t remember which ) and RSHs work with SFS
come real close to the same thing, the ability to change the environment for the app.

# And now the next problem, it`s essentially the same problem I had with OscarTalks Yandex site.
Your Box site won`t give me the actual download url, and Yandex mangles their urls.
There`s really nothing the 2 of you can do about that.

# But your first site worked great with my downloader. Why the different site?

### Do you by chance have your Chromium-30 SFS file mirrored at Smokey`s site.?
.

Posted: Mon 02 Dec 2013, 07:45
by peebee
sunburnt wrote:# But your first site worked great with my downloader. Why the different site?

### Do you by chance have your Chromium-30 SFS file mirrored at Smokey`s site.?
Hi

There is a problem with e-nautia in that you cannot upload a new version of a file without e-nautia changing it's name.

I did wonder if changing to Box might be a problem.

I don't have a Smokey account....

I have uploaded to e-nautia -
http://e-nautia.com/peebee/disk/share/c ... 1-i486-2sl (2).sfs
and as you can see it now has " (2)" appended and I can't use the forum function on it. also to Sourceforge - ... s/download

Do either of these work??

Cheers
peebee

Posted: Mon 02 Dec 2013, 18:16
by sunburnt
Sourceforge`s url is: http://sourceforge.net/projects/lxpup/f ... t/download
Which pops up a Firefox download, so I`m not sure... There`s no FileName in the url.
I`ll check it out and see what luck we have.

# Ally responded to my post about web sites. I`m going to see if his is usable, let you know.
.

Posted: Mon 02 Dec 2013, 22:17
by sunburnt
Hey peebee; I tried your Chrome-30.....i386 from e-nautica and the url is usable.
This site is nice and fast and doesn`t buck the download off after awhile.

Again however, the sandbox file is the wrong mode, 755 not 4755.
One way or the other, both files have their problems. :lol:

I already have Chrome-24 running as a no-install AppPkg. So Chrome`s easy to do.
.

Posted: Tue 03 Dec 2013, 10:02
by peebee
sunburnt wrote:Again however, the sandbox file is the wrong mode, 755 not 4755.
Hi sunburnt

I've uploaded it to e-nautia with a slightly different name:
http://e-nautia.com/peebee/disk/share/c ... 1-i486.sfs

It wouldn't download for me with Pwsget with the " (2)" name....

When I install it chrome-sandbox has the correct permissions - I don't get any errors when I run it from the terminal (under Slacko 5.6).

Cheers
peebee

Posted: Wed 04 Dec 2013, 03:19
by sunburnt
I`ll take a look... Tx. for the help.!

Posted: Wed 04 Dec 2013, 05:55
by sunburnt
I have a SFS file: chromium-30.0.1568.0.sfs
But I don`t know where I got it. It`s the only one that works for me, but I don`t have a url for it.

### Is it yours peebee.?

Posted: Wed 04 Dec 2013, 07:00
by sunburnt
Update on SFS file: chromium-30.0.1599.101-i486.sfs

Used same setup ( 1 link: /usr/lib/chromium ) that worked with: chromium-30.0.1568.0.sfs
### Please see post above and let me know if it`s your file peebee ( I think it is...).

But chromium-30.0.1599.101-i486.sfs errors on my Puppy Precise-5.5.X.5:
Too damn many Puppies.! It must drive you app builders nutty.! :roll:

Code: Select all

[8239:8313:1203/235450:FATAL:nss_util.cc(396)] NSS_VersionCheck("3.14.3") failed. NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
Aborted

Posted: Wed 04 Dec 2013, 07:19
by peebee
sunburnt wrote:

Code: Select all

[8239:8313:1203/235450:FATAL:nss_util.cc(396)] NSS_VersionCheck("3.14.3") failed. NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.Aborted
Hi sunburnt

I think your error message says it all - the 30.0.1599 Chromium demands a later version of NSS than you have in the Puppy version you are using.

You have 3 options:
- stay with the older version of Chromium that works
- move to a more up-to-date Puppy
- try to update NSS to the required version

Cheers
peebee

Chromium 32

Posted: Thu 30 Jan 2014, 17:35
by peebee
Here is Chromium 32.0.1700.102 in sfs format - convert to a pet as described previously if a pet is needed.

Mainly built for use on LxPup but also works on Slacko 5.6

Does not work on Precise 5.7.1 but Oscartalks has a version that should.

On Slacko 5.6.5.2 (5.7 in testing) it "mainly" works but has an oddity in that the window Maximise/Restore button doesn't work - no idea why as there are no error messages when run in a terminal.

Does not include FlashPlayer - download using the GetFlash Install Flashplayer in the menu under Internet.

I did try it with the Pepper FlashPlayer plugin but this didn't work with BBC iPlayer.....

Repackaged from:
http://slackware.org.uk/people/alien/sl ... g/current/ but with added:
harfbuzz-0.9.16 and icu4c-51.2 from pkgs.org

Cheers
peebee

Posted: Thu 30 Jan 2014, 19:15
by Semme
There's a Precise build on this :wink: page.

Chromium 33.0.1750.152

Posted: Sun 23 Feb 2014, 15:37
by peebee
Here is chromium-33.0.1750.152-lx.sfs

Works on LxPup14.03-s and also on Slacko5.7

Cheers
peebee

Chromium 33.0.1750.152

Posted: Tue 18 Mar 2014, 18:00
by peebee
24-mar-2014 update:

chromium-33.0.1750.152-lx.sfs

Now seems to work correctly with Slacko5.7

Chromium 33

Posted: Wed 02 Apr 2014, 02:50
by Dpup
As I posted in Canon 2012 printer update section, have been trying to find way to print with new Canon MX922. No CUPS driver, and Debian Linux CUPS driver just dumped print into bit bucket and reported print complete. Installed Chrome 21 pet posted by Playdaz a while back and MX922 Cloud printer found, worked fine. Installed peebee most recent Chrome 33 update for Slacko 5.7 which worked fine as browser but unable to find my MX922 Cloud enabled printer, booted USB flash with older Chrome 21 and cloud printer found and worked fine. So I don't know what needs to be done to make Chrome 33 work with cloud printing.

Still would prefer CUPS driver for Canon MX922, but so far not successful.

Thanks for any suggestions or fix.