Quote:
Also installed mozilla-nss Still wouldn't work. Complains about Code:
/opt/google/chrome/google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory Code:
slocate libnssutil3 |
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:
Code:
##### 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.
|
Quote:
¿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). |
Quote:
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. Quote:
Quote:
|
Quote:
I tried your script into another slackware64 machine, it install well without errors, but when I try to execute it say Code:
./google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory thanks |
Quote:
Cycojesus's slackbuild for chrome makes this symlink (among others): Code:
ln -s /usr/lib64/seamonkey/libnssutil3.so ./libnssutil3.so.1d 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. |
Quote:
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. |
Quote:
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? |
All times are GMT -5. The time now is 04:31 PM. |