On Thursday, 2009-11-19, spir wrote: > * There is an issue about hal and solid, or rather they do not seem > to understand each other. Seems to be rather on hald's side, for > even if hald runs I cannot execute 'lshal'; output: spir@o:~$ > lshal Could not initialise connection to hald. Normally this means > the HAL daemon (hald) is not running or not ready. > * I also tried (found on another thread): > spir@o:/media/cdrom0$ hal-disable-polling --enable > --device /dev/cdrom Could not initialise connection to hald. > Normally this means the HAL daemon (hald) is not running or not > ready. Both errors say that hald is probably not running. Can you check your process list, e.g. through CTRL+ESC, if hald or /usr/sbin/hald or similar show up? Most like as a system user, here is uses "haldaemon" > * Finally, I found 'hal-info' installed, according to KPackageKit, > but: spir@o:/media/cdrom0$ hal-info > No command 'hal-info' found, did you mean: > Command 'al-info' from package 'flightgear' (universe) > hal-info: command not found hal-info is basically a data package (no programs), containing device configuration data files for HAL. 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.
