I just built KDE 4.13, installed to /opt/kde, on my BLFS system (mostly 7.5), and the Device Notifier is not behaving as expected. No matter what sort of USB device I plug in, it just says "No Devices Available". This is an otherwise successful BLFS setup, and such devices always work in other desktop environments (e.g. Mate) and /dev/sdx exists for the device in question.

If I run "solid-hardware list details" I see output like the following:

Object::connect: No such signal org::freedesktop::UPower:: DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower:: DeviceRemoved(QDBusObjectPath)
Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.ServiceUnknown"
"The name org.freedesktop.UDisks2 was not provided by any .service files"
Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.ServiceUnknown"
"The name org.freedesktop.UDisks2 was not provided by any .service files"

Is there a runtime dependency on UDisks2 now? I'm not using UDisks2 for many reasons and would rather not do so. (I assume a runtime dependency, because I compiled everything successfully without it; although I remember seeing UDisks2 curiously found during a configure stage at some point and that made me confused.) Is there any alternative here? I do have UDisks(1) installed though. Thanks in advance.

Apparently kdelibs builds udisks2 support by default, even when -DWITH_SOLID_UDISKS2=TRUE is not set. To build udisks(1) support, I consulted CMakeLists.txt in the parent directory of kdelibs at the section

############### Give the user the option to build the udisks2 solid backend instead of the udisks backend ###############
option(WITH_SOLID_UDISKS2 "Enable the udisks2 solid backend instead" "ON")

and changed "ON" to "OFF". Then I recompiled kdelibs, and the Device Manager now works as it should.