Hello,

I am running Slackware 10.2 with KDE 3.5.4. Whenever I attempt to mount media from removable devices (CD-ROM, floppy, USB drives, etc.), I receive the following error message from within Konqueror:

Error - Konqueror: Feature only avaialble with HAL

I have installed both HAL and DBUS on my system, and both daemons are set to start up automatically when the computer normally boots. I have read a few posts on this very issue from others, but with no clear resolution to the problem. Any assistance is greatly appreciated. Thanks.

I've noticed this problem too and it looks like a new bug introduced by 3.5.4 version.
I can not comment behavior with hal installed but it should work without it as it did before this releas - entries in /etc/fstab are used for mounting.
I hope KDE developers fix this annoyance before Slackware 11 gets released.

Correct me if I'm wrong, but aren't DBUS and HAL designed for 2.6 kernels? Plus I think HAL is also for autodetecting and mounting media.

Indeed. HAL works with 2.6 kernels.

Anyway, automounting annoys me. Maybe I'm accustomed to manually mount/unmount my CDs. So I disable that %&%/&%/& automounting.

I get the error myself but I have never used that method for networking or drive management.

I either mount from shell or I right clicked on my desktop and create new -> link to device->appropriate device

creates a desktop icon then I edited the properties made sure settings were good ie proper rights and permissions. all I have to do is click on the icon and it mounts and opens. I can right click the device icon and select mount or unmount.

weird how that works yet using the menu through konqueror doesnt.

If you're using Pat's standard 3.5.4 packages (from Slackware-current) you'll need to re-compile the kdebase package, ensuring to use the "--enable-hal" switch at the configure stage.

Re-compiling kdebase took about an hour on my 3.4GHz P4.

Pat compiles KDE without HAL enabled, because HAL isn't part of Slackware.

Yep, it should work by this way, but it still needs to be fixed for systems without HAL, even if kdebase package explicitly allows to build _without_ hal support.

What's the preferred method to recompile a Slackware package? Is it a very intuitive process?

Refer to the SlackBuild scripts. I always use those if I ever have to recompile any standard Slackware stuff.

I'm not too familiar with the entire process, but the Slackbuild script for kdebase package would be insdie the package itself? After I have referred to the script, would I extract the contents of the tgz package and do a ./configure, make, and make install process? As you may be able to tell, I'm not too proficient in this area, so any help on this is greatly appreciated. Thanks.

It's all in the source tree under /source/kde/kdebase. You might have to download it. Try the same place you got the packages.

Hi

I compiled my own KDE and it took about a whole day. Not specifically activated HAL but even so I got that annoying automounting.

Not tested on 2.4 kernels because I don't use 2.4 anymore.

No problems so far.

Hi.
I've been reading and doing as other people have suggested.
I have gotten HAL and D-BUS installed and I have compiled kdebase from scratch with --with-hal. I have all the dependancies for Hal and DBUS. I have slackware 10.2 with a 2.6.17 kernel.
Yet no automount and I still get the "Feature Only Available With HAL" message.
I have tried building hal+dbus+kdebase from source using the latest and greatest (after some patching I got everything to compile. HAL and the new version of D-BUS don't talk all that well as of yesterday)
I have tried getting HAL and D-BUS from freerock (GNOME in Slackware) and then compile kdebase (only the koslave part) and istalling it, and it gives the same message every time I try to go to an unmounted device. "Feature only available with HAL".

The last thing I did was:
#slapt-get --update
#slapt-get --upgrade
got the packages for HAL and D-BUS from Freerock and installed them
using installpkg.
Then added my users to the halusers group
Then I checked the dependancies and they were all met.
#installpkg kdebase-3.5.4-blah..blah..tgz
then, using the sources for kdebase-3.4.5, I did:
#./configure --with-hal (I also tried --enable-hal just for the sake of argument)
#cd kioslave
#make
#make install
#startx

It didn't work. "Feature only available with HAL" is all I get.
Any ideas?... I installed Ubuntu at the office and there are minor annoyances with it, but it auto mounts devices without a problem. Little things like this make me wanna switch away from Slackware but I love other things about Slackware... it's a taugh choice.

Me too. I get this when using preexisting icons on the desktop or the media icons in Konq to mount hotpluggable devices. But they mount fine from bash using "mount /dev/sda1".

So it's just a bug right?

If I compile kdebase (which I doubt I'll do as I'm all out of kde voodoo at the mo', I had to reinstall the 3.5.4 packages 3 times before I could get the kfontinst part to work) then this should work better. If it mounts now, what's it supposed to do. Surely all the HAL bits must be right for it to mount and be useable?

Anyone know why HAL isn't part of Slack?

Same problem here with Slackware 11.0 RC3, as Pat likes to name it.

What I don't get: With Slackware 10.2 I was able to mount USB drives by clicking on them in the system tray on the KDE desktop. After upgrading to the release candidate it doesn't work anymore, due to "no HAL". How did it work before the upgrade, then?

And the question really is: Why isn't HAL a part of Slackware? It's part of Linux, supported by the kernel by standard and teams up usefully with udev. So I actually doubt that it is not part of Slackware, I'd rather suppose that it just has to be turned on. Somehow. Any ideas?

gargamel