My thoughts on Slackware, life and everything

Chromium package updates

There was a new Chromium source release last week, but there were other software releases that had priority to get packages out the door. Therefore I could only chromium packages this weekend.
Chromium 76.0.3809.132 fixes 3 security holes. Note that the version before that (76.0.3809.100) also fixed 4 critical holes but I never packaged that as I went on holiday. So, upgrading now would be a good idea.

The packages (for Slackware 14.2 and -current) can be found on my site or any mirror (e.g.

Enjoy! Eric


  1. Eduardo

    Thank you Eric! So far it’s working good.

  2. guitarrizer

    Thanks a lot!

  3. Steve

    I can’t seem to get new (or any) chromium package to run properly on my 14.2 (X86-64). I must be missing libraries. I can get into my local router address 192.168.1.XXX but can’t seem to navigate to other URLs. I was getting some Slackware pages to come up but I figure they must have been cached somewhere. I can bring up the settings page but it crashes when I try to change anything! Any idea what I might be missing?

  4. Steve

    I also posted on LQ’s site. It occurred to me since my system has been converted to multilib I might need a compat32 version of the package.

    • alienbob

      No, multilib has nothing to do with this.
      If you can access your router by IP address but can not access external web pages, then it is clear that Chromium works, but the DNS name resolving has an issue on your computer.
      If you have the same problems with Firefox then the issue is on your computer indeed. If Firefox however opens all these external pages correctly and Chromium fails, then you could try resetting your Chromium browser profile in ~/.config/chromium/ . Perhaps the issue is a profile setting which you changed recently.

      • Steve

        Yes my Firefox works (resolves URLs) but it is the original 14.2 package (45.2.0esr) and needs upgrading also…
        I tried deleting both ~/.cache/chromium and ~/.config/chromium directories. This is not the issue.
        Launching chromium from the command line gives some feedback regarding NSS even though Chromium allegedly uses BoringSSL instead. “NSS_VersionCheck(“3.26”) failed. My NSS is from Firefox package “mozilla-nss-3.23-x86_64-1”. I will try upgrading NSS and obtaining BoringSSL package from git.

        • alienbob

          Ah, there you have your root cause.
          You never applied the patches which have been released for Slackware 14.2. The currently available version of mozilla-nss for Slackware 14.2 is 3.40.1, see for instance.
          I urge you to keep updated with patches. I compile my Slackware 14.2 packages against a patched and up-to-date Slackware installation.

  5. Steve

    upgrading the mozilla-nss package from -current resolved the issue. duh!

  6. hannibal

    Hi Eric, as always thanks for your work.

    I just want to notify you that your widevine plugin needs to be updated. HBO GO and Amazon Prime Video stops working with your version. Latest is version is now 4.10.1440.18 – I’ve tested it and it works for all VOD services I have.

    • alienbob

      Thanks hannibal for reporting your issue. I will update the package. I see that there’s even a newer version available already.

  7. 3rensho

    OK, applied your patch for the 77.0.3865.75 build and it went fine. Thanks again.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