My thoughts on Slackware, life and everything

KDE SC 4.10.0 released

Right on time, here is KDE Software Compilation 4.10.0. We left behind the 4.9 series but since this is a “zero release” I will keep my 4.9.5 packages around for a while. With this 4.10 series, one of the most interesting new features for end-users is the enhanced scripting possibilities for Plasma Workspaces (using QML, the Qt Markup Language and QtQuick) and the KWin window manager using external scripts. A new print manager has been added as well.

I have had packages ready for a few days already, and that allowed for limited testing by the people I trust. No strange bugs surfaced, if there are any left I hope you will uncover them πŸ™‚

Remember: my ktown packages for KDE are meant to be used on Slackware-current, but I built this set of packages on Slackware 14.0. It allows these KDE 4.10.0 packages to work on Slackware 14 as well as -current.

How to upgrade to KDE 4.10.0? Whether you are upgrading from the stock KDE 4.8.5 of Slackware 14.0/current, or if you are upgrading from my previous 4.9.5 packages, you will find all the installation/upgrade instructions that you need in the accompanying README file.

You are strongly advised to read and follow these instructions!

Highlights for the new set of Slackware packages:

  • You will find nine updated dependencies compared to Slackware’s own KDE 4.8.5:Β  PyQt, akonadi, attica,phonon-gstreamer, qt, shared-desktop-ontologies, sip, soprano, virtuoso-ose. Several of those were updated after my previous 4.9.5 packages. I added a new one as well: qjson.
  • Some of the “extragear” of the KDE in Slackware 14/current has been updated: with new versions of calligra (accompanying the KDE 4.10.0 release), kdevelop, kdevplatform, oxygen-gtk2, skanlite (already updated for my previous package sets).
  • The “extragear” section also introduces new packages (compared to the stable Slackware):Β oxygen-gtk3 – which should give any software which uses the GTK+3 widget set a nice integrated look and feel when you run it in KDE; and kio-mtp which is required in order to access and manage files on devices running Android 4.0 and later. Starting with the KDE 4.10.0 release, I also added libkscreen and kscreen – this is a new screen management software which plugs into the System Settings of KDE’s Plasma Workspace. It tries to make multilple-screen management as easy as possible
  • Compared to KDE 4.8.5, but also compared to KDE 4.9.x, there were some package removals:
    • kdegames has been split up into several smaller individual packages, starting with 4.10.x
    • kdemultimedia had been split up into several smaller individual packages already, starting with 4.9.x.
    • ksecrets has been removed completely since the 4.9.x series.
    • printer-applet has been replaced by print-manager since the 4.10.0 series.

