My thoughts on Slackware, life and everything

Long Term Support (LTS) for KDE 4

qt-kde-620x350 Some folks asked whether the new KDE4-based packages in my KDE5 repository would also apply to KDE 4.14.3. The answer: no they probably won’t, so you better not try what happens.

The updated sources that appeared with regular intervals were all part of KDE Applications, and for the past months I only focused on using those for my KDE5 repository. I did not want to forget users of KDE4 however.

Therefore I refreshed my KDE 4.14.3 repository today (packages for Slackware-current, not for 14.1) with the latest Long Term Support (LTS) sources that I took from KDE Applications 14.12.3.

KDE 4.14.3 was the last release of KDE4. It came with a promise that the developers would provide Long Term Support for this particular release.  Which is why I finally took the new sources for kdelibs, kde-workspace, kdepimlibs, kdepim and kdepim-runtime and built these on top of Slackware 4.14.3. These updated packages are available for you as per direct. As a bonus, they are accompanied by the latest Calligra office suite. There are also a couple of changes in the “deps” directory for KDE 4.14.3. You will find two all-new packages: librevenge and libodfgen, and two updates for stock Slackware packages: grantlee and libwpd. The kdepim package needed a newer grantlee, and the other three are required by the new calligra package.

Users of slackpkg+ have it easy:

# slackpkg update
# slackpkg upgrade-all
# slackpkg install deps

The moment KDE 4.14.3 gets officially added to Slackware-current, I will rebuild all of KDE 4.14.3 for Slackware 14.1 so that people with a taste for stability will have something new to chew on too.

Something funny: when I sat down to write this article, I went searching for my initial announcement on the blog of KDE 4.14.3 packages (released on 11 Nov 2014.). To my amazement, there is no such article! It seems I forgot to write a blog post about KDE 4.14.3 back in November… probably had too much to do at the time, but I can not remember. Apologies for that… I hope you have noticed that there were new packages nevertheless 😉

Have fun! Eric


  1. william

    thank you a lot alien however your work is very userful

  2. cwizardone

    Thank you! Greatly appreciated!

  3. Michael

    Great. Thanks a lot 🙂

  4. Amit Ugol

    built these on top of Slackware 4.14.3 ?

  5. fabio

    that was fast. Thanks! vlc plays fine, but amarok won’t work with any of the backends. Anyone else got the same problem?

  6. alienbob

    Amit Ugol, yes I built them on top of KDE 4.14.3 on Slackware-current.

    What else did you expect when I wrote “I refreshed my KDE 4.14.3 repository today (packages for Slackware-current, not for 14.1) with the latest Long Term Support (LTS) sources that I took from KDE Applications 14.12.3” ?

  7. alienbob

    fabio, perhaps Amarok needs to be recompiled. Give that a spin and tell me about your findings.

  8. cwizardone

    Everytime I reboot the computer and start KDE (startx) KDE says it can’t find the audio card and asked if it should forget all the drivers, which includes the card built into the motherboard and the hdmi card built into the video card. I say, yes, and it starts to use the correct card, that is, the one built into the motherboard. I’ve tried using a /etc/asound.conf file to make sure the system sees the correct card, but that didn’t help, so I deleted the asound.conf and tried a /etc/modprobe.d/alsa-base.conf file, but problem remains.
    Any ideas?

  9. alienbob

    What happens if you rename/remove ~/.kde/share/config/phonondevicesrc cwizardone?

  10. cwizardone

    Well, the first time I got a blank, black screen and a locked up computer, so I hit the reset button, and the second time KDE started properly. We will see what happens tomorrow.
    Thanks for the suggestion!

  11. cwizardone

    Nope. Back to square one on boot up this morning. It is this kind of nonsense that makes me start checking the prices on a copy of win7. 🙁

  12. fabio

    ok. my findings after recompiling amarok. found this thread that seems to explain what happened:
    On FreeBSD the solution was to remove phonon-backend-gstreamer and rebuild kde-runtime with “vlc” option enabled. I can confirm that arch linux is not affected (they always use the latest version of everything). if you can look at the thread when you have the time. I was not smart enough to think of a “slackware solution”. Many thanks.

  13. alienbob

    Hi fabio

    A vlc based solution is not possible for Slackware – vlc will not be included.
    So, perhaps you should stop using amarok and switch to vlc itself?

  14. fabio

    yes. done it already. On Stable switched to Clementine (the slackbuild available at won’t build on -current). On current i’m using vlc itself. Thanks.

  15. Thiago Silvino

    Spoiler request: hey Eric, have you heard if KDE 4.14.3 will officially be included into -current?

    Again tks for all your effort in keeping these excellent KDE builds!

  16. alienbob

    Hi Thiago

    KDE 4.14.3 will be added to Slackware-current including the LTS packages.
    Just a *little* bit of patience is needed…

  17. Daniel

    Why do I have no sound at all with phonon-gstreamer after update on 4.14.3? qt is 4.8.6 (from slackware-current)

  18. alienbob

    Daniel, no idea. If there are more people with no audio and using phonon-gstreamer backend as opposed to the vlc backend, I would like to know.
    People using the xine or mplayer backend – can you try switching to the gstreamer backend? The mplayer and xine backends will be removed from Slackware-current once KDE 4.14.3 gets added there.

  19. fabio

    Upon logging in, visit “System Settings-Multimedia->Device Preference”. Choose the first device in the right pane and then press “Test”.Is there sound or does the “Test” button remain pressed. This is what happens. And here’s what i’ve found on a forum:
    “When the Phonon developers advanced from version 4.7.2 to 4.8.0 of the GStreamer backend, they changed from the older gstreamer-0.10 to the newer 1.0 version. At or near that timeframe, they also opted to prefer VLC over GStreamer. The change from linking against
    gstreamer-0.10 to gstreamer-1.0 results in no audio”

    That’s it. Sorry if it’s lengthy.

  20. jati

    Hi Eric, i’ve a problem to install ffmpeg in my Slackware (after upgrade to slackware64-current 20150421), your libssh kde 4.14.3 deps was not detected by ffmpeg (i’m sure that i’ve installed it), but, when i tried to use the libssh from slackware repository, i could compile and install ffmpeg without any error.

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 ↑