Google Chrome 64 bit on Slack 13/64
 

Hi, I was able to setup google chrome 64bit (the early dev access version) on my machine so just want to share my experience & build script for those who are interested.

http://sites.google.com/site/nguyen/...kware/packages

Feedbacks welcome. Thanks

You might as well warn potential customers that Chrome needs around 10gb in /tmp to build.

If you build from src then it might take that much - the method I use is installing the binary provided by Google

So how's it run, compared to firefox?

Much faster than firefox from what I heard.

Any chance this would officially get shipped with slackware?

it's insanely fast - comparing to Firefox. Still in very early development stage though and is quite immature, lacks of extension supports and configurations.

Maybe in some years when it actually has a release, is stable enough, has proven to be better than the alternatives & many people use it.

How is the speed compared to the Windows version of Chrome?
I would be interested in seeing someone run javascript benchmarks on both.

It is said that chrome run faster under linux than windows. Because chrome consume much RAM, and windows is poor in memory management. It will swap the application into virtual memories on disk if you minimize the window. If you want to bring it up, it takes long to wait swapping from disk to RAM.

I've never used Google Chrome, but have been running the daily Chromium builds for a few weeks now.

It's down right shameful how fast Chromium is compared to Firefox, Seamonkey, and even Konq. Flash takes less CPU in Chromium than Firefox. On one of our modestly powered machines (PDC 2140 1.6ghz x2), full screen high quality Hulu stutters quite often, in Chromium it is fluid.

On my E8400, watching Hulu in Chromium takes 19% CPU with 84M ram. Same clip in Firefox 3.5.5 take 27% CPU with 192M ram. Add to that the startup and shutdown time of Firefox that grows after usage, and the disk thrashing that happens because they want to put everything in an SQLite database, unless Firefox does something to compete with Chromium, I see it's user base going down.

Chromium is nice, I like it immensely, but it can't replace Seamonkey for me yet. My girlfriend used to run Windows in a VM just to play her flash based games, she hasn't had to since I put Chromium on her PC.

So flash on Linux isn't that good, and Chromium makes it usable. It is faster than Seamonkey, but not fast enough - or Seamonkey is not slow enough - to make me want to switch browsers. If I found myself needing to close and launch the browser often, maybe. I usually launch Seamonkey once, and it stays running for a week or so.

If you visit javascript heavy sites, Chromium is quite a bit faster. I personally don't visit these sites that much.
SunSpider JS benchmarks
Chromium 395.8ms
Seamonkey 2253.0ms
Konq 2635.2ms
Firefox 2071.6ms

And that tells me how important benchmarking Javascript is ;) On this PC which ran that benchmark, in day to day usage, Konq is the fastest, then Seamonkey, in dead last is Firefox.

i used chrome in slack before, did not keep it for more than a few clicks. am too used to Firefox n' am too lazy to change.

however, it was really fast, stable and rendering performance was awesome.

although i don't see it being integrated into Slackware tree anytime soon.

In case anyone missed it, there is now a slackbuild for google chrome on slackbuilds.org:
http://slackbuilds.org/repository/13...google-chrome/
The google chrome slackbuild can be installed on both 32 bit and 64 bit Slackware. I am running it on Slackware 13 64 bit. It is indeed very fast and light.
Thanks to Erik Hanson for providing the slackbuild script!

Tried the slackbuild. After installing Gconf and ORBit2, it installed.

Now mit won't run, complains about nss libs.

So google has gone bye-bye. Wasted 45 minutes on this pos, not going to devote anymore time until/if it becomes stable, and actually WORKS on a default install of SW13/64 multilib.

Do you have seamonkey installed?
Also you might wanna try http://slackbuilds.org/repository/13...m/mozilla-nss/

If seamonkey is installed on a default SW13/64, yes. (Version 1.1.17).

Also installed mozilla-nss

Still wouldn't work.

Complains about When I run slocate: So whats up? It's in chrome's own freakin directory!

Figured out how to fix this issue.

The setup tries to link to /usr/lib64/seamokey for all its links.

On a default SW13/64 system, that doesn't exist.

Reset the links to /usr/lib64, and now it works

Might want to work on the build scripts abit

For those of you who are still interested in google-chrome, I found an advert blocking extension for chrome called Adsweep that works pretty well:
http://adsweep.org/
Adsweep is not quite as effective as AdBlock Plus for Firefox; but it does manage to block most ads. I have been using AdBlock Plus in Firefox for so long that it really annoying for me to surf the web without it and have to see all those bleeping, blinking, pulsating flash ads that seem to be so ubiquitous on the internet these days.
I am using adsweep on the google-chrome for Slackware64 that is on the slackbuilds.org site:
http://slackbuilds.org/repository/13...google-chrome/
To use adsweep you only need to install the extension AdSweep.crx. The user script AdSweep.user.js does not seem to be needed. Note that there are adsweep versions available for Firefox and Opera. I have not tried adsweep in other browsers though.
EDIT: Adsweep has just been updated to version 2.0.1. I was able to automatically update it through chrome.

my 2c:

I know it's a puppy but it worked for me as a charm.
Edit the directories in the beginning to fit Your Slackware version.

This might be pretty portable?


my just 2c.
EDIT:

NO dependencies on Vanilla Slackware :)
keep it clean and tidy

