My thoughts on Slackware, life and everything

KDE 4.8.3 packages

The KDE team officially released the sources for KDE Software Compilation 4.8.3 today. I grabbed the tarballs from the packagers site a few days earlier, so that I could again have a full set of Slackware packages for you.

The upgrade will be trivial. Slackware-current was enhanced very recently with KDE 4.8.2 and all the software updates which that move required. Apart from the 4.8.3 release sources, I only had to compile a newer version of libbluedevil and bluedevil, and even those two will be updated in Slackware too, very soon (perhaps Pat already pulled the trigger).

Get my packages here; the official Slackware packages will remain at version 4.8.2, while Pat and the team concentrate on other parts of the distro.

The accompanying README file contains detailed installation/upgrade instructions. Do not fail to follow those instructions!

Have fun! Eric


  1. kkady32

    thanks,work perfectly!

  2. escaflown

    Thanks Eric!

  3. Schmatzler

    Man, your KDE packages are always available before the big news sites post about new versions! Do you own a time machine? 😉

    Thanks for the new packages 🙂

  4. Alberto

    Thanks Eric!
    I’d like to compile them for Slackware 13.37.
    I notice there’s no “deps” folder. Where I can find them?

  5. alienbob

    Hi Alberto

    I had taken the libbluedevil and bluedevil packages (and their sources) out before uploading the rest, assuming that Patrick would have already added them to slackware-current before I made my KDE 4.8.3 packages public. But the amount of updates in -current is going to be a bit bigger so there was a slight delay.
    The sources below 4.8.3/source/ are enough to build KDE 4.8.3 for Slackware 13.37, provided you still have all the sources for the deps I had available together with my KDE 4.8.1/4.8.2 packages.


  6. Eduardo

    Hi Eric, thanks for these packages. They are great and work without problems so far on my system.

    A problem that I’m having now is that, since Slack-current’s latest updates on wicd, the client starts again on each boot. You had instructions on how to disable the wicd client on your readme for KDE 4.7.2, IIRC, but it is long gone now. Can you post these instructions again, please? Thank you!

  7. Willy Sudiarto Raharjo

    chmod -x /etc/rc.d/rc.wicd
    Quit the wicd-client on your system tray

    that should fixed it

  8. alienbob

    Hi Eduardo

    Check my comment below – search for “NotShowIn”.


  9. Alberto

    Sorry for the previous incomplete message, it was wrongly sent.
    Anyway, thanks for the reply!
    That is the point indeed: I don’t have installed those dependecies on my system and I couldn’t find them in your repository anymore.

  10. alienbob

    Hi Alberto

    Indeed I removed the old “deps” sources because I do not need them anymore in order to build a newer KDE on slackware-current.
    However, for Slackware 13.37 you can use this provision which Pat made in the source tree of slackware-current:

    That contains the deps you are looking for (not including virtuoso-ose which you will have to grab from slackware-current separately).


  11. Gabriel Yong

    Whenever i run slackpkg upgrade-all, the old version of kde4.8.2 still appear on the list selection while at lower bottom screen shown currently installed version is 4.8.3. I need to deselect it every time i run slackpkg upgrade-all. How can i avoid this?

  12. Eduardo

    @Wily: Thanks! I already had taken care of that

    @Eric: Thanks! That was exactly what I was looking for 🙂

  13. alienbob

    @Gabriel Yong

    It looks like your slackpkg has not blacklisted my packages. And that means, slackpkg will try to install Slackware’s own version of KDE. Remember that packages in Slackware can be “upgraded” to a lower version.

    If you want to blacklist my packages, then you have to add the following line to the file “/etc/slackpkg/blacklist”:



  14. slacker_mike

    Great job as always! Thanks!

  15. fgcl2k

    Hi Eric,

    just a small note: KDE.SlackBuild tries to build the module extragear:libktorrent, which is not present in src/extragear.

  16. Armin Besirovic

    After upgrading, all GTK+ apps were almost completely black. What fixed this was:

    cp /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc ~/.gtkrc-2.0

  17. sberthelot

    On this version KTimeTracker does not start for me, does anyone else have the same problem ?
    I’ll try maybe to revert to 4.8.2-slackcurrent to see what it does

  18. alienbob


    This seems to be a problem many distros struggle with. It will work if you first start Kontact and then start KTimeTracker from within Kontact (it’s on the lower left).
    The suggestions in the various bug trackers did not help me find out how to fix it for Slackware – several other distros give the same advise a I gave above.


  19. zrdc28

    Since the upgrade to latest -current my ati radeon hd2400pro will not work, I have to use the proprietary driver which is much slower. Is there any type of work around for this?

  20. jsilcock

    I am _really_ missing that deps folder not included with 4.8.3. I am only a casual user, neither a computer scientist nor a system programmer. Creating the deps folder from thin air is beyond my limited abilities.

    Thank You Very Much for the _vast_ amount of free work you do for us, Eric. l8rs

  21. Gabriel Yong

    That’s great work! Thankx Eric!
    At the moment it still heavy for my laptop to run it,Intel(R) Pentium(R) M Processor 1.7GHz with memory of 512MB to run smoothly. i have to disable all the desktop effects for it to load and run. Anyway that’s was cool.

  22. Willy Sudiarto Raharjo

    all the deps are now included in Slackware-Current, so if you haven’t upgrade to -Current yet, then you should read the README for this KDE packages 🙂

  23. Aaron

    hi, thanks for the contributions that we provide and excuse my bad English. I’m new USER in slackware and have had some problems I have solved thanks to your posts.
    I wish I could focus on how to add your packages blacklisted and I do not understand that part.

  24. alienbob

    Hi Aaron

    Open the file “/etc/slackpkg/blacklist” in an editor and add the following line at the end:


    That will blacklist every package of mine that you have installed.


  25. Aaron

    Thanks for your reply Eric helped me a lot but I have a problem when starting kde with startx I get the following error:
    server terminated with error (1) and I could not have been able to solve averguar the source of the problem.
    oajala I can not get help with my problem:
    The characteristics of my team are:
    amd A4
    Video Card: Radeon 1GB HD6650M
    4 GB ram

  26. Aaron

    excuse my bad English

  27. alienbob

    I am sorry, the information you provide is not enough to give any advice about how to solve your issue. Try looking inside the X.Org log (for instance /var/log/Xorg.0.log).


  28. Aaron

    Hi Eric and I could solve my problem, which was not properly downloaded the updates and finally I could start kde. But I have a question from what I read in the update to the current. to notice a change in the update because apparently eliminated comptabilidad with the radeonhd driver and of course I can not install my video driver will there be any driver currently compatible with current radeonhd?

  29. alienbob

    Hi Aaron

    Slackware-current no longer has the radeonhd driver. Did you install my KDE 4.8.x on top of Slackware 13.37 or are you running a version of Slackware-current which is already a bit old? I create my KDE packages for the most up-to-date version of Slackware-current.
    If you are currently using the radeonhd driver then Slackware’s new X.Org should still support your computer, just not using radeonhd.


  30. Aaron

    I just upgraded to current I wondered if there is a driver available even my video card

  31. alienbob


    Certainly, why not? Just make sure that you remove /etc/X11/xorg.conf if that exists and let X.Org figure out what it needs.
    Before starting X, you can run “lspci -v” as root to see what drivers the Linux kernel knows and loads for your card.


  32. Aaron

    by typing lspci-v I get the following:

    01:00.0 VGA compatible controller: ATI Technologies Inc NI Whistler [AMD Radeon HD 6600M Series] (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. Device 107c
    Flags: bus master, fast devsel, latency 0, IRQ 47
    Memory at c0000000 (64-bit, prefetchable) [size=256M]
    Memory at fea20000 (64-bit, non-prefetchable) [size=128K]
    I/O ports at e000 [size=256]
    Expansion ROM at fea00000 [disabled] [size=128K]
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
    Capabilities: [150] Advanced Error Reporting
    Kernel driver in use: radeon
    Kernel modules: radeon

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 ↑