Hi, I just installed slackware 13.37 - current. And then I installed google chrome. When ran it, it complained it failed to locate libpci.Slackware has libpci.a. After checking the slackware build script for pciutils, I added SHARED=yes in the script and then rebuilt then reinstalled the newly built pciutils package. When starting google chrome, the error message is gone.
It seems work now. But i am not that comfortable.Can anyone tell why Slackware does not build this as the shared library? Will it cause any trouble to the other parts of the system?

Are you aware that there is a SlackBuild script to convert the Google Chrome .deb packages for Slackware as well as support libraries in the /extra directory of Slackware-current?

@allend

The additional lib is only PAM, not libpci. So that may be a different problem here.

@huhuhu

What version of chrome did you use?

@grissiom and @allend, I tried both version, stable and beta. I downloaded the .deb from google website, and used the script in /extra/google-chrome to convert it to the slackware .txz package. Chrome seems to try to use libpci to get the gpu information. If you are interested, I can reinstall the pciutils package from slackware current and copy that message here.

By searching the old threads, I can find similar issue was reported already:

ERROR:chrome/gpu/gpu_info_collector_linux.cc(84)] Fail to dlopen libpci

in thread http://www.linuxquestions.org/questi...3/#post4264277


In fact, I think by rebuilding the shared library, the error message when starting chrome is gone. What I'm worried is if the package built with SHARED=yes will cause issues to other parts of the system.

I must admit that I have not tried Google Chrome, so I will quickly back away.

Hmmmm double post

I'm not seeing this here on our 32/64 bit systems.

Which version of Chrome are you running - there's 3 different channels. google-chrome-12.0.733.0-x86_64-1 is installed on this PC, the other PCs are running the same version. I do have Composited render layer borders and GPU Accelerated Canvas 2D enabled. All PCs have Nvidia GPUs with latest Nvidia binary driver, and a couple of Intel i915's.

Some digging led me to believe this is GPU related. Google Chrome does not support all GPUs and all driver versions. This should have been fixed - perhaps it's only in the unstable/dev builds.
http://src.chromium.org/viewvc/chrom...revision=78603

Try launching Google Chrome with

I'd check for an updated version.

There's also this bug report -
http://www.google.com/support/forum/...738ab7dd&hl=en

Chrome is changing all the time so I think it's better to give the FULL version number. I've tried 11.0.696.50 beta and it could launch up. But I got the message from console:

I even enabled all the experimental features but it could launch as well....

Still, I doubt why not build the libpci.so. Is it for security reason?

The presence of a library or not cannot be because of security. If it was, even the .a would be a problem since all you have to do is link it into an executable.

Most likely, the shared lib was overlooked, because there weren't any known users until Chrome.

huhuhu, the link you posted for my issue was related to embedded videos not loading. I think the libpci error shown on the console is not a show stopper, but it is a curious error. I'm using the latest beta of chrome (with the pam solibs that Pat V. provides) with no problems (other than embedded video no playing with vlc like it should).

@disturbed1, if I need to disable all those stuff, I'd simply go back to firefox. The reason I use chrome is because it claims it can access GPU directly. based on my experience, google chrome renders page faster than firefox. (my video card is raedon 2600).

Also, the error message only occurs when chrome starts. Chrome can still start and be used without any problem. But, what my guess is, if this error is there, I wonder if chrome can really access GPU directly. That's why i prefer to recompile and let the message gone.

You can't recompile Google Chrome. They only release it as a pre-built binary. However, you can compile Chromium and see what happens, but it does take a while.

The bug reports that I posted links to, show that this bug is fixed in newer versions.


google-chrome-11.0.696.57-i386-1.txz + ATI 3470 + OSS drivers = libpci error (stable/beta version)
google-chrome-12.0.742.9-i386-1.txz+ ATI 3470 + OSS drivers = no libpci error (unstable)

My ATI 3470 (RV620 PRO) is close to your 2600 (RV630).


This is exactly what I posted above - it is related to the GPU (read the entire output in the terminal) - and has been fixed.



Upgrade your Google Chrome.

1 members found this post helpful.