On Thursday, 2009-11-19, spir wrote: > Kevin Krammer <kevin.krammer@xxxxxx> wrote: > > > > Both errors say that hald is probably not running. > > > > > > Yes, I know, but as shown in another parts of my post, I get proper > > > feedback when running hald with --verbose: > > > > > > spir@o:~$ hald --verbose=yes > > > 12:29:37.191 [I] hald.c:680: hal 0.5.13 > > > 12:29:37.192 [I] hald.c:681: using child timeout 250s > > > 12:29:37.192 [I] hald.c:690: Will daemonize > > > 12:29:37.192 [I] hald.c:691: Becoming a daemon > > > > But this is you explicitly starting hald as a user. hald is a system > > service. All its clients will look for it on the D-Bus system bus. > > > > Try this: > > dbus-send --print-reply --system --dest=org.freedesktop.DBus > > /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep Hal > > > > that should give an output like > > > > string "org.freedesktop.Hal" > > Exactly. does this mean hald runs fine? Yes, but this brings us back to the question by lshal says it isn't. Maybe you can check on a distribution specific list or forum. If even the basic commandline tools fail to work, there might be something wrong with the system setup. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
