KDM starts too early in Lucid, causing keyboard/mouse not to work at first and ACPI not to be detected.

[Michael Marley]

Binary package hint: kdm

On my Lucid amd64 test system, KDM appears to start too early in the boot process. When it first comes up, it is impossible to use the keyboard or mouse for several seconds, and a message like this appears in the log:

 Error config/hal: couldn't initialise context: unknown error (null)

Additionally, another error appears in the log stating that /var/run/acpid.socket could not be found, and the ACPI connection failed. I have worked around the ACPI problem by modifying the KDM upstart script to wait until acpid is running before starting KDM, but it is already supposed to wait for HAL, so I am not quite sure what is going on here. I also wasn't quite sure whether I should file this bug in KDM or in Upstart, so sorry if I got it wrong.

[Jonathan Thomas (echidnaman)]

Hal should probably start only after acpi starts.

[Michael Marley (mamarley)]

kdebase-workspace => upstart => kdebase-workspace => hal

Does anybody actually know what package this bug is in? ;-)

[koso (koso)]

I had the same problem when I connected my USB mouse during boot process (but before kdm started). Also strange is, that internal touchpad worked, only usb mouse, and "internal" keyboard (notebook) were ignored ...