Installed Google chrome latest but not working in slackware 14.0 32 bit

sinar.kk · 01-13-2016, 02:12 AM

I am installing first time google chrome in slackware , and i followed the instructions said in http://docs.slackware.com/howtos:software:google-chrome

(I downloaded the 32 bit deb file from google)

All went fine (the version google-chrome-47.0.2526.106-i386-1.txz)

Slackware said its installed , but i could'nt see anywhere the icon of google-chrome ,

I tried to start in terminal by typing "google-chrome" but the terminal simply said "Aborted" nothing else

Ps I tried this as root also but same output..

bassmadrigal · 01-13-2016, 06:49 AM

You can try and enable logging with:

Code:

google-chrome --enable-logging --v=1

According to this, the log should be in Chrome's user data directory (~/.config/google-chrome/Default).

But my guess is that Slackware 14.0 is just too old to run the latest Chrome. You could try compiling Chromium so it actually uses the libraries on your computer (checking Eric's packages, he only has chromium available up to v37, so that may have been when Chrome stopped working as well).

Alien Bob · 01-13-2016, 06:55 AM

Instead of Chrome you could try Chromium which is compiled from source for the Slackware 14.1 platform.
See https://www.google.com/search?q=chromium+slackware

sinar.kk · 01-13-2016, 08:26 AM

@Alien bob sir thank u for ur reply... ur help for Slackware community is beyond words

CTM · 01-13-2016, 08:31 PM

It's also worth noting that very soon (in March, probably following the stable release of Chrome 50), Google will stop officially providing packages and support for Chrome on 32-bit Linux systems. The build chain will still support 32-bit architectures, though, so 32-bit builds of Chromium are likely to remain available.

garpu · 01-14-2016, 03:05 PM

64 bit, here, but no problems with Chrome 47.0.2526.111. Double check it's got everything it needs with ldd? Did you recently change anything? I remember reading on the Chrome release blog that some other users were having problems with a corrupted upgrade. Might be worth rebuilding the package or reinstalling with a fresh copy.