Ted, do you still get this if you temporarily purge hal-info? That should get rid of the ubiquituous input.keymap properties in hal.
As for the Xorg.0.log hal issue, X.org config/hal.c prints that if libhal_ctx_init() fails. This can happen due to a variety of reasons, and finding out why would need a gdb attached to the X server with a breakpoint at this function. I see that this is hard to do, though, so maybe we need a hal with some fprintf() logging augmentation to find out where it fails. Ted's experiments with delaying the gdm startup seem to indicate that it's not a race condition between hal being busy to attach all input.keymap properties to devices and gdm starting up, so the first X.org startup apparently does some input device detection which change system state. So my current theory is that Ted has like a gazillion hal-setup-keymap processes running (spawned from /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi) which might just get into each other's way. Ted, can you please check that in your augmented gdm script? (ps aux|grep hal should do). Thanks! -- On reboot X requires restart because mouse and keyboard are unresponsive https://bugs.launchpad.net/bugs/276857 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
