[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
talk:howtos:software:google-chrome [2012/09/26 02:56 (UTC)] – moved from the general howtos namespace mfillpottalk:howtos:software:google-chrome [2018/12/04 14:36 (UTC)] (current) – mr.spuratic
Line 16: Line 16:
  
 The chrome SlackBuild does a simple re-packaging of Google's own binaries (available as a debian package). Chromium on the other hand, is //compiled from source// using its SlackBuild. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/09/07 16:36// The chrome SlackBuild does a simple re-packaging of Google's own binaries (available as a debian package). Chromium on the other hand, is //compiled from source// using its SlackBuild. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/09/07 16:36//
 +
 +-------
 +The HOWTO doesn't work for me. First I tried Chrome 26 from Google website on Slackware 14 (32 bit). I could run and use binary, but a lot of places within browser were red squares/boxes only. Very ugly at least. I spent a lot of time searching for fix with no result. Now I've upgraded to Chrome 28 with the same disapointing. When I run chrome with more logging
 +
 +''chrome --enable-logging=stderr --log-level=0 
 +''
 +I could see a lot of messages like
 +
 +''[22079:22079:0804/203243:WARNING:resource_bundle_gtk.cc(96)] Unable to load pixbuf with id 6994
 +'' 
 +
 +I tried a lot and finally got fix by removing gdk-pixbuf2-2.26.1-i486-2.txz from system and compiling/installing the same package with no patches myself.
 +
 +Btw. I got into similar troubles with Graphviz/dot (png output didn't work) on Slackware 14 and simply recompiling Graphviz fixed the problem.
 +
 +----
 +
 +Slackware64 14.2 and Chrome 70.x (October 2018)
 +
 +  * Slackware 14.2 also provides the Chrome slackbuild in extra/.
 +  * Chrome 70 (and possibly earlier) no longer uses the NSS library names that are patched in the slackbuild script (those paths don't need to be patched as the normal library names are used now)
 +  * Chrome 70 *requires* NSS >= 3.26, whereas Slackware 14.2 only provides 3.23. (Chrome will start, and then exit abruptly when you attempt to use it, with a message to that effect)
 +  * Slackware-current has mozilla-nss-3.39, this builds fine via slackbuild script on 14.2, installs with ''upgradepkg'' and resolves that problem
 +
 +This has popped up on [[https://www.linuxquestions.org/questions/slackware-14/requests-for-current-20151216-a-4175561577/page186.html|requests for current]]. I suspect the requirement (based on the [[https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.26_release_notes|3.26 release notes]]) *might* be for ALPN and/or TLS1.3 support.
 +
 +Update: (December 2018) NSS Security patch brings Slackware 14.2 up to nss-3.40 which should fix this too.
 +http://www.slackware.com/security/viewer.php?l=slackware-security&y=2018&m=slackware-security.430378
 +
 +----
 +That LinuxQuestions post you reference is now more than a year old. A few posts later (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-20151216-a-4175561577/page186.html#post5756812) I answered that you can install Chromium as an alternative that works on Slackware 14.2. My Chromium 70, released today, also still works well on Slackware 14.2. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2018/10/25 09:30 (UTC)//
 +
 +-----

Trace:

talk:howtos:software:google-chrome ()