My thoughts on Slackware, life and everything

Last maintenance release in KDE 4.9 series

The KDE developers are already well underway to a 4.10 release, having published the second Beta yesterday. But as I stated before, I will stick with the 4.9 series until at least there is a stable release of 4.10. Today marks the final update in the 4.9 series. With the publication of KDE Software Compilation 4.9.4 we are at the end of the maintenance cycle. Check out the release notes if you want to know all about what happened in the past month.

I think that 4.9.4 is a perfect companion for people running Slackware 14 or current.

My Ktown packages for KDE are specifically targeting Slackware-current, since that is what they are built on. At the moment, the development of -current has not deviated much, so that the KDE 4.9.4 packages will work well on Slackware 14 as well. That is why you will find the packages in a “14.0” directory.

Whether you are upgrading from the stock KDE of Slackware, or if you are upgrading from my previous 4.9.3 packages, you will find proper installation/upgrade instructions in the accompanying README and you are strongly advised to read and follow them.

Highlights for the new set of Slackware packages:

  • You will find five updated dependencies compared to Slackware’s own KDE 4.8.5: akonadi, qt, shared-desktop-ontologies, soprano, virtuoso-ose.
  • Since qt-4.8.4 was released a few days ago, I decided to add this version to the package set. I would have had to rebuild qt anyway in order to apply fixes for crash bugs, but 4.8.4 should be better even..
  • I had upgraded some of the “extragear” of KDE in my 4.9.3 package set and they are kept for 4.9.4: you will find new versions of kdevelop and kdevplatform, as well as oxygen-gtk2.
  • I had added a new package oxygen-gtk3 to my 4.9.3 set which is also carried to this 4.9.4 set. The package should give any software which uses the GTK+3 widget set a nice integrated look and feel when you run it in KDE.
  • And to conclude, I have added an entirely new package to this KDE 4.9.4 set, “kio-mtp” which is required in order to access and manage files on devices running Android 4.0 and later. I have not tested this, and am hearing mixed reports about its usefulness. Let me know if you use this!
  • Compared to KDE 4.8.5, there were two package removals:
    • kdemultimedia has been split up into several smaller individual packages.
    • ksecrets has been removed completely in the 4.9.x series.

Download locations (using a mirror is preferred, both my own taper and Willy’s server are fully synchronized):


Have fun! Eric



  1. Mike Langdon (mlangdn)

    Thanks, Eric! Hope your trip went well and was productive.

  2. escaflown

    Thanks Eric!

  3. just a passive visitor

    wohoo it’s here!
    Thanks for the hard work!

  4. kkady32


  5. Hygor Hernane

    Thx Eric. Hows KDE4.10 beta going? Need any help?

  6. Phil Bevan

    Have tried my Nexus 7 (Android 4.2.1)with kio-mtp. It shows up as “Portable Media Player” in Dolphin, but when I try to select it, get an error message:
    ” Malformed URL udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6.”
    Have tried with USB debugging on and off

  7. jaycee

    @’Hygor Hernane’
    As stated in his blog post, Eric isn’t planning on packaging pre-releases of KDE SC 4.10. If you’re curious to try it though, I recommend downloading the recently released Kubuntu 13.04 Alpha 1, which seems to ship a largely unmodified version of KDE SC 4.10 Beta 1. Mageia 3 Beta 1 will also be released soon, which will ship with a mildly (and, I must admit, beautifully) customised version of KDE SC 4.10 Beta 1. Personally though, during my use of Kubuntu 13.04 Alpha 1, I haven’t noticed any compelling reason to prefer KDE SC 4.10 to 4.9.
    Btw Eric, many, many thanks for your KDE SC 4.9.4 and LibreOffice 3.6.4 packages! I can’t wait to try them out after reinstalling Slackware 14.0 on December 21st! 😀

  8. Gabriel Yong

    Thank you! Eric

  9. gmg

    Thanks, Eric, for all

  10. escaflown

    Got the sane error as Phil with Dolphin and a Nexus 7.

  11. Alan Aversa

    My plasma-desktop toolbar’s icons went missing with this upgrade. E.g., Kopete’s icon and other app’s small icons no longer shows up…

  12. jaycee

    Hey Eric! I just checked the KDE SC 4.9 release schedule, and it appears they’ve recently added a KDE SC 4.9.5 release to it…

  13. Sam Albuquerque

    Thanks for the update Eric.

    By the way the link to 14.0 in the third para has a missing colon.

  14. CD eject problem

    Hi Eric,

    This is awesome, thank you. After updating on to you 4.9.4 packages on my slackware64 14 system I no longer have automatic cd eject from kde apps such as kaudiocreator or from device notifer.



  15. CD eject problem

    In case it’s useful, I get the following output when failing to eject cd from dolphin:

    An unspecified error has occurred.: Method “DriveEject” with signature “s” on interface “org.freedesktop.UDisks.Device” doesn’t exist

  16. Arthur

    Gave error in compilation:

    what can it be?

    I’m still a layman, I do not know what you hear.

  17. alienbob


    It looks like you are compiling KDE on a 64-bit Slackware with 32-bit OpenAL libraries installed. My guess is that you have a multilib system. The SlackBuild for KDE is not written to mind a multilib setup, so what happens in your case if that the kdegames configuration finds the 32-bit OpenAL libraries installed, thinks it is useful for providing some games with better sound, but at the linking stage the linker is unable to use the 32-bit library with the 64-bit KDE binaries, causing this failure.

    You can see if the instructions in are helpful, but otherwise de-install your 32-bit OpenAL package so that KDE will compile, and then re-install it afterwards.



  18. Arthur

    Very many thanks.

    I’ll try to do that now.

  19. Arthur

    Muito muito obrigado.
    vou tentar fazer isso agora.

  20. Johnny

    Hi Eric,

    I just want to know how to proceed with that files
    # find /etc/ -name “*.new”
    # slackpkg new-config


    I think (O)verwrite is a Goog choice? Am i ok?

  21. alienbob

    Johnny, generally speaking, if you never edited one of the original files yourself then it is OK to let them be overwritten with the .new files.
    If you made any manual changes to the original files then you need to inspect the differences between the original and .new file and determine how to merge their contents.


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 ↑