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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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.

** Affects: kdebase-workspace (Ubuntu)
     Importance: Undecided
         Status: New

-- 
KDM starts too early in Lucid, causing keyboard/mouse not to work at first and ACPI not to be detected.
https://bugs.edge.launchpad.net/bugs/490803
You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu.