I'm affraid not zekus. The only workaround I've found is to build your own custom 2.6.18 kernel. Whatever is causing this problem seems to be fixed there.
I did a some HAL debugging and found out the hald process is indeed defunct (marked Uninterruptible sleep / session leader). There's no way to kill it, not even with KILL signal. Here's the whole hald ps listing after system boot. root 4211 0.0 0.1 10260 1632 ? Ss 03:28 0:00 /bin/sh /etc/dbus-1/event.d/20hal start root 4221 0.0 0.1 14228 1092 ? S 03:28 0:00 /usr/sbin/hald 106 4222 8.4 0.5 21176 5816 ? Ds 03:28 0:02 /usr/sbin/hald root 4223 0.1 0.1 11304 1140 ? S 03:28 0:00 hald-runner 106 4229 0.0 0.0 9288 876 ? S 03:28 0:00 /usr/lib/hal/hald-addon-acpi 106 4244 0.0 0.0 9288 872 ? S 03:28 0:00 /usr/lib/hal/hald-addon-keyboard 106 4260 0.0 0.0 9292 896 ? S 03:28 0:00 /usr/lib/hal/hald-addon-storage I also managed to start HAL in verbose mode by first disabling it at /etc/dbus-1/event.d/20hal. This produced a big text log, which I'll add as an attachment. Seems like it's hanging at acpi LID... or at least that's the last log entry before the process hangs. Oh well... I hope someone can make better sense out of this. I'm short on ideas as to what to try next. :( ** Attachment added: "hald started with --daemon=no --verbose=yes" http://librarian.launchpad.net/4942890/hald_verbose_nodaemon.txt -- HAL fails to initialize / hal-device-manager not working https://launchpad.net/bugs/62990 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
