KDE 4.11 – first release candidate available for Slackware-current

A few days ago, the first release candidate of KDE 4.11 was made public – in source format of course. The source version is “4.10.95”. I had an updated KDE.SlackBuild framework ready since the first beta. A re-work was needed because KDE 4.11 splits another four of the big packages in a lot of smaller individual program packags: kdeadmin, kdetoys, kdesdk and kdenetwork.

I took the bait and built KDE 4.11 RC1 on Slackware-current. Uneventful as always if you have the proper KDE.SlackBuild ; I added the new Calligra 2.7.0 (still waiting for the official release announcement but I decided that I have waited long enough) and proposed the new build to Pat. I needed to know if he had plans for Slackware-current. We agreed on Slackware-current sticking with KDE 4.10 for now, and I would upload the package set to my ‘ktown‘ repository.

So here we are, and I can offer you KDE 4.11 RC1 for Slackware-current. Note that this is not going to work on Slackware 14.0 ! If you are eager to try out what’s going to become KDE 4.11 I encourage you to upgrade your Slackware to what will become 14.1 🙂


New KWalletManager user interface; changes to Okular

What’s new in KDE 4.11 RC1 ?

It is recommended to read the feature plan for the new 4.11 series. Most notable changes are the expansion of the use of Qt Quick (the application framework which includes the interpreter language QML), faster Nepomuk indexing (many people keep complaining about Nepomuk), many Kontact improvements, and the start of support for the Wayland compositor in KWin (the window manager of KDE) as well as OpenGL improvements. Overheard during Akademy 2013 (held in Bilbao, ended yesterday) was the fact that KWin may depend on SystemD in future. Bad move, kDE!

How to upgrade to KDE 4.11 RC1 ?

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. Earlier blog posts have more information on rebuilding from source and upgrading from Slackware’s own KDE.

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.95/ and packages in /current/4.10.95/ 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

