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



Some package updates for KDE 4.6.5

My KDE 4.6.5 post from a few weeks back had a few comments about a non-working kcalc. Also, the KDE release team updated all the language tarballs for KDE 4.6.5 – after first renewing the broken ‘nl’ sources apparently the other language sources had issues too.

So, I rebuilt all the KDEI packages (the language packs) using the new sources. And I rebuilt the kdeutils package using several patches for kcalc.

Go get them. If you had the aforementioned issues they might be solved by these updated packages.

For instance at or .



Comment from gbschenkel
Posted: July 27, 2011 at 01:31

Hey Eric, do you know if your packages have some issue with xsane? maybe polkit packages, i don’t know, i can’t get permission to use scanner as user, only as root. The device don’t detect using a user account. Cheers and thank for the kde packages !

Comment from Hans
Posted: July 27, 2011 at 09:09

After installing the packages my KDE no longer responds to me closing the lid and when I plug in a USB stick, it fails to mount it (looks similar to previous poster). What did I forget to do?

Comment from firekage
Posted: July 27, 2011 at 11:19

I can’t download packages using rsync. I paste command from readme and than i get:

@ERROR: Unknown module ‘alien-kde’
rsync error: error starting client-server protocol (code 5) at main.c(1516) [Receiver=3.0.8]

What’s wrong?

Comment from dolphin77
Posted: July 27, 2011 at 11:25

correct the path to your local folder structure. This should work:

rsync -avr –delete rsync:// /home/Soft/alien/ktown/4.6.5/

Comment from alienbob
Posted: July 27, 2011 at 11:53

@dolphin77,firekage, this is about the rsync URI “rsync://” no longer working.

Robby Workman created a new rsync module for me on “rsync://”

You can now access my ktown stuff through rsync:// and multilib files through rsync://

Unfortunately he also deleted the original “rsync://” module… which was not supposed to happen. I have asked him to restore that rsync module.


Comment from firekage
Posted: July 27, 2011 at 12:58

Thanks, now it works.

Comment from witchlord
Posted: July 27, 2011 at 16:56

Эрик- молодчина! Спасибо за труды!!! 🙂

Comment from witchlord
Posted: July 27, 2011 at 16:57

Эрик- молодчина! Спасибо за труды!!! Слакварь рулит!!! 🙂

Comment from pralat
Posted: July 27, 2011 at 20:52

Thanks, man!
And now, i’m waiting for kde 4.7 packages ;]

Comment from Hans
Posted: July 28, 2011 at 16:24

What I forgot, maybe this helps somebody:
1 – in runlevel 3, start the GUI using ‘init 4’, not ‘startx’
2 – enable AUDIT and AUDITSYSCALLS in the kernelconfig
Both are needed to get ConsoleKit to work properly.

Comment from escaflown
Posted: July 29, 2011 at 17:44

Hi Eric. Are you going to bless us with KDE SC 4.7 ? 🙂

Comment from fogie
Posted: November 17, 2011 at 08:40


I’m about to install 4.6.5 on my test box and I had one question. The readme mentions that hal is no longer required, does that mean that I must disable hal completely on the system? Thank you.

Comment from alienbob
Posted: November 17, 2011 at 12:49

Hi Fogie

HAL is no longer used by KDE, it is optional which means the new KDE will use it in addition to udisks/upower.

HAL does not _have_ to be disabled by you, but you can always try what happens if you do “chmod -x /etc/rc.d/rc.hald” and reboot.
Other subsystems (like Slackware’s XFCE and probably the other WM’s as well) still depend on HAL.

If you disable HAL by setting its rc script to non-executable, I would _not_ go as far as to remove the hal package completely.


Write a comment