Download locations (using a mirror is preferred:

Have fun! Eric


  1. Chris

    Thank you very much, Eric!
    One thing: The description and signatures are missing for cmake in deps.

  2. Armin

    Hi Eric,

    Glad to see you feeling well again! Thanks for the packages. Small question: do I need to do anything for oxygen-gtk(2,3) to work (like cp the gtkrc-2.0 file) or is it out of the box?

    Thanks and cheers!

  3. alienbob

    Hi Chris

    For cmake, I only added the sources but no package. You need this newer cmake only if you want to rebuild KDE 4.10.0 on Slackware 14. An uptodate cmake has already been added to slackware-current.


  4. Mike Langdon (mlangdn)

    Thanks Eric! I should be going to bed after just finishing a 12 hour shift, but I have to get this done first. πŸ™‚

  5. kabamaru

    Thanks, Eric. Much appreciated as always πŸ™‚

    There’s a small typo in file alldeps.SlackBuild:


  6. Aaron W. Hsu

    Looks good! I’m downloading now and I hope to give it a shot. Thanks for this!

  7. Aaron W. Hsu

    I just gave this a shot, but for some reason I cannot determine if appmenu-qt is installed? Do you bundle it with the other packages? I’d like to try it out.

  8. Beelzebud

    Thanks for the packages!

  9. david

    All my web browsers lost the ability to log in to after upgrading to KDE 4.10. A reinstall of slackware sorted it out.

  10. Alan Aversa

    It seems they got rid of window tiling!

  11. Victor

    Thank you Eric!

  12. Felipe Weber

    So just installed KDE 4.10 in my Slackware machine, plugged in my HDMI table to watch a movie and – TA-DA! – looks like it’s finally configuring the monitors and resolutions by itself without asking me to configure it! (but still asking if I want to, which is great, but it actually did exactly what I expected automatically including choosing the right resolutions).

    Thanks again for packaging it, Eric

  13. laitcg

    Just installed… Nice… had to recompile calibrey, Just FYI.

  14. Willy Sudiarto Raharjo

    @laitcg: what’s the connection between KDE and Calibre?

    @Alan: yes, they removed the support in KDE 4.10. See

    @David : I don’t see any connection between browser and KDE. They are not tightly coupled

  15. Beelzebud

    @Willy: I wish I had written it down, but it was concerning the new indicator app in 4.10, from what I could tell. I just rebuilt it from Eric’s ‘build’ directory and it works fine now.

  16. alienbob

    Willy, laitcg, it is the sip package upgrade as part of KDE 4.10.0 which breaks calibre’s dynamic build. I installed my static version of calibre (the one in my 13.37 directory) and that worked fine because it has an internal version of sip.


  17. david

    Behaviour as follows – everything working fine with KDE 4.9.5 on top of Slack14. Upgraded to KDE 10. Opera, Firefox and Konqueror unable to log in to disqus, despite both Opera and Firefox being set to do so automatically and despite both being able to do so prior to the upgrade.
    Solution – keep home partition, wipe root and reinstall Slackware. Upgrade KDE back to 4.9.5 – all browsers regained their ability to log in automatically to disqus without any input from me.
    If the problem didn’t follow the 4.10 upgrade then coincidence was playing with me.

  18. Willy Sudiarto Raharjo

    @laitcg: Sorry, i didn’t know that sip could cause the problem as i don’t see it as Calibre’s requirement and it was working just fine for me (probably because i had recompiled calibre after using KDE 4.10)

  19. alienbob

    Hi Willy

    SIP is included with Slackware, that is why it is not needed on to list it as a dependency. But apparently the version change of SIP breaks calibre.


  20. Willy Sudiarto Raharjo

    @Eric, i mean not listed in Calibre’s requirement on their page πŸ™‚

  21. alienbob

    Ah, that is what you meant.
    Well, sip is a dependency of PyQt and PyQt is a dependency of calibre.


  22. cwizardone

    Many Thanks! Best KDE 4.xx, to date.
    One caveat: Gwenview cannot find the kipi plug-ins from digiKam as it has in the past.

  23. Willy Sudiarto Raharjo

    @cwizardone: which digikam version do you use?
    if you have used digikam 3.0.0-rc, then you should have no problem with it. I’m using 3.0.0-rc already, so it’s showing up on my system here

    digikam 3.0.0 should be released shortly, because they depends on some library that shipped with KDE 4.10, that’s why they can’t release it before KDE 4.10 gets shipped

  24. cwizardone

    @Willy Sudiarto Raharjo,
    digiKam 2.9.0. I don’t want to use digiKam at all, but it is, apparently, the only way to get the kipi-plug-ins. Not too fond of being forced to install something I otherwise have no use for and won’t be using.

  25. David

    Hi Eric,
    thanks as usual for the great work.

    After upgrading, I miss β€œHighlight Selection” plugin in Kate. Can you confirm me that this is a problem in KDE package?

  26. alienbob

    Hi David

    No idea, I never use Kate so I can not confirm or deny that this is a bug. But, if you discovered a change in behaviour I think it is best if you open a bug report for it at

    Cheers, Eric

  27. David

    Hi Eric,
    a bug has been already opened by someone else:

    Can I ask you which text editor you use when coding?

  28. alienbob

    I always and only use vi (either elvis or else vim if I want to have syntax highlighting).
    Even at work, in Windows, I installed Gvim for Windows because I prefer that to notepad…


  29. cwizardone

    @Willy Sudiarto Raharjo,
    Thanks! Installed digiKam 3.0.0, and the plug-ins are again working in Gwenview.
    Thanks, again.

  30. Willy Sudiarto Raharjo

    @eric, have you tried notepad++ in windows? They are quite good and i used them as well in windows

  31. jaycee

    Hey Eric! Thanks so very much for creating this set of packages, especially for Slackware 14.0 users! I simply can’t wait to try them out tomorrow night when I have access to my Slackware 14.0 DVD to reinstall it! Thanks also for the LibreOffice 4.0.0 packages! πŸ˜€
    I just noticed that you said you plan to eventually remove the KDE SC 4.9.5 packages. Does this mean you intend to keep a set of KDE 4.10 packages available for Slackware 14.0 users? Because I expect that you’ll want to go back to compiling KDE SC 4.10 on -current in the coming months as preparation for the next release of Slackware, will you not? Or do you think the next version of Slackware will use KDE SC 4.11?
    (Btw, you forgot to mention one of the highlights of KDE SC 4.10 – a nice default wallpaper! :D)
    Btw, is your cough any better than it was last week? Have you fully recovered from your flu?
    Thanks again Eric! πŸ™‚

  32. chrisretusn

    Thanks Eric. So far all is well. KDE 4.10.0 did break digiKam 2.9.0; a recompile didn’t fix it. As luck would have it, I noticed digikam 3.0.0 has just been released. digiKam is now once again working.

  33. Willy Sudiarto Raharjo

    Chris: digikam relies in some library of KDE, so an upgrade would definitely break digikam. It’s also depends to KDE version-spesific libraries, so 2.9.0 will not compile against 4.10.0. You should upgrade to 3.0.0.

    The same goes when next KDE gets released, but that will be long way to go…

  34. alienbob

    Hi Jaycee. I intend to keep at least one version of KDE available for Slackware 14.0. I know that Pat considers upgrading the KDE packages in -current, at least that is what he replied to someone who emailed us with a KDE question. If that happens, I will still try to compile my next set of KDE packages for Slackware 14. If those work without errors on -current at least.

    The reason that I said I would keep the 4.9.5 packages available for now, is because KDE 4.10.0 is not bug-free and some people will want to wait with an upgrade to 4.10 until the first point release.


  35. alienbob

    Willy, I also have notepad++ installed πŸ™‚


  36. LoneStar

    hi everybody,
    I have 3 installations of 4.10.0 (64 and 32) and in all of them kdeinit4 is segfaulting regularly, quite often. Wallpaper goes black, and plasma dies. It automatically restarts after a few seconds.
    What could be causing the crash?
    Is there any

  37. alienbob

    Hi LoneStar

    Did you upgrade from a previous KDE version? I had to delete my KDE cache directories in order to run KDE 4.10 without Plasma issues:



  38. LoneStar

    yes I did upgrade from 4.9.5 (and earlier). Thanks for the suggestion! I’m gonna try πŸ™‚

  39. ecoslacker

    Hi Eric thanks for share all your work!
    I’m using your KDE packages right now on Slack 14.0, but I have the SIP problem (laitcg, Willy above) using the Eric4 IDE for python and QGIS.
    Is there a way to fix this problem?
    Great work and KDE 4.10 is so nice!

  40. Willy Sudiarto Raharjo

    Ecoslacker: have you tried recompiling the package?

  41. ecoslacker

    Hi Willy,
    Yeah I tried recompiling at least for Eric4 (QGIS takes more time) and I get this error:
    RuntimeError: the sip module implements API v9.0 to v9.1 but the PyQt4.Qsci module requires API v8.1
    whe using the SlackBuild from SBo.

  42. alienbob


    Your error indicates that QScintilla is the problem. It has not been rebuilt for a while and that may be causing this API incompatibility issue.
    Try rebuilding QScintilla (it is in the “L/” series).


  43. ecoslacker

    Thanks both of you! Recompiling QScintilla solved my problem and I have Eric IDE again… going for QGIS.

  44. Kenjiro

    alienbob, I also needed to upgrade cmake because of digikam. I had it compiled and installed before kde-4.10.0. Now I was trying to rebuild it, then it complained about cmake’s version. So… new version of cmake on the way πŸ˜‰

  45. Kenjiro

    Ouch! So nice, digikam failed to build anyway (not because of cmake)

    /tmp/SBo/digikam-2.9.0/extra/kipi-plugins/common/libkipiplugins/tools/kprawthumbthread.cpp: In member function ‘virtual void KIPIPlugins::KPRawThumbThread::run()’:
    /tmp/SBo/digikam-2.9.0/extra/kipi-plugins/common/libkipiplugins/tools/kprawthumbthread.cpp:112:24: error: ‘loadDcrawPreview’ is not a member of ‘KDcrawIface::KDcraw’
    make[2]: *** [extra/kipi-plugins/common/libkipiplugins/CMakeFiles/kipiplugins.dir/tools/kprawthumbthread.cpp.o] Error 1
    make[2]: Leaving directory /tmp/SBo/digikam-2.9.0/build’
    make[1]: *** [extra/kipi-plugins/common/libkipiplugins/CMakeFiles/kipiplugins.dir/all] Error 2
    make[1]: Leaving directory /tmp/SBo/digikam-2.9.0/build’
    make: *** [all] Error 2

    (I was building it with “-j1” to be sure)

    Any hints?

  46. alienbob


    As discussed further up on this same page, do not try to build digikam-2.9.0 but move to 3.0.0 instead.


  47. Kenjiro

    Wird thing is that I tried to build kipi-plugins (from SBo) and I believe I got the same error.

    Anyway, downloading digikam-3.0.0-rc to try out. Thanks

    And as usual, you’ve been doing one heck of a job πŸ˜‰

  48. Willy Sudiarto Raharjo

    @Kenjiro: digiKam 3.0 is out, why do you use rc?
    kipi-plugins is now part of digikam, so it’s no longer needed to build it separately

  49. cwizardone

    What if you don’t want digiKam on your computer? Why are we being forced to install digiKam if we need the kipi plug-ins for other KDE applications, e.g., Gwenview?
    BTW, since installing 4.10, the icons on the desktop are locked in place and cannot be moved, and, yes, πŸ™‚ I’ve checked all the settings. πŸ™‚
    Also, for the last several versions of KDE it is not possible to change the size of the desktop icons. You can go through the motions and click on “apply” but nothing changes.
    Other than that, it has been the best release of 4.xx to date.

  50. Willy Sudiarto Raharjo

    digiKam is one of the approved projects for KDE. It’s just not part of the KDE core packages and it provides additional features, just like Gwenview that can be expanded by the use of the kipi-plugins. They are optional, but since kipi-plugins are mostly used by digiKam, it’s decided to be integrated within digiKam source so the maintainance will be included in digiKam development cycle.

  51. cwizardone

    With all due respect, twaddle.
    A decision to only provided the plug-ins needed for other applications, in yet another application, is solely to force users to download and install that application in the hope it, the unnecessary and unwanted application, in this case, digiKam, will become more popular. Right out of the old microsoft play book.
    Thrown in the evil triplets and there is yet another reason to dump KDE all together.
    If I could just find a better graphics viewer than Gwenview…. Tried them all and so far haven’t one, Linux specific, that is as useful and has as pleasant an interface as Gwenview.

  52. Kenjiro

    Hmmmm weird, I can’t find digikam-3.0 on its site. All I find there is beta and rc versions.

  53. Kenjiro

    So much for clicking on the “Download” link of that site. Following the post on the “news” sections was much better *LOL*.


  54. alienbob


    Checking is always a good idea if you need KDE related software.
    In you will find the 3.0.0 source release of digikam.


  55. Kenjiro

    Already compiled and installed πŸ˜‰

  56. Willy Sudiarto Raharjo

    AFAIK, kipi-plugins are maintained by the digikam developer from the beginning, so it’s normal for them to merge it into a single project to reduce maintenance burden

    As for gwenview, it’s an optional dependency, not a mandatory to build the application

  57. Ron

    Hi cwizardone,

    Did you solve the icons issues with 4.10? I might be able to help.

  58. Kenjiro

    Anyone here got lucky building digikam 3.1.0? I just couldn’t. And first I tried to build 3.0.0. No luck too πŸ™

    Now I am running slackware64-current with KDE-4.10.2.

  59. Kenjiro

    OK, problem solved. All I needed was recompiling opencv πŸ˜‰

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 ↑