Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



KDE 4.8.4 (last in the 4.8 series)

With a few days’ delay due to patches which were contributed at the last moment and resulting build failures (…), the KDE team announced the final increment in the 4.8 series: KDE Software Compilation 4.8.4 . I have packages for you and am announcing those for all users of Slackware-current.

The upgrade is trivial if you are already running Slackware-current. It already contains KDE 4.8.2, so the upgrade to 4.8.4 will mostly give you bug fixes and some performance enhancements. There was some talk about adding an unplanned 4.8.5 release because it will take so long until 4.9 stable but it seems that the reasons for wanting this have been addressed in the form of those patches to the 4.8.4 source tarballs which I mentioned above.

Re-compiling the 4.8.4 sources for Slackware 13.37 will not be so trivial, since you have to update quite a lot of other packages in Slackware (and install some new ones). Check out this directory with symbolic links in the slackware-current source tree. It points to all the package sources which you need if you are going to create packages for 13.37: . If there is enough demand, I will consider adding a “13.37 deps” directory for KDE 4.8.4 to the reposititory.

Get my KDE 4.8.4 packages for -current here:

The accompanying README file contains detailed installation/upgrade instructions.

Remember: if you rather want to try out a beta of the future 4.9 series, then I have that available too! See . I am running that Beta on my desktop and I have not found a single bug yet.

Have fun! Eric


Comment from Willy Sudiarto Raharjo
Posted: June 8, 2012 at 09:03

Same here. Didn’t found any problem using the first beta of KDE 4.9.

Comment from Gabriel Yong
Posted: June 8, 2012 at 12:15

i would like to have it in my 13.37, thank you!

Comment from Etienne
Posted: June 8, 2012 at 15:50

Thanks for the packages Eric 😉

KDE works well but gwenview crash when Nepomuk is enabled…

Comment from gmg
Posted: June 8, 2012 at 16:22

Thanks Eric,

but, I have also this bug:

Comment from cendryon
Posted: June 8, 2012 at 19:57


Thanks Eric

Same as Etienne here.
Morever, clicking on a picture in Dolphin crashes Dolphin, even with Nepomuk disabled 🙁


Comment from amigib
Posted: June 8, 2012 at 21:17

Nothing crashes here, maybe deleting old KDE configuration in your home directory will help?

Comment from amigib
Posted: June 8, 2012 at 21:23

oh, btw, i was talking about KDE 4.9

Comment from alienbob
Posted: June 8, 2012 at 22:08

I am running KDE 4.8.4 on this laptop I am typing on right now. And indeed, gwenview crashes whenever I start it. And clicking a picture in dolphin (which launches gwenview) did not just crash gwenview, it took the whole desktop with it so that I had to Ctrl-Alt-Backspace to the console.
The backtrace contained enough useful info that KDE’s crashhandler let me open a bug report for it:


Comment from alienbob
Posted: June 9, 2012 at 12:03

This is what made gwenview at least start and open pictures:

rm -r /tmp/akonadi-${USER}.*
rm -r /tmp/kde-${USER}
rm -r /tmp/ksocket-${USER}
rm -r /var/tmp/kdecache-${USER}
rm -r ${HOME}/.kde/share/apps/gwenview

However, when I click a picture in dolphin, then gwenview will be launched to display the picture, which still freezes it… and twice my complete desktop froze with it.

Some Ubuntu noob closed my bug report stating that it was a duplicate of a Kubuntu bug they had in their KDE 4.7.2… but I re-opened it and it seems to be taken more seriously now that two other distros added their comment that they experience the same crash.

The packagers mailinglist is currently the stage of a discussion of a percieved regression in KDE 4.8.4. Compared to the previous releases, it seems less stable.


Comment from Willy Sudiarto Raharjo
Posted: June 10, 2012 at 09:08


can you try to upgrade soprano to 2.7.57 and see if it fixed the gwenview problem?
It’s not really a stable release for soprano, but if it worked, then it might be better to use this one

I read the comment in the bug report here

Comment from Willy Sudiarto Raharjo
Posted: June 10, 2012 at 09:11

Soprano 2.7.57 is used in 4.8.80, so probably that’s why 4.8.80 is not affected by this bug.

But i guess it brings some problems on the new beta 2 packages

Comment from alienbob
Posted: June 10, 2012 at 11:13

Hi Willy

Spot on! Upgrading soprano fixed the gwenview crash bug. I updated my own bug report with this news.
However, a dependency on an unstable soprano should not have been forced upon KDE 4.8.4 so I guess someone messed up.


Comment from Willy Sudiarto Raharjo
Posted: June 10, 2012 at 12:10

You can use one of these two patches to patch the current soprano if you don’t want to use the unstable soprano

Comment from Willy Sudiarto Raharjo
Posted: June 10, 2012 at 12:13

ahh… that was a patch for soprano in order for KDE 4.9 Beta 2 to build. Sorry…

It’s an upstream bug report

Comment from Janis
Posted: June 11, 2012 at 20:56

