I'm having a curious problem with HAL/DBUS and KDE on Slackware 12. I've read all of the major HAL threads here and don't think anyone else has run across this behavior.
The out of the box HAL/DBUS/KDE automounting works as it should. My non-root user is in the plugdev and cdrom groups, and with my cdrom line commented out in /etc/fstab, inserting a disk creates an icon on my desktop, and I can manipulate its mounting/application opening behavior with the KDE tools. All is good, except that it mounts the disk to /media/<volume name of disk> which I don't really like. For instances where I need to manipulate a disk at the command line (e.g. using installpkg from my Slackware DVD) I don't like having to go hunt the mount point under /media. I like a quick "cd /dvd" and I'm there.
So, I tried uncommenting my /etc/fstab entry, which from numerous posts made me think that should work with HAL and would make the mount point constant. I've tried two different lines (with one commented out, of course):
/dev/cdrom /dvd auto noauto,user 0 0
/dev/disk/by-path/pci-0000:00:1f.1-ide-0:1 /dvd auto noauto,user 0 0
The second was an attempt at using the udev-assigned name like Robby's /dev/cruzer1024 example in the HAL sticky. Robby mentions creating a custom udev rule, but the documentation I found here
implies that a custom rule is not necessary for devices under /dev/disk. I just used the persistent name already available under by-path.
In either case, when I insert a disk, KDE pops up a progress dialog for mounting the disk. It hangs, and my CPU goes to 100% in gkrellm, the CPU temp skyrockets to about 70C, and all the fans kick on full blast. The first time the CPU stayed there pegged out indefinitely, until I ran top and found that kded was the problem. I can kill the kded process to get the CPU to go back to idle, but I have to restart KDE to get kded back. Note that the disk *does* mount properly to /dvd, it's just the kded runaway that's the problem.
So, if anyone can help - is this udev related? Have I just got the fstab entry wrong, and should I go through making a custom udev rule? Or is this a KDE bug that's causing the problem?
Background: My hardware is an HP Compaq nx6110 laptop (Intel 915GM w/ Pentium M), running a custom 126.96.36.199 kernel. Yes, I also checked with generic-smp-188.8.131.52 to make sure my kernel wasn't the problem. I got the same results.
Sorry for the long post. I wanted to document this problem in case anyone else runs across it.