Comment #26 on issue 15984 by willdye: /usr/local/lib/libstdc++.so.6:  
version `GLIBCXX_3.4.9' not found
http://code.google.com/p/chromium/issues/detail?id=15984

My case is even stranger.  I'm running what I thought was a completely  
updated
version of Ubunutu 9.10, with the latest version of Chrome from Google.  I  
still got
the message:

   /usr/bin/google-chrome: libstdc++.so.6: version `GLIBCXX_3.4.9' not found  
(required
by /usr/bin/google-chrome)

...when I ran the command "google-chrome".  I tried searching the package  
manager for
GLIBCXX, installing the latest version that I could find of libstdc++,  
installing and
running a package called "getlibs" that tries to resolve library  
dependencies, and
even installing Chromium from sources, all to no avail.  What finally  
worked in my
case was to write a little script that does this:

   cd /opt/google/chrome
   ./google-chrome $@

Chrome came up just fine.  To make the Chrome icon in my panel work, I put  
the above
code into a script called /home/(my-user-name)/bin/chrome, used "chmod +x
~/bin/chrome" to make the script executable, and changed the icon  
properties to call
up "/home/(my-user-name)/bin/chrome %U".  Now the panel icon works fine,  
and from the
command line "~/bin/chrome" works as well, but I suspect there will be  
trouble in the
future anyway (if I set Chrome to be my default browser, for example, I'll  
probably
have to tweak something else to make it all work).  Still, as an ugly  
work-around,
this worked for me.

I probably messed up my paths or library paths somehow, perhaps in  
a .profile or some
other system setting.  I'm passing this along only in the hope that it  
might help
someone else with a similar problem.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

-- 
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs

Reply via email to