Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



LibreOffice 6 packaged for Slackware

The new major release ‘6’ of LibreOffice was made available almost two weeks ago but I have been struggling with the 32bit build. Despite the fact that my 64bit -current packages for libreoffice-6.0.0 were online for a short while (almost nobody noticed), I did not have anything good to share so I removed those again.
And in the meantime, faster than scheduled because of some serious regressions and a security report, I noticed the release of version 6.0.1 two days ago. I had been busy with new Plasma5, VLC and GCC packages but with those out of the way I set myself again to the task of fixing the 32bit build. And I nailed it, so now I can finally announce packages for Slackware 14.2 and -current.

There’s a lot to write about what has been improved or added to LibreOffice 6, the release page names quite a few already and here is a selection of features that I found striking:

  • modernized look & feel of the user interface
  • gpg-based document signing & encryption, yay!
  • export to epub
  • better unicode font coverage by including a selection of noto fonts
  • improved spell-checker and custom dictionaries
  • improved help system
  • interactive form creation through a new ‘form’ menu in writer
  • impress templates are re-designed into 16:9 format
  • etc…

The Document Foundation has also recorded a video summarizing the best new features of LibreOffice 6. i invite you to take a look at it.

You can get the new libreoffice-6.0.1 packages from my repository or any mirror, like:

I have also added this release of LibreOffice to my just-uploaded PLASMA5 Live ISO which is based on Plasma 5.12 LTS.


Comment from CWizard
Posted: February 11, 2018 at 17:41

Wow, have you been busy!!!!!
Many thanks. Works as advertised.

Comment from kjhambrick
Posted: February 11, 2018 at 20:06

Thank you Eric !

Upgraded libreoffice-5.4.4 with version 6.0.1 on my Slackware64 14.2 + Multilib Laptop.

Works very well for my use-cases.

Thanks again.

— kjh

Comment from gauchao
Posted: February 11, 2018 at 22:34

I know it is never enough, Eric, but thank you again!

Pingback from Links 12/2/2018: Linux 4.16 RC1, ZFS Back in Focus | Techrights
Posted: February 12, 2018 at 22:06

[…] LibreOffice 6 packaged for Slackware […]

Comment from Victor
Posted: February 13, 2018 at 11:50

Thank you Eric !

Comment from Lysander
Posted: February 13, 2018 at 23:43

Great to see you’ve been working on the 32bit since that’s what I use. Thank you so much, Eric. I’m so pleased there are people like you out there working hard to support 32bit archs.

Comment from alienbob
Posted: February 14, 2018 at 00:07

Well enjoy the packages y’all 🙂

Comment from nik
Posted: February 14, 2018 at 08:55

Thanks for all the great job alienbob!

After upgrading libreoffice I get this error:

/usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/ undefined symbol: _ZTVN6icu_6013UnicodeStringE

Any thoughts on that?

Comment from alienbob
Posted: February 14, 2018 at 16:55

nik what version of Slackware are you running (14.2 or -current) and what is the URL of the package you downloaded and installed?

Comment from nik
Posted: February 15, 2018 at 08:57

I’m sorry for not mentioning that info…

I use 14.2 (multilib) and I downloaded everything from here:

The libreoffice packages I installed were:

I also had to update some packages with the following versions:


and make some symbolic links in /usr/lib64/, due to related messages:
ln -s
ln -s
ln -s
ln -s
ln -s
ln -s

This is the message I get when I try to load LO:
bash-4.3$ libreoffice
/usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/ undefined symbol: _ZTVN6icu_6013UnicodeStringE

I also checked it with strings:
root@darkstar:~# strings /usr/lib64/libreoffice/program/ |grep _ZTVN6icu_6013UnicodeStringE

I hope this info is helpfull.

Comment from peebee
Posted: February 15, 2018 at 09:52

Hi Eric
Many thanks…..
Using the 32-bit current version with the quickstarter in the systray…..
Only problem is that after a period (unquantified) it starts to consume 100% of 1 core
Can be “cured” by restarting the desktop (LXDE).
Similar to, but not the same as previous LO/glib2 problems.

Comment from alienbob
Posted: February 15, 2018 at 11:58

nik if you are running Slackware 14.2 you should *never* use packages in the “current” directory of my repository… there’s a “14.2” directory to which contains the package that works with Slackware 14.2.
The libreoffice I compile on Slackware-current simply won’t work on 14.2 because of all the incompatible library updates that occurred between the release of 14.2 and today’s state of development in -current.

