Chromium Browser 34.0.1847.137
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Thanks for the reports.
The Chromium 30.0.1568.0 is a pre-compiled, raw, off-the-trunk version that I downloaded at a time before Version 30 was out as a stable release. It would be considered pre-beta and so may contain bugs. It has been fine for me whenever I have used it, but sorry to hear that some users have experienced problems. There are so many variables including different hardware and user settings. It is difficult for me to even begin to think of how to resolve such problems, especially if I can't reproduce them.
What I would suggest is that if any one version gives problems, just try a different version. These things get updated frequently and it is good that different forum members put together alternative builds and packages for people to try.
There are some versions posted by peebee in another thread which I believe are repackaged Slackware builds but which work in the latest Ubuntu Pups as well.
In my Yandex Disk ( http://yadi.sk/d/zTshLczR4wHj8 ) you will also find a Version 30.0.1599.101 which is a stable release Debian build repackaged for Puppy which works in Precise as well as Wheezy. It would be interesting to know if the crashing problem happens with this version.
I am currently experimenting with a Version 33.0.1717.0 which I might upload for people to try as well.
The Chromium 30.0.1568.0 is a pre-compiled, raw, off-the-trunk version that I downloaded at a time before Version 30 was out as a stable release. It would be considered pre-beta and so may contain bugs. It has been fine for me whenever I have used it, but sorry to hear that some users have experienced problems. There are so many variables including different hardware and user settings. It is difficult for me to even begin to think of how to resolve such problems, especially if I can't reproduce them.
What I would suggest is that if any one version gives problems, just try a different version. These things get updated frequently and it is good that different forum members put together alternative builds and packages for people to try.
There are some versions posted by peebee in another thread which I believe are repackaged Slackware builds but which work in the latest Ubuntu Pups as well.
In my Yandex Disk ( http://yadi.sk/d/zTshLczR4wHj8 ) you will also find a Version 30.0.1599.101 which is a stable release Debian build repackaged for Puppy which works in Precise as well as Wheezy. It would be interesting to know if the crashing problem happens with this version.
I am currently experimenting with a Version 33.0.1717.0 which I might upload for people to try as well.
Oscar in England
They are indeed - they seem to work in both spup's and upup's but not dpup's due to old libraries.OscarTalks wrote:.....which I believe are repackaged Slackware builds but which work in the latest Ubuntu Pups as well.
I haven't had crashes with any of the 30.0.1599.101 versions. Your Debian version works on Slacko/LxPup with the addition of libgconf - and is "better" than the Slackware build because it doesn't complain about missing Google API keys - but is a little bit bigger as an sfs.OscarTalks wrote:.....you will also find a Version 30.0.1599.101 which is a stable release Debian build repackaged for Puppy which works in Precise as well as Wheezy.
Choice is great fun!!
Cheers
peebee
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
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Debian have now released Chromium 31.0.1650.57 so I have been experimenting with packaging that and have removed the earlier versions.
Tested briefly and working in Wheezy, Precise and Upup Raring.
Works in Slacko 5.6 if you install libgconf2 and libgnome-keyring (use the search in PPM). With earlier Slackos you may also need to update the nss libs (which are in the Firefox directory).
I have been wondering if there is any advantage to using a wrapper script (eg does the directory /usr/lib/chromium need to be put into LD_LIBRARY_PATH or even PATH?) or if just launching the binary accomplishes everything.
With Wheezy and Upup Raring there is a fixator which is designed to allow users to install a chromium .deb package, but it also activates if you install a .pet (but not if you load an .sfs). This means that if I have my /usr/bin/chromium as a script pointing to my wrapper script, that /usr/bin/chromium gets over-written by a different one pointing directly to the chromium main binary (bypassing my wrapper script). The browser does still work, but without any of the variables from the wrapper script of course. Maybe I will ask Pemasu if it is possible to modify the fixator.
These recent Debian Chromiums are supposedly compiled against glibc version 2.11 so I did wonder if it might be possible to make them work in Lucid, but I tried adding missing libs and ended up with a symbol error. Anyone have any suggestions?
EDIT:- I have made some alterations so hopefully you can now install the .pet without the files getting altered.
Tested briefly and working in Wheezy, Precise and Upup Raring.
Works in Slacko 5.6 if you install libgconf2 and libgnome-keyring (use the search in PPM). With earlier Slackos you may also need to update the nss libs (which are in the Firefox directory).
I have been wondering if there is any advantage to using a wrapper script (eg does the directory /usr/lib/chromium need to be put into LD_LIBRARY_PATH or even PATH?) or if just launching the binary accomplishes everything.
With Wheezy and Upup Raring there is a fixator which is designed to allow users to install a chromium .deb package, but it also activates if you install a .pet (but not if you load an .sfs). This means that if I have my /usr/bin/chromium as a script pointing to my wrapper script, that /usr/bin/chromium gets over-written by a different one pointing directly to the chromium main binary (bypassing my wrapper script). The browser does still work, but without any of the variables from the wrapper script of course. Maybe I will ask Pemasu if it is possible to modify the fixator.
These recent Debian Chromiums are supposedly compiled against glibc version 2.11 so I did wonder if it might be possible to make them work in Lucid, but I tried adding missing libs and ended up with a symbol error. Anyone have any suggestions?
EDIT:- I have made some alterations so hopefully you can now install the .pet without the files getting altered.
Oscar in England
Thanks for this Oscar. I have been using your earlier versions in Slacko-5502 and I could live with the youtube problem but I couldn't get them to print. This latest version has cured both problems and is performing flawlessly.OscarTalks wrote:Debian have now released Chromium 31.0.1650.57 so I have been experimenting with packaging that and have removed the earlier versions.
Tested briefly and working in Wheezy, Precise and Upup Raring.
Works in Slacko 5.6 if you install libgconf2 and libgnome-keyring (use the search in PPM). With earlier Slackos you may also need to update the nss libs (which are in the Firefox directory).
I'm not using the 0micko's adrive so I didn't have libnss3.so or libnssutil3.so. I grabbed them out of a recent seamonkey and popped them into /usr/lib/Chromium, works fine.
I picked up a couple of addons from http://www.slackware.com/~alien/slackbuilds/, chromium-pdf-plugin and chromium-pepperflash-plugin. I have packaged them as pets. chromium-31.0.1650.57-pdf_reader.pet works very nicely turning the browser into a pdf reader. chromium-pepperflash-plugin-11.9.900.152.pet really bogs down my little atom N270 so I'm sticking with the stock flashplayer but on more powerful machines it will probably be fine. I've modified your /usr/bin/chromium to:
Code: Select all
exec /usr/lib/Chromium/chromium-wrapper "$@" --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so
Thanks again, J
Hi Oscar; Yandex really makes a mess out of it`s urls ( intentionally I`m sure...).
I`m making a no-install Virtual Package with your SFS file and can`t get wget to dnld it.
Yandex apparently hashes the urls so they`re never the same.
So it`s necessary to scrape the page to get the current url from it.
Do you know of any way to allow wget to easily dnld from Yandex.?
# Nice job with your apps, your Chromium apparently works for many Puppies.
This is the kind of apps Puppy really needs, "cross-variant functioning apps".
.
I`m making a no-install Virtual Package with your SFS file and can`t get wget to dnld it.
Yandex apparently hashes the urls so they`re never the same.
So it`s necessary to scrape the page to get the current url from it.
Do you know of any way to allow wget to easily dnld from Yandex.?
# Nice job with your apps, your Chromium apparently works for many Puppies.
This is the kind of apps Puppy really needs, "cross-variant functioning apps".
.
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Hi sunburnt,
Thanks for alerting me to the Yandex / wget issue, I wasn't aware of it and don't know of a fix off hand. Maybe I should look for an alternative storage facilty.
As always, my apps are just me tinkering around. I publish them with an open invitation to anyone to fill in the gaps in my knowledge, but also if they prove useful to other users then that is great.
I have also recently uploaded packages of Google Chrome version 31.0.1650.57 and Iron 29.0.1600.1 if anyone wants to check those out. In both cases I have moved the main folder to /usr/lib rather than /opt/google or /usr/share respectively.
Thanks for alerting me to the Yandex / wget issue, I wasn't aware of it and don't know of a fix off hand. Maybe I should look for an alternative storage facilty.
As always, my apps are just me tinkering around. I publish them with an open invitation to anyone to fill in the gaps in my knowledge, but also if they prove useful to other users then that is great.
I have also recently uploaded packages of Google Chrome version 31.0.1650.57 and Iron 29.0.1600.1 if anyone wants to check those out. In both cases I have moved the main folder to /usr/lib rather than /opt/google or /usr/share respectively.
Oscar in England
You sound like myself, always looking for a better way to do things.
Personally I like adding apps to /opt and keeping /usr relatively clean.
Most of what I write or make goes in /opt/(app) It`s a good place to add apps.
I found out how bad many urls are making my add-on support utility: xdlg.dnldprogress
I solved Yandex and other sites problem by making the /path/file a cli argument.
But this probably won`t solve really messed up urls that are ment to stop download apps.
.
Personally I like adding apps to /opt and keeping /usr relatively clean.
Most of what I write or make goes in /opt/(app) It`s a good place to add apps.
I found out how bad many urls are making my add-on support utility: xdlg.dnldprogress
I solved Yandex and other sites problem by making the /path/file a cli argument.
But this probably won`t solve really messed up urls that are ment to stop download apps.
.
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
@ nooby
The problem of running as root has been resolved by using a flag in the launcher script to specify a directory where the user profile data will be stored, eg:-
--user-data-dir=/root/.config/chromium
I normally run frugal installs, but my Chromiums (or Google Chromes or Irons) should work equally well in full installs.
The problem of running as root has been resolved by using a flag in the launcher script to specify a directory where the user profile data will be stored, eg:-
--user-data-dir=/root/.config/chromium
I normally run frugal installs, but my Chromiums (or Google Chromes or Irons) should work equally well in full installs.
Oscar in England
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Yes, that was the original one in this thread. Always worked fine for me and had lots of downloads. One or two people reported problems but everyone's systems are different. I took it down recently and replaced it with the later version which is a Debian compile against earlier glibc. Reports so far have suggested this is better and it runs in Wheezy. Does it not work for you?sunburnt wrote: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 Oscar.?
Oscar in England
This morning my local time I did dl your google-chrome-31.0.1650.57.sfs
and used sfs-exec to load it but nothing did happen
so most likely Lupu528-005 is too old? Nothing important
I will most likely only use Chrome if nothing else work
on some page dedicated to those who use chrome. So skip it if it is odd
and used sfs-exec to load it but nothing did happen
so most likely Lupu528-005 is too old? Nothing important
I will most likely only use Chrome if nothing else work
on some page dedicated to those who use chrome. So skip it if it is odd
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
This morning I dowloaded it again and will tell what happens later
I get back soon Edit must have done something wrong last time
Haha this time it does work instantly but I am not used to it
so will take some time to adjust to how google wants things done.
So Oscar thanks for the pet and sfs.
I get back soon Edit must have done something wrong last time
Haha this time it does work instantly but I am not used to it
so will take some time to adjust to how google wants things done.
So Oscar thanks for the pet and sfs.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
google chrome
just manual installed google chrome 32 from extracted .deb dl'd from google chrome installer page for first time EVER.
Everything eems be working okay... so far.
-
usb frugal install puppy raring 3.9.9.2
Everything eems be working okay... so far.
-
usb frugal install puppy raring 3.9.9.2
Chrome has a fix for an annoying problem in its browser use
Others may find this news a welcomed update. It is one of those bothersome things which I have agonized over before in browser use: "Where is that audio coming from?"
Hope this helps
Hope this helps
Chrome 32 on Precise 5.7.1 shows this error.
I am unable to install any Chrome version other than 24, every other version shows this error
There is only one old version that I am able to run on it. This error is always shown on every version of Chrome that I try to install. Anyone have any idea how to solve this?
I first ran Puppy Precise 5.5 and then upgraded to 5.7.1 few weeks earlier.
Please, I need to complete a programming project in scratch and the flash on Chrome 24 is outdated to complete my project. I need to submit it at the end of this month.
Code: Select all
/opt/google/chrome/chrome: /usr/lib/firefox/libnss3.so: version `NSS_3.14.3' not found (required by /opt/google/chrome/chrome)
I first ran Puppy Precise 5.5 and then upgraded to 5.7.1 few weeks earlier.
Please, I need to complete a programming project in scratch and the flash on Chrome 24 is outdated to complete my project. I need to submit it at the end of this month.