KDE 4.5.1 – I took the plunge

Yes! KDE 4.5.1 Packages are now available for slackware-current (32-bit and 64-bit).

Read installation/upgrade instructions in the provided README file.

In my previous post I wrote that I was not sure who would be building new packages for KDE, but then I decided that this would be a nice test of my new build box with virtual machines. Indeed my total build time for KDE has been reduced to almost a third of the time that was needed before!

My new KDE 4.5.1 packages are only meant for  Slackware-current. They are not guaranteed to work on Slackware 13.1, so if you want KDE 4.5.1 you are encouraged to upgrade to Slackware-current!

There is one additional dependency to be installed on slackware-current: libdbusmenu-qt (which does not yet exist in Slackware).  You’ll find it in the “deps” directory.

Let me repeat this note from when 4.5.0 was released:


The kdepim and kdepim-runtime packages are not part of KDE 4.5.1 !!
The PIM developers decided that their applications are not yet stable enough to get included, and instead you are encouraged to keep the kdepim and kdepim-runtime packages of slackware-current (version 4.4.5).
There is one caveat: the consequence is that you will only be able to use the english localization of kdepim, because the language files are contained in the kde-l10n-* packages of the old version. You can not install that in parallel with the 4.5.1 version of your language files.

Enjoy, Eric

16 thoughts on “KDE 4.5.1 – I took the plunge

  1. Pingback: KDE 4.5.1 packages

  2. By the way, rsync sources for these packages are:
    Master: rsync://alien.slackbook.org/alien-kde/

    US mirror: rsync://taper.alienbase.nl/mirrors/alien-kde/
    Asia mirror: rsync://repo.ukdw.ac.id/alien-kde/


  3. Pingback: Tweets that mention Alien Pastures » KDE 4.5.1 – I took the plunge -- Topsy.com

  4. I can confirm some nvidia issues, but a driver update and rebuild took care of everything. I’m loving the new desktop, just looks nice and clean while handling all the stuff xfce didn’t (I love that desktop… but manually setting all my hardware buttons was a pain)

  5. @Dorf:

    Users who know what to do after an upgrade and do not have to reboot are welcome of course (usually you do not have to, but that advice was a left-over from way back when I also had to update dbus and polkit files). The “reboot” suggestion is just to make it easy for the inexperienced ones.


  6. Thanks for clarifying. I understand that writing READMEs is boring and you rather spend less time on them. But since you say inexperienced users, I’d like to remark that it’s these little READMEs that contained the most useful insights for me when I was inexperienced.
    In this specific case, I even think that restarting X by pressing Ctrl-Alt-Backspace is far esier than rebooting.

  7. A weird issue with both your builds and those from official -current:

    Lacelot menu, 4.5.1 on slackware 32: fully localized in italian

    Lancelot menu, 4.5.1 on slackware 64: half italian, half english

    It’s weird because the kde-i10n-it package is the same. Or it isn’t? uhm.. I have to try installing the package from the 32bit build..

  8. Pingback: Alien Pastures » Compositing hard lock in KDE 4.5

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.