Comment from nik
Posted: February 15, 2018 at 12:02

Thanks for clarifying that alienbob!

Occasionally I have used packages from -current to my system without problems.
I’ll get back to a 14.2 package…

Have a good day!

Comment from alienbob
Posted: February 15, 2018 at 14:35

nik, you have already upgraded several other packages to “current”,like glibc and gcc. It may be wise to review your installed packages and revert *everything* to Slackware 14.2 packages. Else you will keep running into missing library issues and/or application crashes.

Comment from nik
Posted: February 16, 2018 at 09:13

I am now aware of that (thanks again for noting) and will do so!
Keep up the great work and many thanks again for your overall efforts.

Comment from Eduardo
Posted: February 16, 2018 at 15:12

Hi Eric. Thanks again! Works like a charm!

Comment from BrianA_MN
Posted: February 19, 2018 at 17:34

Hi Erik, thank you for making packages of the latest LOO. On Slackware64-14.2+multilib, LOO 6.0.1 (for 14.2) installed with slackpkg+. However, when attempting to verify java set to openjdk8 LOO is crashing when clicking on Tools>Options. Tested with multiple odb files. Crash doesn’t happen with LOO 5, but with LOO 5 the automatic filters is so slow I can’t use it. Don’t have the crash in AOO 4.1.5. Any suggestions on how to investigate this crash? Thanks.

Comment from Cesarion76
Posted: February 24, 2018 at 00:32

Hi Eric.
When clicking tools>preferences the app crashes.

Running in console shows this:

bash-4.3$ libreoffice
LibreOffice(19580) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm “Load smb config files from /etc/samba/smb.conf
Error loading services.

LibreOffice(19580) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
LibreOffice(19580) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running ‘net usershare info’
LibreOffice(19580) KSambaSharePrivate::getNetUserShareInfo: “Can’t load /etc/samba/smb.conf – run testparm to debug it

X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42 (X_SetInputFocus)
Resource id: 0x620267a

I’ m running stock x86_64 14.2 + multilib with slackpkg+ for pkg managment.

Thanks for all the work!

Comment from alienbob
Posted: February 24, 2018 at 12:20

