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



KDE 4.14.0 – no big surprises

The new major release of KDE 4 has been made available. KDE Software Compilation 4.14.0 is the first of four iterations which will all see the light of day this year, 2014 (KDE 4.14.3 will be released on 11 November). A relatively short cycle, caused by the parallel development towards Frameworks 5 and Plasma 5. What’s still missing for Plasma 5 is the KDE Application ports to Qt5 and the Frameworks and this is where most of the action is nowadays. There is nothing really worthwhile to mention about KDE 4.14 if you look at its feature plan. Nevertheless KDEPIM is being worked on a lot and judging by the activities in the applications’ GIT repositories everybody is still alive and kicking out code. The previously mentioned announcement page has more details about the individual application improvements.

Anyway, like I said: even though this is a new major release, it is more a polishing update to the KDE Applications. That did not restrain me from building new KDE 4.14 packages on Slackware-current. I was out of the country this week (my son is glad about the freedom that gives him around the house …) so the release of my new packages was somewhat delayed, but now that I returned I am going to fulfill my promise and create KDE 4.13 packages for Slackware 14.1 somewhere during the next week.

Akonadi is the only dependency that was upgraded after my KDE 4.13 packages. The KDE 4.14 package-set uses two sources from previous major releases because no new tarball was made available for KDE 4.14. Those are: kactivities-4.13.3 and kde-workspace-4.11.11.

How to upgrade to KDE 4.14.0 ?

You will find all the installation/upgrade instructions that you need in the accompanying README file. That README also contains basic information for KDE recompilation using the provided SlackBuild script.

You are strongly advised to read and follow these installation/upgrade instructions!

Where to find packages for KDE 4.14.0 ?

