I'm currently using Chrome v22.0.1229.79 on Slackware 13.37, on a C2D Thinkpad. For some time now I've had an issue if I log into Chrome to allow for synchronizing settings via the Chrome profile. After varying amounts of time, opening Chrome is an exercise in watching a completely blank window fail to load any structure at all.
I have several times moved or removed some, and then eventually all, of ~/.config/google-chrome/ which successfully allows me to open and use Chrome. I can even log back into Chrome and, for some time, use it without issue. Eventually, though, on this particular machine, I run into the same problem.
I have experimented with disabling some, then all, Chrome extensions. I have had some issues with the Evernote Webclipper, for instance, in a guest Linux VM (on a completely different machine, with a completely different setup), so I thought extensions might be the cause. This didn't help.
I'm assuming that, at some point, Google Chrome changed the structure of its profile components such that older versions get fubar. I've tried to use the Slackbuild to update Chrome, but ran into an issue building.
Code:
opt/google/chrome/chrome: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by opt/google/chrome/chrome)
Looking at the cxxlibs.Slackbuild in /source/a/cxxlibs/, it's just building symlinks to /usr/lib/libstdc++.so.[5, 6]. Which tells me I need to update libstdc++ itself. Which means updating gcc. Which brings me to my questions:
- Is there a way to get Chrome to not corrupt the profile when I log in?
- If not, and if upgrading Chrome is necessary, how much damage do I do by upgrading gcc, given various other components use the older version I have installed?