56 thoughts on “KDE 4.11 – first release candidate available for Slackware-current

  1. Thank you for putting the packages together.
    I’ve ran into one problem, it won’t load the NetworkManager widget and says it can’t find the component.

  2. I just re-read the above. To clarify, it won’t install the widget to the panel. When you move the mouse over the red…. whatever it is suppose be, where I tried to place the networkmanager widget, a box appears with the message that it cannot find the component.

  3. Other problems with 4.11:
    – konqueror in webkit mode crashes on gcc.gnu.org
    – amarok crashes while using Jamendo and changing slider position

  4. Ah, forgot to mention that profile AC is having some problems with power management modules. I think some entries in $HOME/.kde/share/config/powermanagementprofilesrc must be cleaned up (manually)

  5. hm.. has any reasoning started on this info of future dependencies on systemd?

    could it work with a “fake” systemd library put there just to make it work, just like chrome with libpam.so ?

  6. LoneStar – there is no “fake” libpam for Chrome… it is the actual PAM library extracted from the pam package which is created with the sources in extra/source/pam/ …


  7. To sum up the major issues: networkmanager widget does not work, powermanagent acts weird, konqueror in webkit mode crashes, amarok crashes, kwin crashes:

    I do not care much for amarok but if someone reports that the patch works which was mentioned by Willy, then I” rebuild it.

    I wonder if the networkmanagement and kwebkitpart have to be rebuilt. Anyone tried that yet?

    KWin did not crash on me yet, but I have been running in a Virtual Machine so far. I am now upgrading the laptop to KDE 4.11 RC1 because I have another Linux OS on that one, and it is the only machine where I can suirvive a period of non-functional Slackware with KDE.

    I assume that everyone with a problem has already tried creating a fresh new useraccount to see if your crashes are caused by the new packages or by old configuration files?


  8. @Eric

    yes, sorry, I knew that was a wrong statement =)
    with “fake” I was intending that it’s just there to make chrome happy and it’s not really being used for anything else in the distribution.

    So I was wondering if something similar could work with systemd for Kwin, putting there its library without using it for anything else.

    But I guess it’s too early for thinking about this now..

  9. Pingback: 20 anni di Slackware! : LoneStar.it

  10. First quick view of KDE 4.11 RC1 installed on my laptop already pointed out the networkmanager widget issue.
    The kde-workspace package used to have a “/usr/lib64/libsolidcontrol.so.4” library which is now gone, and the widget in the networkmanagement package links directly to that library.

    I am going to rebuild networkmanagement to see if that fixes the issue.


  11. I tried the first attempt on my main desktop, so i can’t leave it as non-functional for long period. Even i have MATE installed, but i still use a lot of KDE apps on my daily activities.

    I will try this on a clean system of Slackware-Current on VM at my office tomorrow.

  12. I built networkmanagement- after I found out that the current networkmanagement- package could not be rebuilt because of a solid-related compilation error. With the new package I have a working NM widget in my KDE 4.11RC1.
    I also rebuilt kwebkitpart and I do not see a crash when konqueror opens gcc.gnu.org.
    I have no issues with kWin, but it had fallen back to XRender for its desktop effects (and several of the desktop effects require OpenGL renderer). When I tried to configure OpenGL 3.0 the KWin crashed immediately, but using OpenGL 2.0 everything is fine. This laptop uses the Intel Open Source graphics driver. Are those with KWin issues running the binary NVIDIA driver?

    I’ll upload the new packages as soon as I have the 32-bit versions ready.


  13. Yes, i’m running NVidia driver and most of the bug report that i found are also using NVidia GPU

  14. The ‘ktown’ repository has been updated with packages for networkmanagement (upgraded to version and kwebkitpart (rebuilt the slackware-current package).


  15. Pingback: Alien Pastures » Security update: flashplayer-plugin

  16. No sound. The system notifications play as they should but there is no sound from any of the applications be they multimedia or a mail received sound from Thunderbird.
    Thanks for fixing the networkmanager widget!

  17. Oops. Somehow the pcm setting in the alsamixer was reeset to zero. Resetting it did the trick, but the question become, what reset it to zero?

  18. @cwizardone:
    Yes, i noticed the same thing when KDE started. Usually it has a sound, but on 4.11 RC1, no sound played.

  19. “Action Policy”? “Configure policies for trusted actions in the system”??!!

    Maybe this has been there for sometime, but I don’t recall seeing it before. It all looks very mickeysoft-windows-ish.

  20. cwizardone – this systemsettings applet is not new, it is part of working with polkit and has been part of KDE’s systemsettings since Slackware 14.
    But I fail to see how this is “mickeysoft-windows-ish” ? System policies are not the exclusive domain of Microsoft.


  21. Went to use Gwenview and it couldn’t find the plug-ins. As one now has to… grrrrrr… install digikam to get the use of the kipi-plug-ins I tried to run digikam and it failed. So I tried to re-build digikam and the process failed with this error:

    /tmp/SBo/digikam-3.1.0/extra/libkgeomap/libkgeomap/backend_map_marble.cpp:642:14: error: ‘class Marble::GeoPainter’ has no member named ‘autoMapQuality’
    make[2]: *** [extra/libkgeomap/libkgeomap/CMakeFiles/kgeomap.dir/backend_map_marble.cpp.o] Error 1
    make[2]: Leaving directory /tmp/SBo/digikam-3.1.0/build’
    make[1]: *** [extra/libkgeomap/libkgeomap/CMakeFiles/kgeomap.dir/all] Error 2
    make[1]: Leaving directory /tmp/SBo/digikam-3.1.0/build’
    make: *** [all] Error 2

  22. btw, when trying to run digikam (before trying to rebuild it) it failed with this error:

    digikam: error while loading shared libraries: libgphoto2_port.so.0: cannot open shared object file: No such file or directory

  23. “cwizardone – this systemsettings applet is not new, it is part of working with polkit and has been part of KDE’s systemsettings since Slackware 14.
    But I fail to see how this is “mickeysoft-windows-ish” ? System policies are not the exclusive domain of Microsoft.

    Well, it appears that “they,” the people at KDE, are deciding for me just what organizations or software can access my computer and I don’t see an option for blocking it, unless turning it off is available to root. At the moment I’m looking at it as user.

  24. @cwizardone : you are missing libgphoto2 from -Current and your digiKam source is still at 3.1.0 which is outdated compared to KDE libraries which are now at 4.11. Can you try use 3.2.0?
    They are now at 3.3.0-beta3 and it should sync with KDE 4.11.

  25. @Willy Sudiarto Raharjo: Thanks for taking the time to reply. Greatly appreciated.
    I’ve checked and doubled checked and the latest version of libgphoto2 is installed and has been since it was first posted to -currernt back in mid June.
    Tried to build digikam 3.2.0, and it failed at,
    CMakeFiles/kipicmd.dir/kipiinterface.cpp.o:(.rodata._ZTV13KipiInterface[_ZTV13KipiInterface]+0x128): undefined reference to KIPI::Interface::editingFinished(KUrl const&, QFlags)’
    collect2: error: ld returned 1 exit status
    make[2]: *** [extra/kipi-plugins/tests/kipicmd] Error 1
    make[2]: Leaving directory /tmp/SBo/digikam-3.2.0/build’
    make[1]: *** [extra/kipi-plugins/tests/CMakeFiles/kipicmd.dir/all] Error 2
    make[1]: Leaving directory /tmp/SBo/digikam-3.2.0/build’
    make: *** [all] Error 2

    I then tried to build digikam 3.3.-beta3, and it failed at the exact same spot.

  26. My Battery Monitor widget lost “Sleep” button… can anyone else confirm this?
    I’ve tried to use Sleep button from KDE menu, but it seems to do nothing else other than show a black screen…
    If I execute the command “dbus-send –system –print-reply –dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend”, suspend works fine.

  27. Hi, to questions:
    If i’ve 4.10.5 from your package can i upgrade via slapt-get?
    or there is new packages in rc1?
    I’ve not found kipi-plugins: where is a updated package?

  28. @cwizardone : do you have kipi-plugins from the old version (2.9.0) ?
    Since digikam-3.0, they provide an internal kipi-plugins. I haven’t tested 3.3.0-beta3 yet, but i have 3.2.0 running fine on my system with KDE 4.10.5. Not yet tested on KDE 4.11, since i couldn’t have a stable performance on KDE 4.11 yet. I tried to use a clean Slackware-Current on VM and it had the same problems i had on my main desktop. KWin and Plasma Shell keep crashing, so i can’t do anything, but to revert it to a snapshot i i created earlier just before upgrading to KDE 4.11.

    Digikam usually released a new version along with KDE release. I think digikam 3.3.0 will be released after KDE 4.11 final gets released.

  29. @ Willy Sudiarto Raharjo,
    I removed 4.11rc1 (4.10.95) and re-installed 4.10.5, and Gwenview, digiKam and the kipi-plugins are now working as they should. At the moment digiKam 3.2 is building in another window and it looks like it will be successful this time.
    Thanks for all your advice. Greatly appreciated! 🙂

  30. @Mike: No, not yet unfortunately
    Do you use NVidia GPU as well and suffer the same problem as mine? KWin/Plasma keep crashing?

  31. Hi Willy

    I have upgraded my desktop to KDE 4.11RC1 today. This is 64-bit Slackware-current.
    This computer has a GeForce GT 240 card inside, and I upgraded to NVIDIA driver version 319.32 together with the new KDE.
    One of the first things I did after logging in, was switching the Compositing Type to “OpenGL 3.1” with Qt Graphics System set to “Native”.
    I have not had a single crash yet, and played with various applications including dolphin – thumbnail view is lightning fast, semantic search, VLC playing a few movie fragments windowed as well as full-screen. I am keeping KDE 4.11 RC1 on here.


  32. @Eric:
    Unfortunately i can’t change the setting at all since KWin crashed first. How do you change that configuration on CLI?

    I used an older GPU so i’m forced to use 304.88 driver.

  33. Thank you Eric!

    The install went all well and everything seems to work OK. Well, *almost* everything. Looks like there is a showstopper bug in akonadi:


    I understand that the KDEPIM folks do not recommend using 4.10.95 if you use maildir for your mails (as I have).

    Right now I’m hitting loads of 14.10 and the like with my 2 cores at 100%, memory maxed out and thrashing… load even reached 17. Thanks heavens that Slackware still is responsive so I can type this.

  34. @Eric:
    RC2 packages is now available. Hopefully most of the bugs has been fixed on this stage 🙂

  35. Hi Eric, I am trying to compile RC2 with your SlackBuild but compilation fails on kdebase:nepomuk-core with the following messages:

    [ 83%] Building CXX object services/fileindexer/indexer/CMakeFiles/nepomukffmpegextractor.dir/ffmpegextractor.cpp.o
    /tmp/kde-build/kdebase/nepomuk-core-4.10.97/services/fileindexer/indexer/ffmpegextractor.cpp:37:28: fatal error: libavutil/dict.h: No such file or directory
    compilation terminated.
    make[2]: *** [services/fileindexer/indexer/CMakeFiles/nepomukffmpegextractor.dir/ffmpegextractor.cpp.o] Error 1
    make[1]: *** [services/fileindexer/indexer/CMakeFiles/nepomukffmpegextractor.dir/all] Error 2
    make: *** [all] Error 2
    kdebase:nepomuk-core failed to build.

    Do you have any pointers?? Thanks in advance.

  36. Which ffmpeg version you used?
    I used Eric’s restricted ffmpeg and i got it here on

  37. Willy: I thought of that also and I solved the problem. I was using an old 0.6 version from SBo. Upgrading to Eric’s latest restricted version did the trick. After that, it was smooth sailing. Thanks for the tip.

  38. I finally got around to installing this and I have no issues to report. Everything seems fine after pulling in the Aug 6 updates and now using NVIDIA blob 325.15.

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.