LibreOffice 7.3.3 and an update for Chromium 101

LibreOffice Community Edition is now at version 7.3.3. Read yesterday’s announcement on the Document Foundation blog to get the details of this incremental (bug-fix) update.
The 7.3.x releases are the bleeding edge of this popular office suite but nevertheless really stable software.
Support for Microsoft’s proprietary DOCX, XLSX and PPTX files will probably never be 100% spot-on but there is no other Open Source office suite that comes close to the excellent interoperability that LibreOffice offers.

A new set of libreoffice-7.3.3 packages for Slackware 15.0 and -current is now available in my repository.
Note that I compiled them on Slackware 15.0 so if you install them on Slackware -current you will also need to install ‘icu4c-compat‘. This is another package in my repository which contains older versions of the icu4c libraries, in particular the version that is part of Slackware 15.0 but no longer part of -current.

Get libreoffice packages from my own Europe-based server: or my US-based server: ;or any mirror if you wait a day, for instance .
These servers all offer rsync access if you prefer that to http.


I also provided an incremental update for regular and un-googled Chromium as part of Google’s bug-fix program.
Updated packages for chromium and chromium-ungoogled bring the version of this browser to 101.0.4951.54, supporting Slackware 14.2 and newer.
They can be downloaded from the usual places like , , or .

Enjoy the new releases – Eric

10 thoughts on “LibreOffice 7.3.3 and an update for Chromium 101

  1. Thanks Eric.
    I installed chromium-ungoogled, chromium and libreoffice this morning on Slackware64 15.0 + Multilib.
    Posting from chromium-ungoogled and have been using libreoffice `scalc` all morning.
    — kjh

  2. Thanks Eric for latest LO and chromium-ungoogled packages.
    I don’t have the horsepower to compile those big applications by myself within a reasonable time.
    Granted, LO is available as a repackaged binary at SBO but having a package built on and for Slackware gives it a special “flavor”.

  3. Pingback: Links 06/05/2022: FreeBSD 13.1 RC6, GCC 12.1, RIP Alain Baudrez/Wamukota | Techrights

  4. Dear Eric,
    If building LO takes so long it is understandable that you evade building it under 15.0 as well as under Current. In the 3.5 months since the 15.0 release the differences are already such that running a 15.0-built LO under Current requires two compat packages: boost 1.78.0 => 1.79.0 and icu4c 69.1 => 71.1. And the differences will grow over time …
    Personally I do not like compat packages as they tend to make temporary stopgaps more or less permanent. If really necessary I use more targeted temp packages.
    Just for fun I built LO using your SlackBuild under your slackware64-live-current.iso. The times were:
    — real 51m14.661s
    — user 477m34.275s
    — sys 62m20.482s
    so not as bad as I expected.
    Regards, Dick

    1. In the case of Libreoffice the build time is not the determining factor; but disk space is.
      I “hitch a ride” on the server as my primary repository site and disk space is precious and scarce there.
      One set of libreoffice packages (32bit plus 64bit) for a Slackware version consumes 800 MB. If I compile for -current as well as for 15.0 it will take an additional 800 MB from that server space and Pat has commented in the past about disapproving excessive disk usage.
      So, either you install the -compat packages or compile the packages yourself. I provide choice, not dogma.

  5. Thanks a lot for all your great work.
    I really love slackware (just for one or two years) but feel the need of your supportive packages, which I would miss in the bare slackware distribution.

    I updated the LibreOffice, which – at first – did not work, because I am running “current” and I missed out your recent post over here.
    Now I installed your icu4c-compat package as recommended and it runs flawlessly.

    Thanks a lot!
    Great job you are doing!


Leave a Reply

Your email address will not be published.

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