To my great disappointment, kde is getting less and less stable. I am suprised that none seems to have problems with it. For example – Alt-F4 stopped working in KDE 4.8.4 and i have no idea how to solve it. The other problem i have on kde 4.8.4 is non-working C&C (under wine, there is no keyboard commands anymore). I am sure that the problem lies with kde – under XFCE everything is OK. I have suspicions it has to do something with currently non-removable component “activities”.
P.S. Eric, it would be very nice if you could leave at least build scripts for older kde versions in repository)

Comment from alienbob
Posted: June 11, 2012 at 22:07


If you want old build scripts then you better start collecting what’s here. I am not going to keep a public archive.
THe fact that things stopped working for you does not automatically mean that KDE is getting worse. The cause could be in your computer. As you state, “I am suprised that none seems to have problems with it”… I am not surprised. Nobody is reporting these problems.

You could try and create a new user account and use that to logon to KDE. If that session behaves better then there is old stuff in your dot directories which is incompatible with newer versions of the software.


Comment from Janis
Posted: June 11, 2012 at 22:32

actually, it (kde) begun misbehave from the first moment after slack-cur reinstallation. I managed somehow to keep things running using hibernation, but this evening was the last. I plan to revert to the 4.6.5 on mu desktop and stay there until Pat will make a new and shiny stable release of Slack.
To my surprise, there is no such problems on my laptop, while the software and configurations are almost identical.

Comment from Helios
Posted: June 12, 2012 at 08:23

I have installed version 4.9-beta1 and everything is working well. And something stops me to go back to 4.8.3 or 4.8.4 : it seems that 4.9-beta1 runs faster.

Comment from Janis
Posted: June 12, 2012 at 09:23

to add a comment o my previous comment – my laptop is a lot bigger trashbox as it is just upgraded all the way form 13.1, not re-installed as the disfunctional one.

Pingback from Problems with ktimetracker and KDE 4.8.2
Posted: June 18, 2012 at 14:19

[…] KDE 4.8.4 is already available on AlienBOB's KTown repository. See his blog post […]

Comment from LoneStar
Posted: June 22, 2012 at 18:16

I am using 4.8.4 on -current x86_64

I notice krunner (alt-f2) is crashing as soon as I start typing anything to search for something to be launched.

does it happen to anyone else?

could this be the case?

Comment from Etienne
Posted: June 23, 2012 at 12:28

Hi LoneStar !

No problem here but I’m using -current in 32 bits.

Comment from crond
Posted: June 24, 2012 at 16:13

I cant able to download README .

Comment from alienbob
Posted: June 24, 2012 at 17:31

Hi crond

I fixed the link for the README, please try again.


Comment from crond
Posted: June 25, 2012 at 05:06

Hi Eric,
thanks, I can see the README file now

Comment from crond
Posted: June 25, 2012 at 21:57

hi eric,
just now I used slackpkg to update the entire system from stable 13.37 to do KDE4.9 testing.
As of now KDE is 4.8.4
I am facing a issue with that.
In the panel I have
1. kick off application launcher
which is not showing a pop-up menu when I click that. It was ok with Slackware 13.37′s KDE version.
Now, I added
2. Application Launcher, which is working fine.

Comment from alienbob
Posted: June 25, 2012 at 22:08


Did you run “slackpkg install-new” in order to install the packages which were added to Slackware after 13.37 was released?
I suggest you fix your KDE 4.8.4 issues before you attempt to upgrade to my KDE 4.9-beta2 packages.


Comment from crond
Posted: June 26, 2012 at 17:11

yes , sure I did “slackpkg install-new”.

And I can’t take a widget and place it where-ever I want in the panel. there is no such an option in the panel

Comment from crond
Posted: June 26, 2012 at 17:50

I noticed one more issue. All my wallpapers [ different for each workspace, totally 4 work space ] are get swapping among the work-spaces for each time I reboot or startX.
And this is also not the case with 13.37’s KDE.

Comment from alienbob
Posted: June 26, 2012 at 19:37

Moving widgets on the panel is only possible when you have unlocked the widgets. just grab a widget in the panel and move it left or right. When you stop moving, wait until the panel creates an empty space and drop the widget there.

About your wallpaper issue – no iea.


Comment from crond
Posted: June 28, 2012 at 05:16

Is it OK , if I proceed to KDE 4.9 rc1.
So, far I am not done with the issues
1. kick off app manager
2. changing wallpapers
You already advised , not to do that.
Meanwhile I dont know to solve that either. :'(

Comment from crond
Posted: June 28, 2012 at 05:17

just FYI, the issues mentioned above are with KDE4.8.4

Comment from crond
Posted: June 29, 2012 at 17:32

Hi, now both the application launchers are started to work. I did NOTHING.
But, now for every click, I am getting some very strange behavior. I just linked the video to you.
Please spare a minute to help me out there.
I am very eager to test KDE beta packages . And in Slackware …

Comment from alienbob
Posted: June 29, 2012 at 18:37

If you are testing KDE 4.9 beta / rc packages please post your findings in comments section of the proper article:

If you are using KDE 4.8.4 then that is now part of Slackware itself, and commenting on it does not belong in this thread anymore. A community site like would be better suited.


Write a comment