Download locations are listed below (you will find the sources in ./source/4.14.0/ and packages in /current/4.14.0/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric


Comment from Deny Dias
Posted: August 23, 2014 at 04:02


The title of your article is precise: no big surprises.

This update was totally smooth, kinda different of what we had with 4.13.3.

Thank you for all this!

Comment from Thiago Silvino
Posted: August 23, 2014 at 04:25

Tks Eric! It’s always good to the updated KDE for Slackware.

Comment from Victor
Posted: August 23, 2014 at 14:52

¡¡Gracias Eric!! Thanks Eric for the great work you do!!

Comment from Eduardo
Posted: August 23, 2014 at 21:39

Thank you Eric!!

Comment from Ricardo
Posted: August 23, 2014 at 21:48

“I am going to fulfill my promise and create KDE 4.13 packages for Slackware 14.1 somewhere during the next week”

Wow, I didn’t remember that promise so here comes an anticipated and highly enthusiastic “Thank you!” from a 14.1 user 🙂

Pingback from Links 23/8/2014: | Techrights
Posted: August 24, 2014 at 01:27

[…] KDE 4.14.0 – no big surprises […]

Comment from Mike Langdon (mlangdn)
Posted: August 25, 2014 at 16:34

Thanks Eric! Upgrade was smooth as always. 🙂
Not sure yet if I’ll give KDE-5 a spin. I want to, but I’ll need some extra time off in case things go south.

Comment from Ricardo J. Barberis
Posted: August 25, 2014 at 17:27

I don’t know wether to report this here or on your other post, but here it goes:

The only issue I have found so far is with kwallet manager not showing up. If I run it through Alt+F2 to configure it to be shown in the tray bar, it asks me for my root password to make the changes effective, but it still doesn’t show up in my tray.

This is on a full Slackeware 14.1, 64 bits + ktown packages installed via slackpkg+

Anyone experienced the same issue?

Comment from LOE
Posted: August 27, 2014 at 15:53

I just install KDE-4.14.0 (with all deps) and get this error for my mail connections (about akonadi):
The server protocol version is 37, but at least version 44 is required

I have slackware-current and akonadi-1.13.0

What may be wrong in my situation?


Comment from Davide
Posted: August 27, 2014 at 23:56

Hi! Thank you very much for this release.

I am compiling from sources and I have found that qt-gstreamer shipped as dependecy is too old (0.10.3); artikulate fails to compile as it needs it to be >= 1.19.0; with the git version (1.2.0), it compiles fine 🙂

Comment from LOE
Posted: August 28, 2014 at 15:34


I reinstall KDE-4.14.0 again and now it works.

Comment from alienbob
Posted: August 28, 2014 at 16:38

Hi Davide

I guess you did not read the README then…

The artikulate package now requires gstreamer-1. Slackware still comes with gstreamer-0.1 and therefore I skipped artikulate this round. For KDE 4.14.1 I will investigate into adding gstreamer-1 to the ‘deps’. The 1.x and 0.1 versions can co-exist on the same system.


Comment from Davide
Posted: August 28, 2014 at 17:37

Hi Eric,

yes, I totally ignored the README, I thought it was only about for the precompiled packages; and I even ignored the advice to _not_ ignore reading the README; tyvm, next time I’ll more care

Comment from Willy Sudiarto Raharjo
Posted: August 28, 2014 at 23:08

@Ricardo J. Barberis
Are you running stable or current machine?
As Eric said, this packages are meant to be installed on current machines

Comment from Ricardo J. Barberis
Posted: August 29, 2014 at 01:01

@Willy Sudiarto Raharjo: I’m using 14.1 stable but with 4.13.3 compiled for it, not the packages mentioned here.

I posted here because I didn’t see a separate announcement for 4.13.3 on 14.1 (well there was one but mixed with other things 🙂 )

Comment from Willy Sudiarto Raharjo
Posted: August 29, 2014 at 06:44

Well, the KDE Framework 5 should be built using the same library and KDE 4.x, not mixed between -stable and -current.

I think this *may* be your issue

Comment from Ricardo J. Barberis
Posted: August 29, 2014 at 17:51

Willy, I dont’t have Frameworks 5 installed, I’m using Slack 14.1 with Eric’s KDE 4.3.13 packages compiled for it, I didn’t compile them myself.

Anyway, this is mostly an annoyance, probably a mangled .desktop file somewhere. Will research it more this weekend if time permits 🙂

Comment from Stephan
Posted: September 14, 2014 at 15:13

Hi Eric and Willy,

after upgrading to this new KDE version Digikam does not run for me anymore. The error message is: error while loading shared libraries: . I have tried to upgrade Digikam to from 4.0.0 to 4.2.0 ( but this fails due to libkgeomap not being found on my system. I now still have Digikam 4.0.0 installed (which does not run anymore) and I can not upgrade to 4.2.0 due to the compile error. Any idea what is wrong here. It might be LibKippi that causes the issue.

Cheers and all the very best from Berlin


Comment from Willy Sudiarto Raharjo
Posted: September 14, 2014 at 16:13

digikam 4.2.0 is built fine here on my system and it links correctly to libkgeomap

ldd /usr/bin/digikam
. => /usr/lib/ (0xb6d69000)

normally after upgrading KDE to newer version (4.13 -> 4.14), you need to rebuilt digikam since it’s linked to several KDE libraries, such as marble.

Comment from Stephan
Posted: September 19, 2014 at 12:46

Sorry for the slow response Erich and Willy,

I am running Aliens multilib libraries on my Slackware current machine.
This is the output of “ldd /usr/bin/digikam” on my machine: => /usr/lib64/ (0x00007fc08147f000)

I still can not compile digikam 4.2.0 on my machine but I managed to get digikam 4.0.0 to run on my machine.

Any idea why 4.2.0 does not compile with the libkgeomap error message would be very much appreciated.

Cheers and thanks from Berlin

Comment from Willy Sudiarto Raharjo
Posted: September 20, 2014 at 11:55

have you tried this?

Comment from Stephan
Posted: September 22, 2014 at 12:17

Hi Willy and Eric,

unfortunately it still fails when I try the hint Willy sent. The error message is:

fatal error: libkgeomap/tracks.h: No such file or directory

Any more ideas from your side are very much welcomed.

Please don’t regard this as very urgent. It is more a pasture.



Note: Eric, can you see all the characters are in this thread come out as I type them. This wasn’t the case with earlier Chromium releases. At least for me. I had to search for the right characters and especially the German “ä, ö, ß, ü” were never printed right. Now all is fine (((-: !

Comment from alienbob
Posted: September 22, 2014 at 12:46


Note that I do not ship digikam in any of my repositories, and do not use it either, so I can only copy/paste information found on the internet.
The digikam support forum has a thread mentioning your error:

Comment from Stephan
Posted: September 26, 2014 at 17:34

Hi Eric,

thanks for your help with this little issue. I had found this post as well and tried it but since I ma using sbopkg I wasn#t able to do this “clean up cmake cache, or delete cmake buil dir”. I am not completely new to slackware but I am still a beginner.

If you could post me a short post how to do delete cmake or how to clean it up with sbopkg I would be grateful Again this is absolutely not urgent or critical.

Thanks Stephan

Comment from Willy Sudiarto Raharjo
Posted: September 27, 2014 at 11:26


Can you list other packages (outside of Slackware’s core packages) that’s installed on your system?

I assume that you did a full installation of Slackware…

Comment from Stephan
Posted: December 18, 2014 at 14:40

Hi Willy and Eric,
I have now resolved the issue with Digikam 4.5.0. It was an issue with the ffmpeg package version 2.4.3 from Eric’s current restricted repository. I removed this one replaced it with ffmpeg 2.1 as well from Eric’s current restricted repository, recompiled opencv and afterwards Digikam 4.5.0 and all is fine now. I was even able to compile the hugin plugins and they as well work fine for me now.

Cheers and thanks for your help.


Write a comment