Dear visitor, welcome to KDE-Forum.org.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
Slackware problem
Since I upgraded to KDE 3.5.4 (yesterday), I was unable to open ANY device in media:/. It says "Feature only available with HAL". Is there a way to disable this behavior? Afterall Slackware doesn't come with D-BUS/HAL. The kdebase package is not compiled with hal backend, but the media manager is still trying to mount the devices using it. Any ideas?
This post has been edited 1 times, last edit by "Furion" (Aug 3rd 2006, 10:57am)
RE: Slackware problem
I'm rather upset at the moment. I am a faithful KDE user. And I run a little distro that's based off of slackware-current. I'm trying to release an update but I cann't because KDE is currently broken and no one seems to want to talk about it. And it's not just that I cann't release a new version my system is also broken.
KDE 3.5.4 is not supposed to require HAL and d-bus. And 3.5.4 is supposed to be just a maintnence update. so what happened how did it break and, how can we fix it.
If you try to Let KDE mount any devices like was posted above it says the features only available with hal. I also went through the trouble if installing hal and dbus into slackware but that still doesn't fix the problem.
This is not a minor bug. It makes the Desktop fairly unusable for most users. And it apears that it's being completely ignored. I have seen no replies to this post above or anyone else on the web asking the same question.
I would like to know any information. Is there something I can configure. Will you rerelease a working version of 3.5.4. Have the KDE team seen or even acknowlage this problem.
The person above posted weeks ago and it's like slackware is just being ignored.
I have the same problem, but I use an updateds Kanotix Distribution (based on Debian SID).
Completely unacceptable
I have favored KDE for more than three years but this HAL problem is serious enough that I am considering a switch to gnome.
This should never have been released like this.
Apparently there is no one who is willing to address this serious error?
I have managed to fix it. Installed D-BUS, HAL, recompiled kdebase with HAL support, and together with ivman everything works as a charm. I'll give you the packages if you want, they are built on current and require the latest udev from current.
This post has been edited 1 times, last edit by "Furion" (Aug 22nd 2006, 9:33am)
I'm glad that you got it to work for you. I don't believe those packages will work for me however. My wireless card requires hotplug. I installed Udev and HAL to try to solve the problem but it threw my wireless card into an endless IRQ loop that prohibits my PC from booting.
Hotplug and HAL conflict and I can not have both.
I worked out my problems. I knew that it would require a kernel change and I was reluctant to upgrade my kernel because of all the headaches it was going to cause with my wireless card. I had attempted it in the past and decided it would be easier to just continue using the 2.6.8 kernel.
I bit the bullet last night and upgraded my kernel and worked my way through the new drivers for my wireless card. After that, everything works great. I am a little disappointed that the new KDE wasn't backwards compatible. But it's just growing pains I guess.
Saturday, June 29th 2024, 3:20am
Go to the top of the page