Oh!
Chrome is lightning FAST (I'm on a 950MHz Duron)

the machine is like *woah!* (::burdenless::)

I've used Chrome off and on in Windows since it came out, but as I hardly ever use Windows any more I've been wondering about it on Slackware.

I have a quick question: one of Chrome's "selling points" is that it automatically pushes updates to the users' computers when they're available. Does that feature work with Slackware? If so, is does ti have to be done as root? Is there any way to control it?

Thanks,

Installed the Chrome SlackBuild along with the depends on my Slackware64 -current multi-lib and thankfully experienced no problems. Don't really notice that dramatic a difference in speed to be honest...a bit snappier I'll admit. Still using Firefox primarily for now.

Same here, I build packages on my Slack64 current multilib and it work fine, same that firefox + or -

¿there are a especial web where could appreciate difference? I do'nt know

Google Chrome for linux has now been released as a beta build:
http://www.google.com/chrome?platform=linux
It is still only available as binary .deb and .rpm packages.

my google-chrome.SlackBuild
 

You might be interested in my SlackBuild @ http://github.com/cycojesus/slackbui...google-chrome/

It repackages the .deb, tested on x86_64 -current, should also work on x86...

I tried various other .SlackBuilds before but they all tried to kill my system (it ain't fun to get a "command not found" when you type ls...) so ultimately I decided to roll my own. Works (flawlessly) for me.

Incidently, today I decided to ditch Chrome from my system because of 1) the stupid declaration of Eric Schmidt (spelling?), and 2) firefox suck less (for me).

Thanks, I made a note of your chrome slackbuild page for future reference.
I just upgraded to the google chrome beta using the slackbuild from slackbuilds.org:
http://slackbuilds.org/repository/13...google-chrome/
Using that slackbuild has worked well for me so far. I am running Slackware 13 64bit.
Could you elaborate on that please? Which slackbuilds did you try? And how did they break your system? Have you tried the one from slackbuilds.org?
Could you elaborate on this as well?

Hello

I tried your script into another slackware64 machine, it install well without errors, but when I try to execute it say

wath I can do ? where search chrome the shared libraries ?, the symbolic links are in /usr/libexec/google-chrome

thanks

Just a guess, but do you have Seamonkey installed? Seamonkey is part of a standard Slackware install. So if you did a full install you should have it.
Cycojesus's slackbuild for chrome makes this symlink (among others):
So without Seamonkey that would not work.
Also, (another guess) the chrome slackbuild from slackbuilds.org requires Gconf, which in turn requires ORBit2. I don't know if Cycojesus's slackbuild requires them or not though.

Yes, semonkey is installed and functional. GConf and ORBit2 is also installed. It is rarely because yesterday I installed in my other computer and it work well.

thanks

Solved, for some reason the library /usr/lib64/seamonkey/libnssutil3.so did not exist, however, it allow to create a symbolic link without error.

Glad you got it fixed.
Just out of curiosity, how did you go about creating the /usr/lib64/seamonkey/libnssutil3.so library? I assume that is how you fixed it. Is that correct?

I think (was some time ago now) I tried one found in a topic here, and then another from slacky. (Note that I adapted both to make a x86_64 package). Both changed permissions in such a way that I had to reinstall aaa_base to get a functional system again. Seeing that I immediately removed chrome's packages, I was just curious. One day I got curious enough to write my own and motivated long enough to make it work.

I didn't know that slackbuild.org had one, missed that somehow, so my advice now would be to use that one as I'm a happy user of SBo and sbopkg when they have what I need. The .SlackBuild in my repository are only the ones I couldn't find or that I modified.

EDIT: Why I don't use it anymore:
http://www.theregister.co.uk/2009/12...dt_on_privacy/ & the fact that it doesn't really satisfy me. For me it lacks polished extensions and the address-bar completion is not as good as firefox's and I use it a lot so it was inconvenient as I had to think before typing something I expected to auto-complete which defeat auto-completion's purpose...
I'm back to firefox (3.6b4) :)

Please elaborate, or at least provide a link. I have no clue what you're referring to here.

I've pointed out elsewhere why I prefer Firefox and Seamonkey (although Konqueror is a close third):

• Firefox/Seamonkey have a quick way to turn off all styles (View -> Page Styles -> No Styles) which is very useful on pages that don't render well or are just plain ugly.
• I like the fine-grained control over settings (including the user interface) in Firefox/Seamonkey.
• Old habits: I've been using Netscape since it was in .8 beta and the Netscape lineage in Firefox/Seamonkey is comfortable/comforting.
• The intention with Chrome is that updates are pushed automatically to users without much user interaction/control. This runs counter to how I administer my Slackware computers.

Having said all of that Chrome looks like a good browser, and the Windows versions I've played with seem to work pretty well.

Regards,

First create all symbolic links to /usr/lib64 , after reinstall seamonkey, I wished copy only that library, but not it in my hand .

Thanks

[QUOTE=Lufbery;3785494]Please elaborate, or at least provide a link. I have no clue what you're referring to here.

I believe he's talking about a comment implying only criminals care about privacy.

http://yro.slashdot.org/story/09/12/...For-Wrongdoers

Ah well, that's a silly statement. I get where's he's coming from (sort of) -- I pretty much never do or post something on the Internet that I wouldn't do in public. But I also value my privacy both in the real world and on-line. Some stuff, even most of it, is nobody else's business. :-)