My thoughts on Slackware, life and everything

It’s been released: KDE SC 4.4.0

The KDE community has announced the immediate availability of the KDE Software Compilation 4.4.0 (“KDE SC” is the new name of what used to be called just “KDE“). In preparation for this event, the website was re-vamped yesterday to reflect their “shift in marketing and promotion vocabulary”. Looks shiny and new! Also, I think that the new layout makes it easier for people to find information about the KDE community and the software compilation.

Users of small form-factor laptops will be interested to learn that the new Plasma desktop manager now offers two workspace choices. One is the usual desktop-oriented workspace. The interesting addition is a netbook-oriented workspace, with special consideration for the netbook’s smaller screen and typical mobile usage patterns. I have not yet installed KDE 4.4 on my own Asus EEE netbook but I will most certainly do so, later this week!

In order to fully appreciate the work that went into KDE SC 4.4 and learn what has changed since KDE 4.3, you should definitely take the visual tour. Lots of new functionality and usability improvements are hidden beneath this new desktop workspace and just waiting to be discovered and used to the fullest.

Slackware packages galore!

Like I did with the pre-releases of KDE 4.4, I have prepared new goodies for all you Slackers. Get those 32-bit and 64-bit packages for Slackware Linux and install them on your computers (or build them yourself using the accompanying SlackBuild scripts, patches and sources).

You will find all of those at .

Please take good notice of the fact that these packages are built for Slackware-current. You can safely install the KDE 4.4.0 packages if you are running a slackware-current from around 01 february 2010 or newer. Do not try to install these packages on Slackware 13.0.

Slackware 64-bit:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86_64/deps” directory.
  • The KDE 4.4.0 packages themselves can be found in “x86_64/kde
  • And of course, the localization packages (non-english language translations of KDE) are available in “x86_64/kdei“.

Slackware 32-bit:

  • Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86/deps” directory.
  • The KDE 4.4.rc2 packages themselves can be found in “x86/kde
  • If you need a language pack, you can grab one from the 64-bit package tree “x86_64/kdei” since these packages are in fact architecture-independent.

Here are the steps on how you download the packages and install them. You can have an older version of KDE installed, but that is not required. You will end up with KDE 4.4.0 installed on your system.

Instructions are for the 64-bit packages, I think you can figure out how to change them if you want the 32-bit versions:

  1. Download everything in the directory :
    # lftp -c "open ; mirror x86_64"
  2. Change into the directory “x86_64? which has just been created in your current directory:
    # cd x86_64
  3. Remove the no longer required kdelibs-experimental package if you still have that installed. It is part of KDE 4.3.x (i.e. Slackware 13.0 did not have this package). If you do not have kdelibs-experimental on your system, you will get a harmless error message that you can ignore:
    # removepkg kdelibs-experimental
  4. Install/upgrade the KDE 4.4 dependencies:
    # upgradepkg --reinstall --install-new deps/*.t?z
  5. Install/upgrade KDE4.4.0 packages:
  6. # upgradepkg --reinstall --install-new kde/*.t?z
  7. Install/upgrade a language package if you prefer to have the KDE interface in your local language (I used “nl” in the example command, you should substitute your own language code there):
    # upgradepkg --reinstall --install-new kdei/kde-l10n-nl-*.t?z

Of course, you should not run those commands while running KDE…!

If you want to compile the packages from source like I did, that is entirely possible using the provided sources and build scripts. It will take quite a while though…

Have fun, Eric

Note for users of any KDE 4.4 pre-releases:

If you never before installed and used one of the Betas or Release Candidates of KDE 4.4 , then you can safely remove one package,  virtuosoconverter. This package is only needed if you were using “nepomuk desktop search” before this final release of KDE 4.4.0.

# removepkg virtuosoconverter

If you ran any Beta or Release Candidate of KDE 4.4.0 prior to upgrading to 4.4.0, then you will notice that your nepomuk database will automatically be converted from virtuoso v5 to v6, the very first time you login to your KDE 4.4 desktop. This process will take a while (not too long) and will temporarily double the size of your nepomuk database (by default, this database consumes a maximum of 50 MB in your homedirectory below ~/.kde).

If this database is not valuable to you, you can also decide to skip this database conversion by just deleting the database before starting KDE:

$ rm -r ~/.kde/share/apps/nepomuk/repository/*

or by following the instructions in Sebastian Trueg’s tutorial:

If you manually remove the old nepomuk data, you can also remove the virtuosoconverter package of course.

If you do not have any clue about what I am talking about and what you should do, just don’t do anything… and all will be well.

A final remark about nepomuk and strigi – I think that KDE 4.4 finally has a desktop search which is optimized to a level that it no longer eats all your CPU cycles or claim a large chunk of your harddrive. Now I just wish that the strigi developer properly fixes the indexing of my PDF files!


  1. Ismael C

    Great! I’ll be looking forward to hearing more about the notebook mode, I’m really considering buying one (and put Slack on it, of course)

  2. Ponce

    Thanx for these packages: hope to see this stuff in official current soon 🙂

  3. cchalk

    Thanks for these packages! Great work. Can’t wait to see some of the new improvements made in this release.

  4. Eduardo

    Eric, thank you very much for the packages! I’m downloading them now.

  5. Gunnar


  6. BrZ

    Thanks Eric =]

  7. Widya Walesa

    Thanks (again) eric. I’m about download and test it right now…

  8. escaflown

    Thanks Eric! KDE is definitely getting better and better. I’m really happy that Pat picked KDE back then.

  9. escaflown

    Hi Eric,
    Should we put kdelibs-experimental in slackpkg’s blkacklist after the installation? I noticed that after performing the installation, a slackpkg install-new gives the option to install kdelibs-experimental.

  10. alienbob

    Yes, indeed you have to add kde-experimental to the slackpkg blacklist (/etc/slackpkg/blacklist). This package only existed in KDE 4.3.x.


  11. LoneStar

    well done Eric!
    Using both 64 & 32 bit packages in my local systems. Was missing a 32bit build of 4.4rcX, and now I’m quite happy !

  12. ????????? ????????

    Hi Eric,
    I use you’re packages, but there seems to be a problem – It’s tottaly unstable … Plasma broke 3 times for the last 15 minutes … has you expirienced somthing like that … the KDE efect manager is allmost unusable …
    Do you have any idea why this is?

  13. DrTor

    Thanks Eric ! There is only one problem, the flag of the country in switching allocations of the keyboard is badly displayed.

  14. alienbob

    Hi ????????? ????????

    I have no idea why you are experiencing these crashes, I know many people who are using my KDE 4.4 packages and for them it is all very stable. Are you running slackware-current or 13.0? Perhaps you should open a thread on for this.


  15. ????????? ????????

    I’m running current. And I found the culprit: the Kopete try icon right click menu as strange as it sounds … i brakes Kwin for a second … I’ll just avoid using it …

  16. Alan D

    Thanks Eric!

  17. Rich

    Thank you for you packages, Eric!

  18. Aleksey

    Hi Eric,

    Thank you for the packages!!!

    The only issue I’ve experienced is absence of Phonon in /usr/lib64/qt/include.

  19. alienbob

    > The only issue I’ve experienced is absence of
    > Phonon in /usr/lib64/qt/include.

    Indeed, I split phonon out of qt back into its own package. As a result, the phonon header files are now in /usr/include/phonon/


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