The Document Foundation announced version 6.1.2 of their office suite last week. Today, new LibreOffice packages for Slackware 14.2 and -current are done compiling and available in my repository.
Get the packages from my repository or any mirror, like:
- https://slackware.nl/people/alien/slackbuilds/libreoffice/ .
- http://slackware.uk/people/alien/slackbuilds/libreoffice/ .
I also updated the VeraCrypt package to version 1.23, and you’ll find one for Slackware 14.2 as well as -current. Next on the list to update are: handbrake, ffmpeg, mkvtoolnix and probably others that I have neglected. All of these will become available shortly for 14.2 and -current. Fans of Plasma5 will have to wait a bit… Plasma 5.14 is just around the corner but I may wait until 5.14.1.
Have a good weekend, Eric
Many Thanks!
Greatly appreciated!
Hi Eric, usually the 5.x.1 versions of Plasma come so soon after the 5.x.0 that I feel there’s no problem skiping the .0s, at least on my part.
Cheers!
Heh, your text for the handbrake note cuts off for me here, and I thought it was amusing (and still fitting): “…then grab the variant found in my alternative repository where I keep the packages containing code that might violate stupid”
Many thanks Eric.
Dear Eric,
first of all: thank you for the much work you do!
In the moment on my slackware-current installation is a problem with the libreoffice 6.1.2-package. If I try to start libreoffice ist fails. I receive the message: /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var
Best regards
Peter
Peter, do you have a self-compiled version of freetype installed? Upgrade to Slackware-current version of freetype or recompile that package using the sources in the slackware-current source tree and this error should disappear.
Dear Eric,
ty for Your support. But I use the original-freetype-version from slackware-current freetype-2.9.1-x86_64-2. Now I made additionally an re-update. The error still exists.
Best regards
Peter
Thanks Eric!
Many Thanks sir. Working perfectly.
On my Slackware current, it fails because it needs libicui18n.so.61 and libicuuc.so.61 while the version is now .63
Workaround with a couple of symlinks fails because /usr/lib/libreoffice/program/libi18nutil.so: undefined symbol: _ZTVN6icu_6111ReplaceableE
The culprit is the newer package icu4c-63.1-i586-1
Umberto, maybe try the icu4c-compat package (see http://www.slackware.com/~alien/slackbuilds/ChangeLog.txt). My libreoffice -latest is working just fine with -current and the icu4-compat package.
Superb! Thanks Ragnad,
icu4c-compat actually fixes LibreOffice.
In the meantime I have uploaded a set of recompiled libreoffice packages that work with the new icu4c in -current.
Hi Eric
libreoffice-6.1.2-i586-2alien.txz seems to be linked to icu4c-61 so won’t work on a current based system with only icu4c-63
Thanks
PB
PeeBee, libreoffice-6.1.2-i586-2alien.txz is actually compiled against icu-63.1. I just tested and verified this.
You probably have the previous package build still installed.
I noticed that both the old (1alien) and the new, working, package (2alien) are in the 32bit -current repository. I will remove the old package version and re-generate the repository data.
Hello Eric
First thank you for all do. Did you use to include en-US-help with LibreOffice? It is not included in the latest version 6.1.2.1
Thanks again
Wali
Wael, no package was removed. The en_US help is part of the main libreoffice package. All other languages have their own sub-package.
Hi Eric!
I’ve noticed that LibreOffice does’t look at the fonts available in /usr/share/fonts/*/
Do you know if it is an issue with LO itself or with the configuration during compilation? Or another thing?
Thanks in advance.
Fellype
Fellype, I don’t know what you are talking about? Of course Libre Office looks for (and finds the) fonts in /usr/share/fonts/ . Only TrueType fonts of course.
Perhaps you added some new fonts and they are not showing up? In that case, read https://docs.slackware.com/howtos:general_admin:install_fonts
Eric,
I verified that it is happening only in one PC I use. On the other 2 it is OK.
Yes, I added new fonts to /usr/share/fonts/TTF dir. I followed the 3 steps in the documentation you indicated. But LO still not finding the new fonts at /usr/share/fonts/TTF
Strange š
Anyway… thank you.
Regarding: /usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var
I compared directory /usr/lib64/libreoffice/program/ to that in another computer without the symbol error & found 2 old directories:
drwxrwxr-x 2 root root 4096 Apr 26 2014 __pycache__/
drwxr-xr-x 3 root root 4096 Nov 21 2015 python-core-3.3.3/
I ‘rm -rf’d these old directories & no more symbol error.
Prior to eliminating the 2 old directories, I found I could successfully start libreoffice this way:
/usr/lib64/libreoffice/program/soffice.bin
Both computers have libreoffice-6.1.3-x86_64-1alien.txz installed; one was last updated Dec 5 the other Dec 13.
Hope this helps…Bob
PS Muchas gracious AlienBob for your continuing contribution to Slackware. I assume your evolving employment responsibilities are keeping you well focused away from this avocation. Best wishes to you & your family.
Argh…Dec 14 updated libboost stuff to 1.69 & libreoffice-6.1.3-x86_64-1alien.txz depends on 1.68. Just when ya think ya have things sorted out…:-)
Bob Geer you should really watch my repository RSS feed. You would have noticed the ‘boost-compat’ package announcement in there, which will stop-gap the library issue until I have recompiled libreoffice and other packages.
Point taken. Thanx.