I will say that I haven't been able to get the latest version of Hal (in
Lenny) to initialize on my AMD64 system at all. I'm currently running kernel
2.6.21; all hal dependencies are in and running.
Here is a printout of hald --daemon=no --verbose=yes:
15:20:01.725 [i] hald.c:529: hal 0.5.9.1
15:20:01.725 [i] hald.c:594: Will not daemonize
15:20:01.725 [i] hald_dbus.c:4807: local server is listening at
unix:abstract=/var/run/hald/dbus-AXTNAeSuNg,guid=7b22275b56e2c28a96cfe30046b10711
Runner started - allowed paths
are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
15:20:01.728 [i] hald_runner.c:299: Runner has pid 30143
15:20:01.728 [W] ci-tracker.c:200: Could not get uid for connection:
org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of
name 'org.freedesktop.DBus': no such name
15:20:01.728 [E] hald_dbus.c:4462: Cannot get caller info for
org.freedesktop.DBus
15:20:01.728 [i] hald_runner.c:180: runner connection is 0x650480
15:20:01.729 [i] mmap_cache.c:251: cache mtime is 1185664204
*** [DIE] osspec.c:watch_fdi_files():349 : Unable to initialize inotify:
Function not implemented
So I must say that I am waiting with bated breath for a fix to come through!
LATER -- I got to reading through the existing bug a bit more thoroughly, and
find myself moved to add the following details:
1. I am currently running Lenny on my AMD-64 machine.
2. I went so far as to try reinstalling hal several times from online
download. Indeed, I even tried a different server, to rule out the
possibility of corrupted file. No help at all.
3. I'm afraid that hal never has gotten to the point of having a pid on my
machine. Every time aptitude tries to start it to configure it, it hangs. A
consequence of this is that, every time I do an aptitude upgrade now, it has
two programs sitting out there partly configured and useless: hal and
kdebase, which depends on hal.
Thanks *VERY* much for your efforts in this regard. If you have any further
questions, please shoot them to me. :)
--
. Willy Gommel
http://www.wg3.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
