As you may already know, there is a problem with KDE 3.5.4 (in Slack-current, ie. Slackware 11RC2) - it doesn't more allow to use kio-slaves without HAL, although it did worked flawlessly with plain /etc/fstab in previous releases.

After a brief correspondence with Patrick I started to experiment with D-Bus/HAL implementation in Slackware-current.

First PITA was the discovery current hal release 0.5.7.1 does not compile against current dbus release 0.92 because changes in function definition So I've picked up dbus rel. 0.62 and hal could be finally built.

Second PITA is a "skin game" with extra groups & users adding into the system to which dbus and hal daemons drop their running privileges and manual creation of status directories in /var/run subtree for pid and socket files and /media directory for mounting - install target of Makefiles somehow "forget" to create them. I've been heavily inspired by Freerock GNOME packages and Portpkg SlackBuild script to solve mentioned problems.

Third PITA was the need to rebuild kdebase package with hal support but it was very simple by using Pat's script. It only took around 4 hours of compile time including massive use of ccache.

Fourth and not yet resolved PITA after everything seemed to be finally working is the inability to unmount device previously mounted by the same user.
kio_media_mounthelper displays error message "Volume mounted by uid UNKNOWN cannot be unmounted by uid 1000."
Uid 1000 is my uid of my user account, mount options seem to be proper
so I really don't know what else this load of s*t demands Any idea ?

What the hell I have to mess with such annoyances if everything did worked with full satisfaction before ? Why KDE team has decided to don't give more an option whether an user wish to use such automagical "things" ? Forthcomming KDE 4 will probably completely replace DCOP with this dbus/hal beast.
One of the main reasons why I've leaved Windows world and what I *really* hated latently infiltrates Linux world in the last years - users/admins are more and more forced to lose control over their systems.

I don't know how to fix the problems with HAL/D-Bus, but I much rather prefer to not have HAL as a KDE dependency, so I gave 20 votes to the bug report at https://bugs.kde.org/show_bug.cgi?id=132281

This *is* a bug, because in the KDE 3.5.4 requirements page, HAL/D-Bus is only optional and it states that without it, kioslaves will be using fstab only.

Thank you for participating in voting for my bug report. Hope developers recognize it as a bug - not a feature - and will fix it soon.

Hi. Just gave my 20's too, and right after this message appeared It's my first time using KDE's bug report system so what does that mean and why does it shoes it's from me ? Anyway, hope my votes help.

Nykey, great thanks to you too.