[SOLVED] Google Chrome from SlackBuilds.org stopped working...

Lufbery · 12-23-2009, 10:40 PM

Hi all,

I installed Google Chrome a few days ago to check it out.It worked fine yesterday, but stopped working today with this error:

Code:

/usr/bin/google-chrome: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory

My computer has libgconf-2.so.4 in /opt/google/chrome/, but that's actually a link to /usr/lib64/seamonkey/libgconf-2.so.4 which is not there any longer.

The strange thing is, I don't think I did anything to Seamonkey between yesterday and today to cause the change. Furthermore, Seamonkey is still working.

I'm running Slackware64_13 -stable with all the patches installed. I realize that the last patch was an update to Seamonkey, but I think I installed Chrome after installing the Seamonkey patch.

Help?

Regards,

~sHyLoCk~ · 12-23-2009, 11:30 PM

Hi,
I don't know if I'll be much of help but I'll try. I just installed Google Chrome amd64, from Slackbuilds. It gave me nsslib error, so I upgraded the seamonkey-solibs to 2.0.1 and then it gave me the libgconf error you got. I then built the Orbit2 and GConf packages from Slackbuilds and Google Chrome now works.

trxdraxon · 12-23-2009, 11:33 PM

I thought I was going crazy, I am having the same issue. I even tried building gconf and orbit2 from slackbuilds but that didn't help, gconf keeps complaining that orbit2.0 isn't installed even though it finds 2.4

EDIT: This was a few nights ago on stable, going to try again now that I am running current.

~sHyLoCk~ · 12-23-2009, 11:46 PM

Quote:

Originally Posted by Lufbery

My computer has libgconf-2.so.4 in /opt/google/chrome/, but that's actually a link to /usr/lib64/seamonkey/libgconf-2.so.4 which is not there any longer.

Hmm strangely enough

Code:

$ file /opt/google/chrome/libgconf-2.so.4
/opt/google/chrome/libgconf-2.so.4: broken symbolic link to `/usr/lib64/seamonkey/libgconf-2.so.4'

Still google-chrome is working. However I do have:

Code:

/usr/lib64/libgconf-2.so                     
/usr/lib64/libgconf-2.so.4.1.5               
/usr/lib64/libgconf-2.so.4  
/usr/lib64/libgconf-2.la

Maybe you could try linking them there?

damgar · 12-23-2009, 11:51 PM

I've had no problems out of Chrome aside from meeting the dependencies listed in the Slackbuild and the bugs I have on all the different versions I have installed on 3 machines. It's even survived the move from stable to current and a large round of updates to current yesterday........ I just checked and some of those bugs are actually gone since yesterday's updates....Chrome was not one of them.

Lufbery · 12-24-2009, 08:45 AM

Thanks for the help, guys. I'll poke around a bit more and see what I find out.

Lufbery · 12-24-2009, 10:48 PM

This is solved; thanks for the help.

I needed to install the dependencies listed in the slackbuild: Gconf and Orbit2. Now everything is working just fine.

I think the update to seamonkey-solibs to 2.0.1 from 2.0 broke the dependencies. To put it another way, if you've got seamonkey-solibs 2.0, you don't seem to need Gconf and Orbit 2 to run Chrome.

Thanks!