LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Google Chrome 64 bit on Slack 13/64 (https://www.linuxquestions.org/questions/slackware-14/google-chrome-64-bit-on-slack-13-64-a-770480/)

cwwilson721 12-01-2009 09:10 AM

Quote:

Originally Posted by sahko (Post 3775712)
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
Code:

/opt/google/chrome/google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory
When I run slocate:
Code:

slocate libnssutil3
/usr/lib64/libnssutil3.so
/usr/lib64/firefox-3.5.2/libnssutil3.so
/usr/lib64/thunderbird-2.0.0.23/libnssutil3.so
/opt/google/chrome/libnssutil3.so.1d

So whats up? It's in chrome's own freakin directory!

cwwilson721 12-01-2009 09:29 AM

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

tommcd 12-03-2009 12:48 AM

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.

SCerovec 12-08-2009 02:01 PM

my 2c:

Code:

#####
#
# the patch for google chrome on Slackware 13.0
# The rpm for fedora was converted with rpm2tgz ;-)
# GPL v3 apply. Cest73@gmail.com
#
####



libdir="/usr/lib/"
finddir="/usr/lib/seamonkey/"
EXE="chrome"
DIR="/opt/google/chrome/"
lst=$(ldd $DIR$EXE | grep "not found" | sed s/" => not found"/""/)
echo missing: [$lst]
echo "chrome executable:" $EXE
echo "chrome dir:" $DIR
# this was for slackware 13.0
# lst="libnss3.so.1d libnssutil3.so.1d libsmime3.so.1d libssl3.so.1d libplds4.so.0d  libplc4.so.0d libnspr4.so.0d"

for f in $lst
    do
    d=`echo $f | sed s/"\..d$"/""/`
    echo loacating "[$d]"
    h=`find $finddir -name $d`
    if [ -z $h ]; then
        echo not found!
        echo "missing [$h]!"
        else
        l=$libdir$f
        echo found!
        echo "symlinking[$h] to [$l]"
        rm -v $l
        ln -vs $h $l
        fi
    done
   
   
echo "done."

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

SCerovec 12-08-2009 02:03 PM

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

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

Lufbery 12-08-2009 03:00 PM

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,

zbreaker 12-08-2009 03:08 PM

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.

ROXR 12-08-2009 05:25 PM

Quote:

Originally Posted by zbreaker (Post 3784475)
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

tommcd 12-09-2009 12:20 AM

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.

cycojesus 12-09-2009 01:02 AM

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).

tommcd 12-09-2009 01:35 AM

Quote:

Originally Posted by cycojesus (Post 3785024)
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...

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.
Quote:

Originally Posted by cycojesus (Post 3785024)
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.

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?
Quote:

Originally Posted by cycojesus (Post 3785024)
Incidently, today I decided to ditch Chrome from my system because of 1) the stupid declaration of Eric Schmidt (spelling?), ...

Could you elaborate on this as well?

ROXR 12-09-2009 02:25 AM

Quote:

Originally Posted by cycojesus (Post 3785024)
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...

Hello

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
wath I can do ? where search chrome the shared libraries ?, the symbolic links are in /usr/libexec/google-chrome

thanks

tommcd 12-09-2009 03:40 AM

Quote:

Originally Posted by ROXR (Post 3785112)
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
wath I can do ? where search chrome the shared libraries ?, the symbolic links are in /usr/libexec/google-chrome

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):
Code:

  ln -s /usr/lib64/seamonkey/libnssutil3.so ./libnssutil3.so.1d
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.

ROXR 12-09-2009 03:55 AM

Quote:

Originally Posted by tommcd (Post 3785190)
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):
Code:

  ln -s /usr/lib64/seamonkey/libnssutil3.so ./libnssutil3.so.1d
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.

tommcd 12-09-2009 06:29 AM

Quote:

Originally Posted by ROXR (Post 3785213)
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?


All times are GMT -5. The time now is 04:31 PM.