Cesarion76 – I would guess that there’s something wrong with your X installation. The only real error is the “X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42 (X_SetInputFocus)”.
What happens if you open the file /etc/profile.d/ and un-comment (remove the #) in the line:

#export SAL_USE_VCLPLUGIN=gtk3

Make sure all the other lines start with a ‘#’.
Then logoff, login again and see if that makes libreoffice work.

Comment from Cesarion76
Posted: February 24, 2018 at 13:52

Hello. The error message is not showing after un-commenting

#export SAL_USE_VCLPLUGIN=gtk3

Still when clicking tools>preferences the app crashes and restarts.

Comment from alienbob
Posted: February 24, 2018 at 17:44

What is the name of the openjdk (or openjre) package you have installed?

Comment from Cesarion76
Posted: February 24, 2018 at 22:52

Hi Eric, I have openjdk-8u151_b12-x86_64-1alien installed.

Comment from alienbob
Posted: February 25, 2018 at 11:27

Well, same here. Take an alternative approach: create a new user account on your computer, login as that new user, start libreoffice and go to tools>preferences. If it does not crash you’ll know the issue is in your own user’s profile. If it crashes, it is a systemic issue. In that case, try another desktop environment (XFCE instead of KDE for instance) to see if that makes a difference. Et cetera, keep trying a single parameter time after time until you find the cause.

Comment from Cesarion76
Posted: February 25, 2018 at 16:22

Eric, login in to another user did the trick.

No crashes in KDE and XFCE. So there’s a problem in my own profile.

Also tried XFCE but also crashes.

I ‘ve deleted ./config/libreoffice/* but still same problem

Should I delete ./kde , etc?

thanks for all the help

Comment from Ricardson
Posted: February 28, 2018 at 02:26

Thank you!!! work pretty good here.

Comment from thim
Posted: March 3, 2018 at 15:12

Hello. Same problem here (tools>options and crash), Slackware 64 full install (but with a newer kernel 4.14).
Problem remains regardless of desktop (Xfce, KDE, Wmaker, FVWM).
Tried /etc/profile.d/ (uncomment each time and a different option). No luck either.
Removepkg libreoffice* and all user’s setings (rm -r ./config/libreoffice). Did not fix it.
Login as a different user. Works.
Tried it in a different computer, fresh installed slack 14.2 64. LO was the only additional package. Worked.
Starting LO in Safe Mode, tried some options there, did not help.
Just wondering, if there is a fix, or something for else to try -apart from creating a new user.

Comment from thim
Posted: March 3, 2018 at 15:15

(ps: my first post here though i using slackware from 2013 with the “help’ of alienbob’s packages. So, thank you for a great work!)

Comment from alienbob
Posted: March 3, 2018 at 19:51

LibreOffice does a lot more than just reading and writing in ~/.config/libreoffice/ – like, accessing the files in your “recent documents” list, accessing desktop theming configuration etc. That is a lot of files in your homedirectory which a freshly created account does not (yet) have.

Try starting LibreOffice from a terminal like this, work for a bit and let it crash. Then examine the file “strace.log” in your current directory (it will be *huge*) and try to find out what it was accessing in your homedirectory when it crashed:

$ lowriter –strace

Comment from Mats
Posted: March 3, 2018 at 21:39

Do you plan to build LibreOffice 6.0.2?

Comment from alienbob
Posted: March 3, 2018 at 21:51

No idea. No time now. There’s lots of other stuff too that needs an update. Real life takes precedence at the moment since package building does not pay the bills.

Comment from thim
Posted: March 3, 2018 at 22:15

Following the advice, i tried with — strace and i found that the crash occurred when lo was accessing /home/thym/.gnupg folder.
After i removed that folder, lo seems to working flawlessly! (of course i ll keep an eye on it for the next couple of days).

Comment from alienbob
Posted: March 3, 2018 at 22:44

thim – I too have a ~/.gnupg folder containing my private and public keyring… but LO does not crash accessing the tools>options menu. Is there someting amiss with the directory access rights and ownerships? Does that directory actually contain a GPG private/public key pair?

But I am glad it works at least, without the need to create a whole new user account.

Comment from thim
Posted: March 3, 2018 at 23:14

After try and error, i found that the file causing the crash was the secring.gpg (inside the initial .gnupg folder). And i am not using a gpg key pair -yet. Anyway, lo works and i am more than happy with this. (btw, 6.0 version looks very nice)

Comment from Cesarion76
Posted: March 6, 2018 at 23:24

Can confirm removing .gnupg did the trick. LO is working great now.

When running “$ lowriter -strace ” no log is generated in my case.

Here is a list of the file/dir ownership in my folder before I deleted it

$ ls -la
total 108
drwx—— 4 cesar users 4096 mar 6 19:00 .
drwx–x–x 76 cesar users 12288 mar 6 18:58 ..
-rw——- 1 cesar users 128 mar 6 19:00 .directory
drwx—— 2 cesar users 4096 sep 12 19:09 dirmngr-cache.d
-rw-r–r– 1 cesar users 0 sep 21 20:44 gpa.conf
-rw——- 1 cesar users 7680 feb 22 2017 gpg.conf
drwx—— 2 cesar users 4096 mar 21 2017 private-keys-v1.d
-rw——- 1 cesar users 1203 feb 19 20:49 pubring.gpg
-rw——- 1 cesar users 1203 sep 22 13:50 pubring.gpg~
-rw-r–r– 1 cesar users 22093 sep 12 19:09 pubring.kbx
-rw-r–r– 1 cesar users 22061 sep 12 19:09 pubring.kbx~
-rw——- 1 cesar users 600 sep 22 13:50 random_seed
-rw——- 1 cesar users 2581 sep 22 13:50 secring.gpg
srwxr-xr-x 1 cesar users 0 sep 21 20:44 S.uiserver
-rw——- 1 cesar users 1280 feb 19 20:49 trustdb.gpg
-rw——- 1 cesar users 858 sep 12 19:09 trustlist.txt


Comment from thim
Posted: March 8, 2018 at 09:14

you can try libreoffice –strace instead of lowriter -strace

Comment from Hugok
Posted: April 21, 2018 at 19:01

Hi eric, i just did a fresh slackware current installation… qbittorrent 4.0.4 and libreoffice 6.0.3 from your current repos does not work even with all the dependencies installed of qbittorrent…
I’m using KDE.

Comment from alienbob
Posted: April 21, 2018 at 19:07

They are broken after latest boost update in -current. That what happens regularly if you decide to install -current instead of a stable release… either you wait for me to compile new packages or you recompile them yourselves.

Comment from aikempshall
Posted: May 21, 2018 at 08:16

From time to time I chase regressions in LibreOffice and sometimes submit very small patches.

For a long time I have had a working clone of the source code sitting on my 14.2 production machine.

Always compiled with –enable-kde4 because I use, on my production machine, kde4.

Trying to compile libreoffice, with –enable-kde5 on a development machine with current and your ktown installed, but I getting errors.

I’ve looked at you libreoffice.SlackBuild and it looks to me that you chosen to compile with either –enable-kde4 or –diasable-kde4.

Have you attempted to compile with –enable-kde5 and found that it doesn’t work or have you another reason not to use –enable-kde5?

Comment from alienbob
Posted: May 21, 2018 at 10:02

I think the Qt5 / KDE Frameworks5 support was added to Libre Office 6.0.0. However: since there’s no such thing as “KDE5” in Slackware-current I saw no point to enable this feature.
I will consider it on the next package build though.

Comment from bl0tt0
Posted: June 29, 2018 at 21:40

Just to chime in here, I was also running into issues with libreoffice crashing when accessing ‘Tools > Options’ on 14.2 multilib, and it seems that the issue may haev to do with conflicting versions of gpgme installed on the system vs. what is used at build time. The pertinent part of the stack trace is:

Thread 1 “soffice.bin” received signal SIGSEGV, Segmentation fault.
0x00007fffe20865f7 in ?? () from /usr/lib64/../lib64/
#0 0x00007fffe20865f7 in () at /usr/lib64/../lib64/
#1 0x00007fffe207f389 in () at /usr/lib64/../lib64/
#2 0x00007fffe207f8a3 in gpgme_op_export () at /usr/lib64/../lib64/
#3 0x00007fffea50cec9 in GpgME::Context::exportPublicKeys(char const*, GpgME::Data&, bool) () at /usr/lib64/libreoffice/program/

Further, looking at the libreoffice.Slackbuild, the source files are pulling in gpgme-1.9.0:


However Slackware 14.2 is only on gpgme-1.6.0:

# slackpkg info gpgme

PACKAGE NAME: gpgme-1.6.0-x86_64-1.txz

If I remove the gpgme system package, then the crash in libreoffice goes away, however course this breaks other things.

I’m not sure if the recent versions of libreoffice will build with gpgme-1.6.0 for the sake of compatibility with 14.2, but perhaps an environment variable can force libreoffice to prefer the included libgpgme?

Comment from alienbob
Posted: June 29, 2018 at 23:23

bl0tt0 if you find a way to compile LO against gpgme 1.6.0 send me the patch. Otherwise you’re out of luck.
It has already cost me many long nights without any success to find a solution. I won’t spend any more time on it.

Comment from bl0tt0
Posted: June 30, 2018 at 19:05

I just did a little further digging on this, and it\’s apparently already been reported as a bug to

Appears to be dubious RPATHS for libgpgme and libassuan. They\’ve fixed it in 6.0.5, but there\’s also a patch here:

Comment from alienbob
Posted: June 30, 2018 at 23:04

bl0tt0 – nice find. I had not ran into that bug report before.
I guess I will have to compile LO 6.0.5 then.

Comment from Pete Christy
Posted: August 14, 2018 at 15:19

Hi Eric, I guess you are probably aware that the latest Slackware updates have broken your LibreOffice package again. Libboost seems to be the villain of the piece this time. I’ve worked around it with an awful kludge, but the real answer is to recompile.

Looking at your slackbuilds on, the latest seems to be for 5.4. You’ve implied in the past that there are issues with building Libreoffice for Slackware, so will this older slackbuild work if updated to reflect the current version 6.1, at the time of writing, I think)?

Or do you have an update in the works?



Comment from alienbob
Posted: August 14, 2018 at 16:04

Pete, the latest libreoffice.SlackBuild is for 6.0.5, not for 5.4.
I have just finished compiling a whole new ‘ktown’ release for Plasma5 which I am not allowed to release before thursday (Applications 18.08 release day). With that finished I am now working on a package for LibreOffice 6.1.0 for slackware-current to fix those boost library issues and bump the package to the latest release at the same time.
as with every bump in the LibreOffice release I am running into trouble and it may take a bit to get to a working package.

Comment from Peter Christy
Posted: August 15, 2018 at 09:50

Hi Eric, and thanks for the update! Yes, I know the latest release of LibreOffice you have published is 6.0.5, but I couldn’t find a slackbuild for anything after 5.4 on the UK mirror, but your link above took me straight to it. I think I need to get some new glasses! 😉



Comment from Nicola
Posted: September 14, 2018 at 00:20

Hi, I`ve a problem with LO 6.1 for both slackware & slackware-64 : if I use calc and want to change a column width .. it shows completely crazy values. I tried to delete the libreoffice settis folder in my home directory, tried to remove and to reinstall the package … nothing, the problem is present. I`checked using other linux distro and there that problem is not present.


Comment from Nicola
Posted: September 14, 2018 at 00:27

Just finished to download LO 6.1 Appimage file. Executing it on my slackware64-current the problem I`ve reported is not present.


Comment from Patrick B
Posted: October 17, 2018 at 16:55

Hi Eric
I tried to install Libreoffice today (not a techie) as follows:

bash-4.3# lftp -c “open; mirror build”
bash-4.3# cd build
bash-4.3# sh libreoffice.SlackBuild

I got this message

Source ‘libreoffice-’ not available yet…
Will download file to /root/build/sources61

and a whole bundle of files were downloaded

Then after a great deal of text, I got the following:

libreoffice.SlackBuild: line 1283: JAVA_HOME: unbound variable
sed: can’t read Makefile: No such file or directory
libreoffice.SlackBuild FAILED at line 1352
and that was the end of the process.

Do you have any idea what the problem might be?

Many thanks

Comment from alienbob
Posted: October 17, 2018 at 19:26

Patrick, why do you want to compile LibreOffice from source instead of just installing the package from my repository?

If you want to compile from source you need to install the build dependencies first. They are: JDK version 8, Apache Ant and perl-archive-zip. Obviously you do not have a Java installed, hence the error.
My advice: use pre-compiled packages and do not try to compile from source if you do not know what you are doing.

Comment from Patrick B
Posted: October 17, 2018 at 20:02

Foolish me, I thought I was just installing it.

Is there a simple step-by-step available somewhere?

Comment from alienbob
Posted: October 17, 2018 at 20:54

Patrick, that information is available in the README in the toplevel of my package repository. This URL will display it straight away:

I also suggest you take some time to get acquainted with Slackware documentation, as obviously you are pretty inexperienced. Start here and read at least the articles linked to in the top part of the start page:

Comment from Patrick B
Posted: October 17, 2018 at 21:08

Many thanks Eric. I’ll do that!

Comment from Patrick B
Posted: October 24, 2018 at 22:34

Hi Eric,
I made a further attempt, using the package this time.
Unfortunately it installed but doesn’t work.

Here’s the reason why:
/usr/lib64/libreoffice/program/oosplash: /lib64/ version `ZLIB_1.2.9′ not found (required by /usr/lib64/libreoffice/program/oosplash)

It seems that I have version 1.2.8

What’s the best way round this?

Comment from Patrick B
Posted: October 24, 2018 at 22:37

Sorry if this is all dealt with in one of those documents you mentioned, but I thought I might say that I’m probably better suited to a more enduser-friendly distribution!

I also tried to install vlc, and had no luck either ….

Comment from alienbob
Posted: October 24, 2018 at 23:10

Patrick, I assume you are running Slackware 14.2 which contains zlib-1.2.8.
Every Slackware stable release receives security patches over time, and those end up in the “patches” subdirectory of the repository. You really should apply those security updates on a regular basis.
For Slackware 14.2, the zlib package got an update and the latest one is in the “patches” directory. At the moment that’s 1.2.11 and I assume that your error will be gone after having upgraded all the packages in slackware64-14.2/patches/packages/

Also if you have issues getting to grips with the distro, this blog is not the best place to discuss. Try your luck in the Slackware forum where many friendly fellow users are ready and able to answer your questions:

Comment from Patrick B
Posted: October 26, 2018 at 12:20

Thank you again for your patience and help.
Patrick B

Write a comment