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.10.4 – packages for Slackware 14

Packaging a new KDE Software Compilation is verging on boring – believe it or not.

The KDE developers are so unbelievably focused on quality and co-ordination that preparing packages for the new release is a matter of checking the “kde-packagers” mailing list for messages about updated dependencies, adjusting the build scripts (disabling obsolete patches, bumping version numbers) and starting the build on a fresh clean virtual machine. It usually does not take more than a single pass to build all the packages for incremental releases.

Real investigative work is usually waiting around the corner only when jumping to a new major release (re-designing KDE.SlackBuild for the new modular build, almost two years back was a good example of that).

And today’s release of KDE SC 4.10.4 is no different – the packages were built without issues soon after I got hold of the sources. Now that the sources are available for public download, I have uploaded my Slackware 14 packages to the servers.

Note that these are built for – and should be used only on – Slackware 14.

I assume it will not take long for Pat to add KDE 4.10.4 to Slackware-current. So if you are running our development version of Slackware, just wait for Pat and do not install my packages – they will have issues on -current.


KDE’s Dolphin File Manager

What to expect of KDE 4.10.4?

As with every incremental KDE release, this brings you “bugfixes and translation updates” and no new functionality. The over 50 recorded bugfixes include improvements to the Personal Information Management suite Kontact, the File Manager Dolphin, and others, according to the KDE 4.10.4 fix set.

How to upgrade to KDE 4.10.4?

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. Please note that if you are not yet running one of my KDE builds, you should upgrade from a (preferably) full installation of Slackware 14. I had some feedback from Slackware users who installed Slackware 14, excluded the whole “KDE” package series from that installation, and then installed my KDE packages on top. That way, you will be missing a lot of packages, several of them essential to the proper functioning of KDE! If you skipped the whole KDE series and install my KDE packages, you still need to get these from a Slackware 14 package tree (the essentials are highlighted in blue):



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

Where to find packages?

Download locations are listed below (you will find the sources in ./source/4.10.4/ and packages in ./14.0/4.10.4/ 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 jaycee
Posted: June 5, 2013 at 16:08

Excellent as always Eric! Many thanks!
Well, if packaging KDE SC 4.10 is getting boring for you, perhaps packaging the 4.11 pre-releases might entertain you? Is that testing initiative KDE started with KDE SC 4.9 still going? Also, I noticed that KDE Plasma Workspaces 4.11 will be an LTS release. Do you think such LTS updates might make it into a Slackware release containing KDE SC 4.11?
As an aside, I may just find myself reviewing the mirror list for slackpkg next month in anticipation of Slackware 14.1

Pingback from KDE incoming -current
Posted: June 7, 2013 at 10:34

[…] for those still running Slackware 14:…-slackware-14/ […]

Comment from david
Posted: June 7, 2013 at 19:24

Hi, after upgrading to KDE 4.10.4 when I type a network path like “smb://” in the address bar, Dolphin says me “invalid protocol”.
I’m sure that the same network path worked well in KDE 4.10.3.
Anyone can confirm this bug/behavior?

KDE people says me that this is not a Dolphin issue.

Comment from Trey
Posted: June 8, 2013 at 05:43

Worked perfectly on my Sager notebook.
Thank you for making this available for Slackware stable users.

Comment from MiRacLe
Posted: June 9, 2013 at 16:59

+David: have same problem in -current branch after upgrade to 4.10.4

Comment from alienbob
Posted: June 9, 2013 at 23:00

Yeah that is a bug in the Samba kioslave. I found a fix, and it will be applied to the kde-runtime package for Slackware 14 (by me) and -current (by Pat).


Comment from david
Posted: June 11, 2013 at 13:14

After upgrading to -current, Dolphin works fine.

Thanks to Eric and Pat!

Comment from alienbob
Posted: June 11, 2013 at 13:40

David (and MiRacLe) – the dolphin bug had been fixed in my own kde-runtime package a few days ago already… same patch as used by Pat in -current. There was no need to upgrade to -current just for that fix…

FYI, there is a RSS feed of “Alien’s Unofficial KDE Slackware Packages” in the right sidebar of this blog, the update to kde-runtime is mentioned there.


Comment from micko
Posted: June 14, 2013 at 15:04

Many thanks, worked perfectly.

Pingback from Alien Pastures » KDE 4.11 – first release candidate available for Slackware-current
Posted: July 20, 2013 at 20:00

[…] also contains basic information for KDE recompilation using the provided SlackBuild script. Earlier blog posts have more information on rebuilding from source and upgrading from Slackware’s own […]

Pingback from Alien Pastures » KDE 4.11 is out
Posted: August 14, 2013 at 23:14

[…] also contains basic information for KDE recompilation using the provided SlackBuild script. Earlier blog posts have more information on rebuilding from source and upgrading from Slackware’s own KDE. […]

Write a comment