I recently upgraded my KDE to version 4.2.x so that I could use the upgraded 1.6+ versions of K3b on my system to take advantage of Blu-Ray and other features.
Unfortunately, even though the 1.68beta version starts, it absolutely will NOT recognize either of my drives at all.
It seems to be something to do with DBUS, HAL, or both, but I am unsure.
If it is related to HAL/DBUS, I must confess that I don't understand why that is necessary, since I am not using either an external SATA drive or USB/Firewire.
My drives are an ATAPI DVD+-RW and an SATA Blu-Ray.
I have no need to hotplug or otherwise mess around with my burners, and this step forward by allowing those drives is a major step back for me.
If there is a compile time option to disable the need for HAL/DBUS, I am all ears, since I only will ever need ATAPI/SATA support.
I have scoured the web in vain hope of finding a definitive answer, but nothing works.
I kept my old KDE3.x libraries in my /opt directory, and using those, I can still run the old 1.0.5 version, but I would prefer to scrub the 3.x libraries and old K3b and move up permanently up to the current versions.
Anyone out there have any idea how to get this off the ground?

This is a major pain.

I should have included the output from the XTerm when I ran this, but I was posting from a different computer.
Thanks for any ideas.
Here is the output (yes, my shell is tcsh) of "k3b >& out"

k3b(28698): ""Backgroundcolor" - conversion from "Window" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(28698): ""Foregroundcolor" - conversion from "WindowText" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(28698): ""Backgroundcolor" - conversion from "Window" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(28698): ""Foregroundcolor" - conversion from "WindowText" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

K3bQProcess::QProcess(0x0)
K3bQProcess::QProcess(0x0)
QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

K3bQProcess::QProcess(0x0)
k3b(28698): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(28698): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(28698): Attempt to use QAction "quick_dir_selector" with KXMLGUIFactory!
QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

This looks like Solid is unable to maintain a link with HAL, it has probably crashed...
Please check your system configuration, especially the D-Bus System bus and HAL.

Code: Select all

QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

I hate to sound clueless, but I must admit I know next to nothing about either HAL or DBUS, except that they seem mainly intended for people who make extensive use of external devices or hotplugging.
If you could be more specific, I would gladly configure them both to work properly, but what I was really hoping was that someone would know of a way to disable HAL/DBUS and have it run for my system, which has only internal DVD burners.
I dug all over the documentation in the source code for K3b, and I either missed the section that explains how to run without having to use HAL/DBUS, or it is not in there at all.
Anyone?

K3b uses Solid (KDE hardware library) to enumerate burning devices. Solid currently uses HAL as its backend. As far as I know there is ongoing development of new backend based on udev/udisks/upower but I don't know when it will be finished.

you should probably contact the developers of your distro which maintain kde4, and ask them how to debug this further, since starting and stopping services like dbus and HAL are different on different distroes, making it hard for us to tell you exactly what to do.