LibreOffice Community Edition 7.3.5 was released last week. The Document Foundation blog has the news on it.
The 7.3.x releases are the bleeding edge of this popular office suite but nevertheless really stable software. Libre Office 7.4.0 is right along the corner (expected release is mid-august) but I might hold out on that first release.
The new package set for libreoffice-7.3.5 (for Slackware 15.0 and -current) can be downloaded from 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‘ and boost-compat. These are other packages in my repository; they contain older versions of the icu4c and boost libraries, in particular the versions that are part of Slackware 15.0 but no longer part of -current.
Get libreoffice packages from my own Europe-based server: https://slackware.nl/people/alien/slackbuilds/libreoffice/ or my US-based server: https://us.slackware.nl/people/alien/slackbuilds/libreoffice/ ;or any mirror if you wait a day, for instance https://slackware.uk/people/alien/slackbuilds/libreoffice/ .
These servers all offer rsync access if you prefer that to http.
I wrestled with the Chromium 103 updates. Most frustrating program to build, ever, considering the time it takes to compile a package and the fast release cycle.
Here’s the heads-up: I have an incremental update both for regular and un-googled Chromium 103, but only after I finally gave up on compiling the 32bit chromium-ungoogled package. The compiler just keeps on segfaulting.
Google’s announcement last week of the 103.0.5060.134 release mentions a couple of vulnerabilities with a security level of ‘high’, so again it’s recommended to upgrade. This release kept my build box busy for several days but with VLC and LibreOffice packages waiting to be built and seeing the chromium-ungoogled compilation fail 4 times in a row at different stages, I had to decide skipping the 32bit chromium-ungoogled package this time. Let’s hope I have better luck next time.
The updated packages for chromium and chromium-ungoogled are available for Slackware 14.2 and newer. I will try to keep supporting Slackware 14.2 for as long as I can.
The packages can be downloaded from the usual places like http://www.slackware.com/~alien/slackbuilds/ , http://slackware.nl/people/alien/slackbuilds/ , http://us.slackware.nl/people/alien/slackbuilds/ or http://slackware.uk/people/alien/slackbuilds/ .
Enjoy – Eric
Thanks A LOT, Eric !
LibreOffice 7.3.5 seems to work fine for my limited use-cases ( reading and writing .xlsx and reading .docx )
And I am posting this note via chromium-ungoogled-103.0.5060.134-x86_64-1alien
Your Packages make Skackware a Joy to Use 🙂
— kjh
Thanks Eric for the update of those “big” applications (LibreOffice and chromium-ungoogled in my case).
Hey, thanks for VLC!
Having a spot of bother regarding libreoffice-7.3.5-x86_64-1alien.txz. Seems to have been compiled against icu4c-69; current is icu4c-71. Soffice throws an error looking for libicui18n.so.69. No worries, you provide the sources, so I just ran the build script so it works with libicu18n.so.71.
Well, that didn’t work. The SlackBuild script throws errors, so I re-installed your package then headed off to the slackware.uk archive and tossed libicui18n.so.69 into /usr/lib64. All to print an envelope. What happened to the arcane art of drawing words with a pen? I could have written the address and return address by hand hours ago.
=-=-=-=
ERROR: Missing files at /tmp/build/tmp-libreoffice/libreoffice-7.3.5.2/solenv/bin/modules/installer/scriptitems.pm line 1211.
Failed to install: No such file or directory at /tmp/build/tmp-libreoffice/libreoffice-7.3.5.2/solenv/bin/ooinstall line 91.
Installing XML files because ‘make distro-pack-install’ fails to do so…
mv: cannot stat ‘/tmp/build/package-libreoffice/usr/lib64/libreoffice/sdk/classes’: No such file or directory
libreoffice.SlackBuild FAILED at line 150
You did not read the post, nor the repository ChangeLog?
It’s right here on this page, in the main article, what you need to do for icu4c.
Of course I didn’t read the above or some changelog for the entire site. I have a bookmark for http://slackware.uk/people/alien/slackbuilds/libreoffice/pkg64/current/, just went there and grabbed the tgz. Same as the last dozen or so versions; by habit. Thank you for pointing out the error of my ways.
I hasten to point out that you used to compile everything against Current. Upon installing icu compat, seems boost needs some attention. Cuurent is boost-1.79.0-x86_64-1
/usr/lib64/libreoffice/program/soffice.bin: error while loading shared libraries: libboost_locale.so.1.78.0: cannot open shared object file: No such file or directory
Learn to live with it. I used to have time in abundance an leave my family orphaned at the kitchen table, but for the two users of my packages I am no longer compiling every package for every Slackware release.
If you come here to report an issue but do not actually read the article you are commenting on… then the race is lost.
By the way; http://www.slackware.com/~alien/slackbuilds/boost-compat/pkg64/current/
Perfect! Many thanks.
PS: Can you please Update OpenJDK to a newer version? JOSM will soon cancel the support of OpenJDK8 and need OpenJDK11 or higher.
“JOSM soon will no longer support this version of Java, you should update to version 11 or better!”
I don’t know what JOSM is… I have not used Java in 5 years anyway.
It’s an editor for Openstreetmap, which I also use a lot. Because it’s maps are much clearer then google maps (for cyclists at least), and without all the commercial shit (which basically works like the more you pay the more obnoxious you are visible on the map, even while totally zoomed out). And because I want to use google products as little as possible.
By the way, Rudis, you can use slack builds to build OpenJDK11:
http://www.slackbuilds.org/repository/15.0/development/OpenJDK11/
There’s even a script for OpenJDK 17.
Oh, thank you!
Hi Eric.
All this takes time and effort from you. Just for that reason, I always try to come here to thank you. It is a joy to have this laptop with latest KDE, LOffice, Browser, etc on Slackware 15. Thanks again.
Hi. Eric.
As always, thanks for your work.
I’ve recently update chromium to 104, and found problem with its internal pdf viewer. It doesn’t work at all – it displays only blank window, no matter pdf I choose. Did you also have this issue? Or It is my local problem?
I have no issue displaying PDF files in Chromium 104, on my local hard disk or via Internet URL. Works as expected.
I am running Slackwar64 15.0 here at the moment.
OK. I found it. PDF files in fact renders but very very slow. It take at least 30 seconds to show simple file, as before it renders almost instatly.
It seems to be global and local issue.
The problem is global because it works in previous versions, and I didn’t make any changes in my configuration.
And local because chrome displays in console: “Warning: disabling flag –expose_wasm due to conflicting flags”. But sadly, I cannot disable “those others” flags to fix 🙁
BTW. I’m using latest multilib current.
alienbob —
Thanks for chromium-104.0.5112.79-x86_64-1alien and chromium-ungoogled-104.0.5112.79-x86_64-1alien
Note for Konrad —
I have no problems with Onine PDF Files on Slackware64 15.0 + multilib in alienbob’s latest chromium-ungoogled.
Online PDF Links ‘just work’.
And if I open a Local File, as URL = /path/to/foo.pdf then chromium-ungoogled rewrites the URP as chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/file:///path/to/foo.pdf
Note it is rewritten as file:/// ( three slashes )
OTOH, if I try URL = file://path/to/foo.pdf ( two-slashes ) then it fails with an error:
PDF.js v2.3.164 (build: 12ff2527)
Message: Missing PDF “file://home/tmp/foo.pdf”.
— kjh
Hi Eric,
I was thinking about building myself – but slackbuild script lists quite a lot of optional dependencies. Then Eureka! Probably AlienBob built this.
My need for LibreOffice is Zotero plugin which generates previews for documents. And I have a lot of pdf’s. Just mess.
Again great thanks for your work. I use solely now your live -current version. This way I have kind of “rolling-release” Slackware.
Best Wishes,
Piotr (igadoter)
Hi Eric,
Just got little strange error while downloading boost-compat -as dependecy for libreoffice. Can’t download checksum file for bosst-compat txz package:
404 Not Found
The requested URL /~alien/slackbuilds/boost-compat/pkg64/current/boost-compat-1.79.0-x86_64-1alien.txz.md5 was not found on this server.
—
Apache/2.2.22 Server at http://www.slackware.com Port 80
Piotr (igadoter)
I see a version number “1.79.0” in your feedback. That was the old package. The new package has version “1.80.0”. if you are using slackpkg+ you may have to run “slackpkg update” still.
Thanks Eric,
Now everything ok.
Piotr (igadoter)
Hi, I’ve an ods file (with macros). I have 2 PC (One Is an AMD desktop PC,
while the other Is an Old Intel Centrino laptop) , both using same Linux
distro (Slackware64-current), same installed packages, same LibreOffice
version (7.3.5). On the desktop PC the ods Is perfectly opened, while on the
laptop .. “Read Error. Format errore discovered in the file in sub-document
contenta.xml”. I tried loadinh from different sources (hdd, USB pendrive) but
nothing: on one it works perfectly wile on the other not at all. Moving back
to Slackware64-15 on laptop LibreOffice returned to work perfectly. Something
recently upgraded in the current branch is causing such problem.
Nicola
You could try extracting “contenta.xml” from the ODS document, which is nothing more than a ZIP file, and then use xmllint to check for inconsistencies in that “contenta.xml” file.
Between Slackware 15.0 and -current I assume there will have been updates to libxml2, perhaps older versions of libxml2 were more forgiving of XML syntax errors?
Just guessing.
I upgraded Slakcware64, and yes, there was a new libxml2-2.9.14 but that docs were perfectly opened. I thought a possible problem could be caused by libxml but when I saw the file correctly opened with libxml2-2.9.14 I was: “OK, and now?????”. What left me perplexed was that 2 systems with same OS, same installed packages (all updated up to yesterday evening), one opened the file and the other not. This morning I installed Slackware64-15 to have a test and after lunch I upgraded it. I’ll check the xml as you suggested me but .. that should be useful if it’s not working on both pcs.
back to slaclware64-current (2022-08-14 iso) and installed LO.
bash-5.1$ xmllint –noout content.xml && echo ok || echo problem
ok
bash-5.1$
while opening the ods wirh LO:
Read Error.
Format error discovered in the file in sub-document content.xml at 2,523861 (row,col).
Looking at the syntax of the document in that position,
“2029”
it correctly closes the previous block (“ce577″/>) and starts the new table block “<table:".